RSA1 initialization - setting of logical system

We just finished the installation of SCM 5.0. In the post-installation steps, we have created the logical system and assigned it to the client. You are then to execute RSA1 and enter the logical system in an initial popup window. Someone accidentally pressed the [Cancel] button on that popup window, but a BI_CONT_ACTIVATION job was executed anyway. The job is failing with errors related to not being able to find the logical system, as expected. Is there a way to "re-initialize" RSA1, to allow the logical system name to be entered in that popup window properly, or another way to correct this problem?

It does not provide the popup window for entry of the logical system name again.

Similar Messages

Setting up Logical system in ALE Config !

Hi,
I have set up the ALE logical system in SAP to transfer data. Basically RFC destination setting. While I am trying to test the connection, I am getting an Error Program INBOUNDASYNC not registered.
Could any one help me out here.
Thanks,
Senthil

Hello,
Please make sure you have completed the starting of SMD agent also after the setup, u can find it in the guide.
also check the p4 or Https port number is correctly mentioned.
The user and pass mostly would be that of SMDadmin, created during the setup, or u can use SIDADM which will wrk fine.
sometimes root needs to be used as even sidadm can be restricted in ur envt. ( just in case).
Regards,
Kaustubh.

RSA1 error Logical system name has been changed for this system

Hello All,
Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.
But now when we login to client 500 and execute RSA1 it is showing
Logical system name has been changed for this system"
In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps
Change the name of the logical system (table T000) for client back to SIDCLNT300. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to SIDCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow.
Guys do you know how to fix this ? .
Also do you know Assignment of Source System to Source System ID (table RSSOURSYSTEM) using RSA1 ?
Edited by: Sahad K on Mar 17, 2008 10:55 AM

Hello Hari,
Both the options you said cannot be used
since the logical system SIDCLNT300 is used by client 300 and it cannot be given to client 500. Also there already exist a logical system SIDCLNT500 which is assigned to client 500.
I found out the issue. In the table RSBASIDOC the logical system name that can use rsa1( bw client )is set as SIDCLNT300). Only if we delete that entry and set it to SIDCLNT500 ( 500) we can use it on client 500.
The solution is specified in /message/3284842#3284842 [original link is broken]
Let me try the solution 2 and inform you.
Solution 2:
You cannot delete the source system. Two cases have to be distinguished:
The source system still exists.
Switch to Transaction SM59. Find the destination which has the same name as the logical system of the source system from field SLOGSYS in table RSBASIDOC (see above).
Such a destination does not exist in Transaction SM59. In this case, you have to create the destination to the source system. Name the destination equal the entry in SLOGSYS from above. Then return to the Administrator Workbench and repeat the deletion.
The entry exists but a remote login is not possible. Correct the communication parameters.
Everything works. Change to Transaction SE37, function module RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS = <log. name of the source system>, I_FORCE_DELETE = 'X'.
The source system no longer exists or was replaced with another source system with the same IP address.
Proceed as described in the first case but make sure, that the field 'Target host' contains a not existing server in the maintenance screen of the destination (Transaction SM59). If necessary, change an existing entry. Later when you delete, the system asks you whether you want to delete, although the source system is not available. Select 'Ignore'.
Incase you have any idea other than this please let me know how to edit the RSBASIDOC table and change the entry to client 500.
Edited by: Sahad K on Mar 18, 2008 5:07 AM

BW / SolMan Logical System Change

Hello all, I am having a BW related issue and would really appreciate some advice. I realize some of this is for the solMan forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1.
I am embarrased I missed this section in the master guide the first time around. I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

SolMan / BW Logical System Issue

Hello all, I am having a SolMan/BW related issue and would really appreciate some advice. I realize some of this is for the BW forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1
I am embarrased I missed this section in the master guide the first time around.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.
I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.

EBP Logical system after client copy

Hi Friends,
We did a client copy for our EBP system from the production system.
Now when I access the system to create invoice, the below error
prompted.
Error message
Error calling META BAPI META_CALCULATE_TAX
Error occurred calling META_BAPI_DISPATCH
In the debug mode for F/M META_BAPI_DISPATCH , I could see the logical system
still pointing to the live system.
So far Basis already changed all the logical system entries.
Hope someone could give some hint to solve the problem
Many thanks
Mike

Dinesh,
We are using SRM Standalone. No sync with backend product categories. In the debug mode I could see the system getting the logical system = "production sys" for business object BUS2205 (invoice).
Belief there is some setting for logical system still need tobe changed.
Hope you could give some hint.
Many thanks.
Mike.

Post installation error "Local logical system is not defined"

Hello everyone,
I freshly installed the latest SAP NetWeaver 7.01 ABAP Trial from scratch and like to configure ALE.
I followed thew steps of http://help.sap.com/printdocu/core/Print46c/EN/data/pdf/CABFAALEQS/CABFAALEQS.pdf
(ALE Quick Start) but cannot get through the following step on page 12:
From the R/3 Implementation Guide screen in TA SALE
choose Basis
    Application Link Enabling (ALE)
      Modeling and Implementing Business Processes
        Maintain Distribution Model and Distribute Views
Clicking on Maintain Distribution Model or using TA BD87, I immedeately get the following error:
The initialization of the logical system has failed.
With TA BD64 the error: Local logical system is not defined arises. I also looked at
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi,
/people/vikash.krishna/blog/2006/10/15/replicating-hr-master-data-part-1 and
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide describing the same actions
to find an explanation, but without success
I assume, the error does not occur because the trial version does not support it, but
because of other post installation activities that must be done.
I already created two logical systems and assigned them to newly created clients 100 and 200,
but this did not have any impact on BD87 and BD64 as i was hoping.
Does somebody know what to do here?
Thanks in advance and kind regards,
Andreas

Hi Naveed,
i made the following settings:
SCC4: new entries created
100     Sending System
200     Receiving System
SM59: new ABAP type 3 connections:
RFC_DEST_LS_100
RFC_DEST_LS_200
- Tab Logon & Security Logon user: current user (bcuser client 001)
Connection test is successful
- Technical Settings: target host: localhost
SALE: new logical systems created
LS_100
LS_200
SCC4:
double click on 100 Sending System   configured with logical system LS_100
double click on 200 Receiving System configured with logical system LS_200
kind regards
Andreas

Error: Local logical system is not defined

Hello
Our scenario is File-XI-IDOC , wherein we connect to SAP R/3 Development server for posting IDOCs
Now , we need to connect to SAP R/3 Quality server for posting the same IDOCs.
However, recently, the Quality system database was refreshed with production data completely Hence all the ALE configuration data in Quality tables got erased, due to which we are not able to send IDOCs to Quality
Now, we proceeded as follows :
1. We set up Logical System in Quality
2. We entered the partner profiles too
However when we goto transaction 'BD64' , it gives error as "Local logical system is not defined"
Hence we had to redistribute the profile from the sender system, and IDOC started being posted correctly
But, we need to know, why cannot we execute 'BD64' in Quality itself and also, will this have any impact on our IDOC posting
Further, if Quality is refreshed every now and then, do we need to repeat the above process each time or some other way is available to restore the ALE configuration data automatically
Regards

Hi Naveed,
i made the following settings:
SCC4: new entries created
100     Sending System
200     Receiving System
SM59: new ABAP type 3 connections:
RFC_DEST_LS_100
RFC_DEST_LS_200
- Tab Logon & Security Logon user: current user (bcuser client 001)
Connection test is successful
- Technical Settings: target host: localhost
SALE: new logical systems created
LS_100
LS_200
SCC4:
double click on 100 Sending System   configured with logical system LS_100
double click on 200 Receiving System configured with logical system LS_200
kind regards
Andreas

Logical System Name Usages

Hi,
In Connector properties there is one property called "Logical System Name" what is the purpose of this.
regards
mmukesh

Hi,
Some of the purposes of Logical System Name are,
1. Systems of the Central User Administration (CUA) are referred to using logical system IDs. In the SAP sense, a logical system is a client. Therefore you must first set up logical system names that you then assign to the clients in the SAP systems.
2. System in which applications sharing a common data basis run. In SAP terms, a logical system is a client in a database. Messages are exchanged between logical systems.
Regards
Srinivasan T

Logical System,Business System

Hi Gurus,
What is Logical System? n What is Business System?
Wt is the Difference betweent these two?Can you explain me in detial.
thanks in advacne.

Hi Kumar
Logical System
System in which applications sharing a common data basis run. In SAP terms, a logical system is a client in a database. Messages are exchanged between logical systems.
Systems of the Central User Administration (CUA) are referred to using logical system IDs. In the SAP sense, a logical system is a client. Therefore you must first set up logical system names that you then assign to the clients in the SAP systems.
It is possible that the logical system name already exists because you have already included the system in an ALE distribution. You can then ignore the procedures Define/Set Up Logical System and Assign Logical System to a Client.
Business systems are logical systems that function as senders or receivers within the SAP Exchange Infrastructure. You configure business systems in the SAP System Landscape Directory (SLD). A business system is always associated with a technical system (here: SAP Web AS ABAP system).
Configuring an SAP Business System
http://help.sap.com/saphelp_nw04/helpdata/en/87/7277e8fba34421a45d97a41ec27381/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
Defining/Setting Up a Logical System
http://help.sap.com/saphelp_nw04/helpdata/en/aa/b4b13b00ae793be10000000a11402f/content.htm
Assigning a Logical System to a Client
http://help.sap.com/saphelp_nw04/helpdata/en/cf/b4b13b00ae793be10000000a11402f/content.htm
regards
sandeep
ih helpful kindly reward points

What is logical system in ALE

Dear all
I still confuse with Logical System in ALE where we already have Client.
And I see that relationship between Client and Logical System is 1:1
So why we need Logical System instead just use Client ?
Regards,
Halomoan

I think this is what you want to read:
A logical system is an unique identifier of a system/client combination.
That is why SAP recommends to use the notation <SID>CLNT<CLT> to set the logical system. For example, assume you have client 400 for system QA1 and you have client 400 for system DV1. Then the logical system name would be:
for QA1/400: QA1CLNT400
for DV1/400: DV1CLNT400
The logical system is used in the IDOCS that you transmit from one system to the other. So with this, you know the source system of the IDOC, and this tells you where the business document was created.
Using only the client as identifier is not enough, because you can have the same client number in several systems.
Nevertheless, you should read the documentation!!
Regards,
Juan

Conversion of logical system name fails

Hi,
when trying to transport a transformation on BW7 the logical conversion name is failing. When i check the setup (on rsa1 menu "Conversion of logical system names") it seams to be ok on source and target system.
Any tips to solve this ?
thx in advance

Hi,
when you are not maiantained the logical systems properly , then you will get that error when you are transporting the objects
in Bi production system ( to which server you are moving objects) in that you should maiantain the all logical systems as below
1) for examaple BI deve --- BI prd
one logical systm should be bi Dev to BI prd
2) ECC production connected to BOI production
Then one more logical assignment ECC prd to BI prd
normally those two you are maintained i think so.
but when you are moving the objects from the BI development to Bi production
the daat sources are pertaining to the ECC developmet
so that ECC deve to BI Dev ( here there is no problem)
when those daat source s you are moving to production it shows error
because that ECC deve Data source logical system should be changed to BI production
so you main tain one more logical system ECC dev to ECC PRD
in your BI system
Then try reimport the same.
Thansk & Regarsd,
sathish

Event trace error: own logical system not defined ?

Hello,
i am trying to start a workflow when the status of a document changes to "completed". I was checking the event trace with transaction code : "SWEL" and i found out that the workflow is trying to start but there is some kind of error and the event trace is saying :
Your own logical system has not been defined for this client. Most of the ALE functions therefore cannot be used. No links can be written.
Any suggestiobns on what can be the problem ?
points are awarded
Regards

Sounds like you need to setup your client as a logical system, to do so..
To do setup the Logical System follow the following steps
In IMG Settings
Cross Applications -> Distribution (ALE) -> Basic Cofiguration.
Set up Logical System -> Maintain Logical System.
Create New Entries

Setup Logical System from blank

the default logical system of client 100 is blank
now we have to set a logical system for ALE and BW data transfer
but we found that some documents will not be transfer and some document cound not be found
eg: we cant found the FI documents from material document as MB53
debug the program we found that the programe check the logical system
is there any way to change the old documents logical system to new?
i found there is a sap note to describe how to change the logical system from a old value to new
but it not suit the situation of set new logical system from blank value.

HI ,
You need to create the logical system name and assign that to that client.
This can be done in Transaction :SALE.
Have a look at the t-code SALE and its options....
SALE->Basic settings->Logical system---- we have three options.
one is for creation ,assigning itto client ,other one is coversion.:Last one is only called BDLS .(little critical)
Thanks.

Local Logical System

Hi All,
This is my first post.
when I'm trying to create a business partner., there was an error message saying " Local Logical System is not defined / assigned ". What is that exactly mean by? and What are the prior steps we need to take before creating a business partner. Please reply to [email protected]
Thanks

Hi Venet,
Transaction SPRO (this is the IMG) and click on the glasses button (F5).
Under the following path:
-> Customer Relationship Management -> CRM Middleware and Related Components -> Communication Setup -> Set Up Logical Systems
Set up the logical system and then assign it to the client. I suggest you read the document on the left of each section to understand what you are doing.
More information can be found at http://help.sap.com
Cheers
Andrew

RSA1 initialization - setting of logical system

Similar Messages

Maybe you are looking for