BusinesSystem with blank Logical System Name
Hi All, I add a new client to an WebAsABAP Technical System using :
SLD>TechnicalSystems>myTechnicalSystem>Clients>AddNewClient
ClientNumber: 123
LogicalSystemName: SIDCLNT123
and than I set the new Client number to the old businessSystem, using:
SLD>BusinessSystems>myBusinessSystem>Integration>Change...-->210 of TST
Now in the Integration tab on myBusinessSystem the LogicalSystemName is blank.
any suggestion please.
Tnk
Domenico
Hi Domenico,
I have faced the same problem in my current implementation.
What i did was i deleted the Business System and then created the Bs System with the same name. After that you refresh SLD cache.
I did the following steps
<i>Remove the existing client in TS
Add the new client n TS
Remove the business system
Add the new business system with new client.
In ID remove the dependencies of the business system.
Remove the business system.
Save and Activate.
Assign new business system in ID.
save and activate.</i>
Hope It helps
regards
Ramesh P
Similar Messages
-
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 Shanmugamopen BS in edit mode,
choose from menu: Adepter Specific Identifiers
Here you push button: Compare SLD data
Save and activate -
Same logical system name for two productive systems - BW, PI issues
Dear all,
we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
However as far as I know:
- we cannot connect systems with same logical system name to BW,PI
- we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
How can we overcome the problem?
Please advice.> However as far as I know:
> - we cannot connect systems with same logical system name to BW,PI
> - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
Right.
> How can we overcome the problem?
Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
Markus -
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 -
Problem with logical system name
Hi All
We are facing problem when connecting Ecc 6.0 and BW
When i execute the RSA 1 transaction, i am getting the following error:
<b>Logical system name has been changed for this system</b>
I raised this issue to SAP.
I got the following reply:
<b>Please see if the RSADMIN table has the correct logical system in BW.
If the logical system name here is incorrect, use report
sap_rsadmin_maintain to change the logical system name.</b>
We reffered the Table RSADMIN, but couldnt identify which field has got logical system name.
Then we executed sap_rsadmin_maintain program in se38, but dont know what to enter in value and object field.
Can anyone help in this regard
Thanks in advance
Regards
RakHi Lars,
I would start RSA1 in debugging mode. Try to establish which check is giving you this message by e.g. trying to set breakpoint at message.
Like this you can at least check which entry must be converted in order to be able to proceed.
Best regards,
Olav -
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,
RehanHi 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 -
Cost center integration with HR - logical system for CRT inconsistent
Hi there,
we are distributing Cost centers from our SAP ERP system to another SAP HR system via ALE [COSMAS01 basic type].
The cost center created in target system contains information about source system logical system name - table CSKS, field LOGSYSTEM.
This is causing problems in Travel Managment in SAP HR system, where we get the error: Logical system for CTR inconsistent.
Cost centers created/changed in HR system does not contain any value in CSKS-LOGSYSTEM field and work fine.
Any ideas how to solve this issue?
For now to fix the issue, user needs to do a phony change in SAP HR system to get rid of original LOGSYSTEM value.
I am thinking about removing field E1CSKSM-LOGSYSTEM from COSMAS IDoc but I gues there must be simpler soloution.
Thanks for your advices,
IgorIgor :
I think this has something to do with matching logical system with controlling area in TKA01. Another option for cc's logical system to have no values when outbound ALE is to config V_TKA01_ALE (so it will be transported to the system that has cc ALE to other systems) to have field 'ALE Distribution Method' blank (No distribution to other system).
This way, when SAP is creating outbound idoc for COSMAS, field CSKS-logicalsystem will not be populated (logic is in SAP 'MASTERIDOC_CREATE_COSMAS' , around line 86).
Rgds. -
Assign a Logical System Name of a production client
Hi everybody,
We have an ERP system (now upgraded to ECC 6.0) that is in productive use since 7 years. Until now, no Logical System Name have been assigned to the production client - the field in transaction SCC4 is empty/blank.
Now we plan to implement a BW, so a test and a productive BW systems have been installed. According to the attached file and content of note 184447 we choose to use "Option 1: Uniform Logical System names clients by system type" for naming convention for LSN's.
All the systems/clients (BW test and productive, ERP test only) now are assigned with corresponding LSN's, except the production ERP client. It is still without LSN and the client is not defined as Source System for productive BW system.
So, my question is:
Should I expect any problems if the LSN of the production client is set up now, after long time, effective productive use?
I would mention that this is infact initial setup, not a change of LSN. Therefore transaction BDLS is not relevant, I think.
Thanks in advanceHi DB49,
I already did an initial setup of LSN in the test ERP client (that client is copy of the productive ERP client, i.e. the LSN has not been set). And everything seems to be OK.
But the documentation says that ".... In a production system, the logical system must not be changed ...".
"Changed" is not "ïnitial setup" of course, so there will not be any problems I hope, but ...
SCC4 --> LSN field --> F1 -->
"System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
The logical system is relevant in the following SAP areas:
ALE general: two or more logical systems communicate with one another.
ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
Workflow objects: the logical system in which the object is located is always included in an object's key.
When maintaining the logical system, note the following:
The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system." -
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 HummelHi,
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 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 -
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.
RegardsHi,
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. -
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 ProfileHi 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 -
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 MerwanaFor 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. -
System Copy and Logical system name conversion
Hello All,
Can any one let me know some inputs over these few queries.
1. How much time would a 500+GB clients take for Export and reimport after the system copy.
2. What would be run time of the BDLSS report ( Converting the logical system names) for a typical 1500 GB QTY system
The requirement is my QTY has 3 clients, and i would like to refresh it with my PRD data. How do i safely perform thia activity with the least downtine possible and please note, the clients are around 500+ GB huge..
Thanks in advance for your inputs.
Rgds,
SriHi Frank,
the parameters of my installation are as folows.
Appl Serv : OS - AIX (5.2 Version) and CPU's - 4 (Mem 20480) ::: DB serv : OS - AIX(5.2 Version) and CPU - 6 (Mem 22528)
The DB version is Oracle 9.2
We are on 4.7 enterprise version of SAP with SAPKA62055 patrch level.
br
Sri -
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,
RichaThis 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
Maybe you are looking for
-
How to Customize Preview and Print / Sales Order Acknowledgement
Hi, Our client needs some additional attributes on a sales order acknowledgement print ( Preview and Print ) output. The current layout is based on ONTORDDFFN.xml and ONTORDDFN.xsd How to customize the same to include additional attributes like Terri
-
I have just aquired an iPod Touch 2nd Generation 8GB. When it is connected to my PC, running Vista home, it says it has synced successfully but I can,t transfer onto it an album I have bought and downloaded from iTunes. Help!!! This is my first Apple
-
Please, make it possible to rename the file from within LR - in different modules, including Library and Develop. This can be done by adding an option "rename photo" into the right-click menu, - just next to "delete photo".
-
How to include two charts in one web template
I need to dispaly two charts which are based on same query and on characteristic 1 vs KF's and the other on characteristic 2 vs KF's in one web template. How can this be done? Thanks in advance, Murali.
-
IPhoto slideshows - randomly rotating images.
Hi People, can you help? I've put photos from my Nikon onto the hard drive and imported some into iPhoto v5. I then rotated the ones needing it, but when I run a slideshow the rotated images sometimes appear correct, but then appear rotated again, so