SLD Logical System Name Changes not taking effect in IDOC

All -
I've had to change a logical system name in the SLD, everything appears to be okay but new Idocs are still posting with the old LS name - any suggestions as to where to look for the old name would be most appreciated.
Thanks!

Hi Dennis,
After changing the logical system name in SLD have you done "Compare with SLD" from Service --> "Adapter-Specific Identifiers" for Business system in Integration Directory?
- Pinkle

Similar Messages

Logical system name has not been assigned to

Hi, Expert
I m trying to transferr DATA from ECC to APO . when I configured my ECC and APO systems according the SCM 210, but I still meet the error like this
logical system name has not been assigned to
syste: user:
Function/Q/SAPAPO/CIF_PRODUCT_INBOUND
text: logical system name has not been assigned to
my ECC is ECC6.0,and APO 7.0
Can u help me,Thank u. I m waiting the solution on desk
Rockey
Edited by: Xinyou Dong on Jun 2, 2011 9:11 AM

Hi,
I think you dont have partner profile created.
Try to create one with the RFC which is connecting ECC and APO.
Thanks,
Deepthi

Logical system name change

Hi all,
Now my BI development is pointing to R/3 development. R/3 logical sytem name is bbbclnt100. Now all my datasources are pointing to this logical system. Our basis people are going to change the logical system of R/3. Please tell me the repercussions? what will happen to my datasources?
Thanks in advance

Anni,
Change logical system name and run BDLS job to adjust. Do not change souce system. If you change source system all transfer rules will get deactivated.
Check: [Conversion of Logical Systems|http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
Search forum for more links.
Srini

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 changing

Dear Team,
We had upgraded BI system from 3.0B to BI 7.0. At the time of upgrade dev
copy(shadow system) logical system was not changed because most of the data is coming from ETL. Now we want to test the extraction from R/3 Dev.
R/3 Dev is already connectwed to BW dev 3.0B, Now we need to test
extraction from R/3 Dev to BW dev copy server( NW2004SR1 ).
Here we are facing a problem with Logical system. While upgrading the
same logical sys was copied to BW dev copy.
What is the procedure to change the existing logical system name in BW
dev copy and establish connectivity with R/3 dev?
what is the impact if we run BDLS transaction.
Thanks& Regards,
Satish.K.Neni

Hi Satish,
Go to transaction SALE -> Basic settings -> Logical systems -> execute "Define logical system" to create a new logical system -> then execute "Assign Logical System to Client"
That should solve your problem
Regards
Juan
Please reward with points if helpful

Logical system Name Change Via Transport

Hi All,
Recently we made changes in parallel processing profile customizing table (/SAPAPO/SDP_PAR) and created entries for Macro Jobs and CIF.
For Application "CIF Delta Report", Logical system is mandatory and in Dev we gave the APO Dev Logical System Name (AD1XXX). Now when we moved the changes to Quality, expectation was that Logical system name for CIF Entry in the table would change to AQ1XXX - However, it still shows as AD1XXX there. Moreover AD1XXX entry is not a valid entry in Quality System and even when we see Drop Down values for that column (Press F4) - Only APO and ECC Quality systems names are appearing.
Please suggest how can this logical system name be corrected. One option is running BDLS, but when this TR moves to Production there also we might end up in same scenario (Logical system as AD1XXX instead of AP1XXX) and running BDLS in Production wont be approved.
Please suggest if there is any other option to handle this.
Regards,
Alok

Hi Alok,
we describe a solution in our
SAP Rapid Deployment Solutions (RDS)
Quick Link
                Access SAP Rapid Deployment Solutions (RDS) directly via
                  http://service.sap.com/rds
SAP Demand and Supply Network Planning rapid-deployment solution
Quick Link
    Access this area directly via
http://service.sap.com
/rds-dpa
In confgiguration guide
Central Master Data Replication (SCO)
you can read how it is done with
Create Entries in Table
TVARVC for Logical System Variable in Variants
Frank

Printing Paper Changes not Taking Effect

Hi,
I recently upgraded to Windows 7 from XP and I also have Acrobat 9 Pro installed.
When I use a different size page, in this case 11x18, and go to print it will start out as our printer default 8 1/2x11 which is should be. I would then proceed to go to the printer preferences and change the paper size and click "ok" to get back to the main print page where I would notice that the print preview would not update ot the new size. If I proceed to print with it showing the 8 1/2x11, even though it is set to 11x18, it would scale it to the 8 1/2 x11. What I have found to work around it is if I click and then unclick the button "Choose Paper Source by PDF Page Size" it would scale the paper to the correct size. I use different size paper and do not want to change the default size.
This is sort of a hassle and I sometimes notice that when I'm going from 11x17 to 23x20 it would not even update and would not allow me to print on the correct paper size.
I am using a sharp AR-M207 printer. I have tried to use the PCL/PS/PPD drivers for the latest version and they all have the same effect. Additionally Acrobat 9 Pro is also up to date.
Is there an update or a patch somewhere or another reason why this is occuring. I am not included to switch printer mainly because I do need a large format printer and its difficult to find one.
Thanks,

Daniel,
Yes I am currently using the most recent version of Acrobat and Printer Drivers.
I have not tried the Help > Repair option. I actually noticed that this issue occurs on my laptop as well, same operating system (Windows 7). It is possibly an issue because of compatability with Windows 7 although there might be a workaround for it.
I have tried a different printer, ie my laptop, and the same problem occured.
I can look for outdated Sharp print drivers but that might be difficult to find.
Also I currently use Windows 7 64bit.

Posture Policy changes not taking effect in ISE!

Hi all
I think that something is definitely wrong with the posturing rules on our ISE. I am seeing weird behaviour when changing posturing policies and thier elements in our ISE.
In Full, we currently have a policy written with a requirement that clients must have SEP 11, 12.0 or 12.1 installed and the AV defs can be up to 28 days older than the latest AV definition file date.
However, prior to us rolling out SEP12.1 in our environment, we wanted to test that the ISE could remediate SEP 12.1 just like it does for SEP 11 clients.
To do this I created a policy just to test SEP 12.1 being out of date for over 2 days. A client never matched this policy, it was still passing posture using the old policy. I imagine this is because the old policy was still referencing that sep12.1 defs can be up to 28days older than the current release date.
So, in the AV Compound Condition for the old policy I unticked references to SEP 12.0 & SEP 12.1. This had no effect. When I looked at the posture reports they were still showing SEP12.1 clients passing posture on the old policy. Well, this can’t be possible as I have unticked those conditions now.
So, in the end, I was forced to complete delete the old Posture Policy Rule, the Requirements Condition and the AV Compound Condition. I then created it all again from scratch just for SEP11, so there is no reference for SEP12.0 or 12.1.
When I check the posture reports, they are still showing that the SEP 11 clients are passing posture on the old rule and old conditions that don’t even exist any more! Luckily, I haven’t broken anything as clients are still being allowed on to the network and they are being posture checked.
It looks like the ISE is holding on to this old posture configuration somewhere and it may be that the only was to truly get the ISE to recognise the changes I have made to the posture policies is by restarting a particular service (not sure which one) or restarting the whole node (which I don’t really want to do, and shouldn’t have to do surely!).
Any suggestions? This is rather urgent as it is holding up testing of remediation for sep12.1 clients.
thanks
Mario De Rosa

OK, i resolved this by performing a Re-Sync between my two ISE nodes.
It appears that the secondary ISE node went in to a "Replication Disabled" state. Once I performed the Re-Sync, the posture reports now show all the correct policies getting matched.
Lesson Learnt there!
Mario

[SOLVED] Syslinux.cfg changes not taking effect

When I first switched from grub to syslinux, I discovered that my system won't boot properly without a nomodeset command in the boot line (actually I knew that; it was also in grub but I installed that 5 years ago and long since forgot). It worked great.
A few weeks later, I had some trouble with the virtual terminal after X started, and someone suggested adding vga={x} to the boot command. I did that, but as it turns out the one I picked wasn't supported by my graphics card/monitor: Whenever I boot, it says to press {enter} to choose from available modes.
I found one that worked well, and added it to syslinux.cfg, saved my work, and rebooted. It *still* complains about the previous mode and makes me choose a proper one. I have rechecked that my new value is in syslinux.cfg and rebooted countless times since then, and the new values just won't take.
Is there something else I need to do after editing syslinux.cfg? The man page and wiki page are extremely thorough on initial installation and configuration, but not so much on making later changes.
Last edited by WyoPBS (2013-05-15 17:18:15)

When I change label values in syslinux.cfg the new label appears, so I am 100% positive I'm editing the right file on the right partition.
However, I found the answer -- When the list of modes pops up and I key in 313, the boot console is reading that as 0x313. When I have "vga=313" in the cfg file, syslinux reads that as 313 decimal which is 0x139, an invalid mode. It just never occurred to me that the mode menu was presenting hex values... Just had to change it to vga=0x313 and all is well.

Configuration Changes not taking effect for Sun Java Web Server 6.1

Hi,
We're trying to make some changes to a sun ONE web server, to accept a couple of additional MIME-TYPES, as well as turning on compression and adding cache control headers to files. Please review the following and advise as to our path to proceed.
Our first challenge is that it seems that the change to the mime.types file are not being applied. We've added these to mime.types:
type=text/cache-manifest exts=manifest
type=image/svg+xml exts=svg,svgz
Elsewhere in the file is a configuration for PNG
type=image/png exts=png
Using HTTPFox firefox plugin, it's evident that these file types are being served with the mime-type of text/plain. See the attached image. Also note that PNGs are being sent as text/plain.
Are there any other changes except for mime.types that we need to do through console or in any of the obj.conf or magnus.conf file.

yes there are two instances on that machine, the changes to mime types was done through console for both the instances and both the instnaces were restarted including the Admin server. However, we will still see content being served text/plain. Please help, if you want I can send you the obj.conf, magnus.conf and mime.types files so that you can take a look.

Volume changes not taking effect in nested sequence

Sometimes when I make volume changes to a clip in a sequence the change does not carry over to the master sequence that the original is nested in. What am I doing wrong? I am double clicking on the nested sequence in the master sequence to open it before I make the change to it.
Mac OS X (10.3.8)

I'm not sure it applies to your case, but I had similar problems with video rendering: changes to the nested sequence sometimes didn't appear in the nesting sequence, and attempt to render didn't work because ... there was nothing to render according to FCE.
Then I forced FCE to render: I first selected the nested sequence (in the main sequence), then I first applied "Disable Clip" (contextual menu) and then "Enable Clip", and finally the render bar changed to red (or orange), meaning it needed rendering. I rendered, and all changes in the nested sequence appeared in the nesting sequence as well.
Maybe it works also with volumes in your case...
Piero

Weblogic 8.1 SP4 Admin Console JDBC or Start-up changes not taking effect?!

Gents..I have an open case with BEA on this one but wanted to get some immediate help here. I am trying to make changes to my JDBC pools to check the connection pools (reserved, created, & released) however once I check the boxes and click "Apply" then restart WebLogic the changes I made just revert back to as if I never made them?! This is the same case for when I try to undeploy a start-up class in the Admin interface. Permissions on the config.xml look to be writtable by the user who is running the weblogic process. Also after making the changes I only see a 1 byte change to the config.xml and dont see the changes (undeploy etc) actually being made?!
Any help would be greatly appreciated!
Thx
Cody

I did a reinstallation and the problem didnt re-occur. So one neednt work on this problem.
Priya

Account layout change not taking effect

I copied the account default layout to my own, and tried to remove all the campaign info that
won't be implemented. However, it still shows up even though I've attached the new layout to my profile.
Is there something I'm missing?

Maybe yor personal configuration is different and it takes the place of the default donfiguracion (the profile one).
To view that navigate to My configuration / Personal Page Layout.
Regards, Kim.

Changing logical system name on ECC

Hi,
We have made copy of production to our test environment. Next, we created a number of copies of the test environment. We now want to hook the copies up to BI, XI etc. where we don't have multiple test environments, which means that a single BI test instance will support several ECC test instances as an example. This means that our ECC instances will have to have their logical system name changes changed in addition to the obvious SID change. We have a fairly comprehensive landscape with GRC, XRPM, BI, SolMan, CRM connected to our ECC instance. What areas of concern would you consider important to test once the logical system name changes are done? We are looking at the ALE, RFC connections, BI connections. We included the [help.sap.com information |http://help.sap.com/saphelp_nw04/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm] in our thinking, but since that did not really explore landscape wide issues....
Thank you,
Mike

Hi
As prelim checks:
Check if these changes are maintained in SCC4 client details as well, and check if all the RFCs are working fine.
Regards
Rahul

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

SLD Logical System Name Changes not taking effect in IDOC

Similar Messages

Maybe you are looking for