Reg: Table name where logical system name will store in R/3 and CRM..

Hi
We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
Regards

Hi,
In CRM: look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
Hope this helps.
Thanks,
Karuna.

Similar Messages

Logical System name in BBP_DET_TAX_CODE

I am having a problem updating the logical system name in the configuration for BBP_DET_TAX_CODE. The menu path is SRM Server -> Cross-Application Basic Settings -> Tax Calculation -> Determine Tax Code for Country/Product Category. When I try to add new entries to the table, the logical system name field is grayed out so that I cannot enter any value.
The entries in the table have the logical system name. Example:
I Domestic US CAP035 DRACLNT220 I0
I Domestic US CAP036 DRACLNT220 I0
I tried using the Edit -> Change Field Contents -> Source system name, but this didn't change any values. We are running SRM Server 5.5 with support pack level 14 in classic mode. Any help would be appreciated.
Thanks,
Scott Andrew

Hi
Yes, logical system field is greyed out. Once you enter the product category (category ID), it will automatically pick the relevant backend logical system.
R/Reddy.

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

Logical System name in Entitlement Systems

Hi,
In Authentication > SAP, I have given System and client names, but logical system name is not generated.
Please let me know how to resolve this.
Thanks in advance,
Priya

Hi John,
Thanks for your response.
FQDN and IP address are added in the host file.
But still the logical system name is not displaying.
Without logical system name, other details are filled for Application Host Logon as
Application server name - Host name
All the details are filled except the selection of logical system name.
Then it is displaying the error - "Please specify complete credentials for either load balancing or direct application host logon"
Please let me know how to resolve this.
Thanks,
Priya.

Where to define third party logical system name in file to idoc scenario

Hi Friends,
I am shalini shah.
I have one doubt, where I can define the logical system name in File to Idoc scenario.
I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
In SALE or any where.
Please give me solution.
Warm Regards,
Shalini Shah

Hi Shalini,
You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
Just refer the below link for configurations with step by step solution.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

Reg Logical System Name

Hi,
We have ECC 6.0 PROD and ECC 6.0 QAS System.
WE have different logical system names for both the systems
But when we refreshed the PROD to QAS , we have to run the BDLS transcation to change the logical System name(since we are having different logical System name)
But BDLs is taking more than 40 hours.
Please let me know , whether logical system name can be the same throughtout the landscape or not
In other words , is there any side effects if i have same logical system name for QAS and PROD

I've been researching the same issue. I found the following
"Is it necessary to change the logical system names?
Because of the two reasons mentioned above (long runtime of transaction BDLS and possible inconsistencies), it may be desirable, to avoid the renaming of logical systems during system copy.
Whether logical systems names need to be changed at all after a system copy depends on the type of the target system: "
This is from SAP System Landscape Copy for SAP Net Weaver and my SAP Solutions
Best Practice for Solution Management
I found it searching for sap bdls alternative
Hope this helps. I'm continuing my search.

To get the logical system names of all the child systems in a CUA envirnmnt

Hi Gurus ,
Is there any table where we can find the logical system names of all the child sytems in a CUA environment .
This is for a requirement that i need to develop an automated process where we can reset the password of all the child system in a CUA environemt when requested by the user at once .
I found some tables such as V_TBDLS , but they do not contain the exact information what i need .
Thanks in advance ,
Harshit Rungta

Hi,
You are in the right track. BD54 will show you the logical system name for all the existed systems in CUA.
Else you can also go to your CUA system and execute t-code SALE --> Basic Setting --->Logical Systems ---> Assign logical system to client -
> Display details
here you can see logical system names for all the clients assigned to CUA.
Thanks,
Deb

Logical system name conversion.

We are performing a logical system name conversion of a client and its taking long time due to huge DB Tables like COEP.
Is there any process to speed it up ? Also what will be the consequences if Consutants workin the Other clients of the same system.

Hi Narendran,
what problems would it create ? i am looking for some specific ones as i too would know that if a user works during the process the database tables which are getting updated with a new logical name would get corrupted and there is a possible chance that the table for eg VBRK woiuld be having a few entries with the old LS name. But my thoughts were in this direction. This report first converts the table T000 and then TBLST from where the MANDT and LOGSYS gets picked up many times. if they are converted every new entry which is entered will be having the new name and the old names are under the process. so how risk is it ? to allow a user to work is what i am looking for. This might be putting a test to SAP code but i am looking for this test as analysing this report would help us in many ways. you must be knowing that this report may run upto weeks, we had this experience in the last client copy and i am trying to check on this reports behaviour.

Changing Logical System Names

Currently, each instance(SID) in an entire landscape all have the same logical system name and the RFC name that corresponds is all the same. You really don't know what system the RFC is pointing to until you open it up and see which server, etc. is listed in the RFC. So, we are working on a project so that each instance has it's own unique logical system name. The biggest problem we are concerned about is making sure that we change all the places where these definitions exist. I have a small list of transactions that need these items changed (SM59, SALE, SCC4, RSA1, SMQR, SMQS, SBIW, SPRO (this is a tough one)). We realize we will depend on our application teams heavily to know where they changed any configuration to use logical systems. My question is to see if anybody has done this type of change, if they have any tips/guidance, to see if anybody can give some good direction on where to find all the places these LS names are used, and if anybody else can throw out any other transaction suggestions that we should check. Thanks in advance.
-Marsha

Marsha,
I think you should examine the reasons why it would not work before asking if you can do it. One reason for us was archiving. We regularly archive off data only keeping the last 3-7 years of data in the system for some tables. Changing the logical system ID for us would mean it would be impossible to reload some of that archived data, without customizing or a new development effort.
So if your questions is can you do it? Yes, you can do it.
If the question is should you do it? .....Well, then you need to examine why or why not in your own environment. There are likely to be pitfalls especially if its usage is widespread at your company as you indicate.
-jwise

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

Logical system name to be updated while client copy--URGENT HELP REQUIRED

Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.

Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe

How to get RFC Destination and Logical System name dynamically

Hi all,
I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
There is a way to do so in CRM which is as follows:
DATA: lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
           ls_siteselect TYPE siteselect.
CALL FUNCTION 'SMOF0_READ_SITESELECT'
    TABLES
      to_siteselect = lt_siteselect.
READ TABLE lt_siteselect INTO ls_siteselect
         WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
I want to achieve the functionality fulfilled by the above code in R/3.
Kindly help.
Useful answers will be rewarded.
Thanks in advance,
Karan Merwana
I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
Message was edited by:
        Karan Merwana

For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
If anyone does manage to get a workaround, please let me know.

Stuck with logical system name for JDBC Sender system!!!!!!!!!!!!!

Hi All,
I'm doing a scenario as JDBC2FILE.
I tried to add my jdbc sender system to SLD. So i created the technical system
now i'm creating business system...what should i give at logical system name tab? I've created tech system and business system as third party.
do we need logical system name in this scenario where we are not interacting with any R/3???
can anyone suggest the way to achieve this scenario?
Thanks in advance.....
Santhosh.

Hi Santhosh,
I just want to add ons..few more information which it might help you.
You no need to give logical system when you are using Thirdpaty.
Please check the below blog you will get more idea how to proceed to achieve the JDBC Scenario.
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
If you have any doubts while proceeding with your scenario plesae let me know..I will try my level best.
Thanks and Regards,
Chandu

Change of logical system name

Dear Experts,
I have following situation in ECC 6 EHP4 system:
a system copy of PRD system was peformed on QAS. POst system copy BDLS was NOT run, and logical system of QAS client was maintained manually.
Now client 300 in QAS has logical system as QASCLNT300 (after copy it was PRDCLNT300). The problem is that many accounting documents still point to PRDCLNT300 and hence can not be viewed now since log sys is QASCLNT300 now.
I can not run bdls now bcoz for BDLS target logical system should be new. Also for last few months new accounting docs has been generated for QASCLNT300.
Is there any way around? pls suggest
-Thanks,
Richa

This is a situation , where you cannot run BDLS now and you face issues with accounting docs .
As far as I feel , you will have have to redo the system copy and run BDLS again. The logical system name should never be maintained manually in SCC4.
Edited by: Ratnajit Dey on Jan 2, 2012 12:16 PM

Logical system name changes

All,
Has anyone faced a scenario where you need to change the logical name for any SAP system?
For instance:
System      Logical Name                                                    System      Logical name B
BW                      A                     system is pointing to            ECC                  B
ECC will be upgraded and system name will changed to C
Is that possible? If so do you forsee any issues? Can we switch ECC B to ECC C with no issues?
I appreciate any help.
Regards

Hello Mike,
please elaborate a little more your inquiry. Are you talking about the ALE logical name changing? For this, please check the following notes:
#544509 ALE: Converting the name of the "logical system"
#121163 UTI: Logical System names
If you're referring to a domain name changing (like a Windows domain name change) or a hostname change, please refer to the following notes:
#96317:   Host names during R/3 upgrade, tips & tricks
#1275273: Hostname change on 7.10/7.11 java stacks
#757692: Changing the hostname for J2EE Engine 6.40/7.0 installation
#8307:    Changing host name on R/3 host: What do you do?
#1070561: SMD: Best practice for planned domain name changes
and on the following SDN threads:
/message/9196590#9196590 [original link is broken]
Re: Domain name change
Re: Change the Domain Controller
How to change hostname
Change Domain Controller
Or, lastly, you're talking about a SID change? On this case, you must perform a system copy to change de SID, please refer to the following note:
#11692: Renaming the system ID
(Sorry for the long and generic answer)
I hope this information helps.
Best regards,
Tomas Black

Reg: Table name where logical system name will store in R/3 and CRM..

Similar Messages

Maybe you are looking for