Clarification Regarding Logical System Names

HI all,
I read the blogs regarding Logical System Name, even I am having the some problems in my system.
For PI system client is 100.
R/3 System Client is 100 is created.
IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
When I checking in the R/3 system that logical system Name ('PICLNT100') is not there and for r/3 client 100 having the different logical system name.
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
It is different from the SLD logical System Name.
How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
How I have to maintain the logical system names in this case?
please help me in this.
Regards,
Sree

hi.
each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
once you configure it all data from r3 system is exported to SLD.
if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
hope its helps
Rodrigo
PD: rewards points if useful

Similar Messages

Logical system name for acknowledgement in BPM

Hi,
I have a szenario:
IDOC --> BPM --> MAIL
Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
"Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
What can I do?
Possible Solution 1:
I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
Possible Solution 2:
I can enter an existing logical system name in the "adapter specific attributes".
BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
Is Solution 1) a common way?
Thanx
Regards
Wolfgang Hummel

Hi,
there are many ways:
some for aleaud are described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
>>>>Is Solution 1) a common way?
no this is not good a good idea
BTW
you can also supress aleaud raport IDX_NOALE
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Logical System Name Not appearing in the Business System

Hi,
Initially we had created a Technical system with Client 700 without a "Logical System Name" in SLD. hence the 'logical system name' in 'business system' was also Blank.
Now, since we are implementing the IDOC to file scenario; we need to maintain the "Logical System Name" in the client and which in turn should reflect in our Business System in SLD.
Though we maintained the Logical System Name in the Technical System --> Client --> Logical System Name; we are unable to see the same(Logical System Name) in Business System ('Integration' tab)
Please also note that Business System is of the ROLE: Integration server.
When we go to business system in SLD ---Integrtaion tab ---Logical System Name -- is still blank.
Can anyone please help us to update the 'Logical system name' in Business System in SLD?
Regards,
Rehan

Hi Sunil,
I followed your link till
Bussiness System -> select your bussiness System -> in Below pane u will find Details of your bussiness system ->amongs the various tabs available select Integration Tab->U will See option for technical system beside that u will see option for change ->click this ->u will be taken to Logical system ->there u define u r logical syatem name and then save the entries.
When I clicked the option chnage ---> "Change Associated Technical System" appeared, It didn't take me to Logical system.
But in turn I clicked hyperlink corresponding to Technical systems, it took me to technical system --> clients tab --I have entered the Logical system name.
When I go back to Business system again its not showing the Logical system name in Integration tab.
regards,
rehan

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 in business system (SLD)

Hi,
While creating business system in SLD what should give for the logical system name?
Should the logical system name exists in ABAP stack or the new one?
Thanks.

Hi,
If you are creating the BS for SAP R/3 in SLD means we have to give the LS name which we had in SAP R/3( goto SALE and take the LS from there)
Goto Assign LS-----take the client which you are using for SAP R/3 and take the LS name assigned to that Client
Regards
Seshagiri

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

PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED"

HAI EVERYBODY,
PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED" during the material master replication by using middleware parameters.
step1 : i have taken SRM client 810 and named it as CHINNISRM
step2 : i have taken r3 client 810 and named it as CHINNIR3
step3: During material master replication i maintained tables like crmconsum,crmrfcpar,crmparoltp in r3 and smofparsfa in srm client and filtered the objects and loaded the objects through r3ac3,r3ac1,r3as.
step4 : And later i have checked in r3 queues to activate the objects,but i have seen a message like "LOGICAL SYSTEM CHANGED:SEE 588701".according to the oss instructions i have checked in CRMPRLS table in se16 in R3 .there i found out there is one logical client named with T90CLNT810.
oss :588701
Solution
There are different cases in which different forms of processing are
required or where several options exist:
- The logical system name of an R/3 Backend client was changed in
current operation. In this case, the data hangs in the outbound
queues of the R/3 Backend system as specified under point 1 of
the symptom. In this case, the logical system name must be
changed back to the original value. Then the outbound queues
can be reactivated. If no data was transferred to the EBP/CRM
server before the change, also a correctioin of the check table
is possible.
- The same logical system name was used again in a new client of
an R/3 Backend system that was linked to the EBP/CRM server. In
this case, the data is in the inbound queue of the EBP/CRM
server with the exception GUID_FOR_LOGSYS_CHANGED. In this
case, the queue entries which have status SYSFAIL must be rejected, however, not the entire queues. If the new client of the R/3 Backend system you have linked has exactly the same
data as the old client and if it is meant to replace the old
client (that is, this was deactivated), also a correction of
the check tables is possible. In this case, the inbound queues
can be reactivated after the correction.
oss:765018
1. If the situation in your system corresponds to the situation described
under "Reason and Prerequisites" and if symptom 1 occurs, you can
delete the table entry from table CRMPRLS table (there is just one
entry). Since there is no maintenance dialog for this table and you
cannot maintain it using transaction SE16, you must use a report to
delete it. This report is attached to this note as correction
instructions.
Create the report ZZ_DELETE_CRMPRLS in your system and copy the source
code from the correction instructions. You cannot implement this
source code using transaction SNOTE.
You can use the report in every plug-in or plug-in basis system, even
if it is not specified in the validity section.
After you have run the report, you can trigger existing queues again
in transaction SMQ1.
2. If the situation in your system corresponds to the situation described
under "Reason and prerequisite" and if symptom 2 occurs, you can
delete the entry from table CRMMLSGUID (there is just one entry).
Since there is no maintenance entry for this table and you cannot
maintain it using transaction SE16, you must use a report to delete
it. This report is attached to this note as correction instructions.
If they do not yet exist, add the following messages to message class SMOF in your logon language:
Message Message short text
303 User &1 is not allowed to change table &2.
304 User &1 IS not allowed to display table &2.
305 Logical system &1 was not found in table &2.
306 System error! The current client was not
found in table T000.
Create the report ZZ_DELETE_CRMMLSGUID in your system and copy the
source code from the correction instructions. You cannot implement
this source code using transaction SNOTE.
You can use the report for every release of the CRM system, even if it
is not specified in the validity section. The only exceptions are CRM
releases with Support Package versions that are too low such as CRM
Release 3.0 with Support Package 12.
After you have run the report, you can trigger existing queues again
in transaction SMQ1 of the R/3 back-end system or transaction SMQ2 of
the CRM system.
so what should i do to do the replication.please suggest me .untill and unless i solve my problem i cant move to the further activity.i hope you people can solve my problem.thanks in advance.
thanks and best regards,
n.chakradhar

Hi chakradhar,
Did you find a solution to your issue? We are facing a similar issue and looking to figure out how this can be resolved.
BR// 420

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

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,

Logical System Name is defined for which type of Business Sytem

hi
Can some one helps me on this question and explaination.
Logical System Name is defined for which type of Business Sytem ?
a.Third Party
b.Web AS java
c.WebAs abap
d.Standalone java
Thanks
Chandra

Hi ,
Logical System Name is defined for the Business System type WebAS ABAP.
It is used in ALE scenarios when exchanging IDOCs between the particular system and XI. The IDOC adapter will pick up the information from the SLD and it can then be used in the configuration in the Communication Channel (Adapter Specific Identifiers).
Refer to this How-To Guide for more info
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
Regards
Manish

I need help in logical system name in business system

i created two business system with same logical system name and now am getting error in ID when i try to activate business system"" Logical system LSSUN already exists in service | BS_RCVESUN"" So,i again changed a logical system name in SLD and tried to activate it again but changes is not reflected back in ID.again it show logiacal system alredy exists.
pls giv me a steps to reflect changes back in ID.
thanks & Regards
Manikandan Shanmugam

open BS in edit mode,
choose from menu: Adepter Specific Identifiers
Here you push button: Compare SLD data
Save and activate

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

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 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

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

Clarification Regarding Logical System Names

Similar Messages

Maybe you are looking for