Changing system name in copied function

Hi Guys, I have copied a bunch of functions, however the system is not allowing me to change the System Name in Actions tab.
Can anyone help?
Thanks

First and foremost: I'd say this is not right - please open a customer message.
I'm guessing what you want to do is have the same TCodes and Objects used in risk analysis for a new system you're adding.
If this is the case, copying the function is not the right approach. You's either do that by adding the TCodes for the new system to the existing function, or - MUCH better - use a logical system and just add the new system there.
Copying a function may be useful for building organizational risks, i.e. risks&funktions that have a direct link to a certain part in the organization.
Frank.

Similar Messages

Change system name? 11.5.10.2+

Hi,
Is it possible to change the system name of an instance? What does it affect?
Do we do it just by changing the name in the context file and running autoconfig?
I am asking this question because, after a clone we dont usually change the system name but if we want many ebs envs monitored from enterprise manager, the system name must be different

Hi,
What I provided you is a quick method to do the needed.
If you need the official one, then you have to follow these documents:
Rel 11i: How to change the hostname and/or port of the Database Tier using AutoConfig (Doc ID 338003.1)
11i: How to change the hostname of an Applications Tier using AutoConfig (Doc ID 341322.1)
Regards,
Bashar

Change role name after copying

I copied a role (Business Explorer) and want to rename the role.
Changing the name does not help, because only changes to other languages than the original language are taking effect.
Changing the ID is possible, but there I am not allowed to change the name.
How can I change the name of the role in the original language?

I found the solution. I created the role in language "EN".
I wanted to have the name change in language "DE". Therefore, I had to translate the role name.

SA520, change system name

Hi,
is there anyway i can change SA520 system name? i am using v2.1.18 firmware.
i am refering administration guide but it doens't mention, please adivce
Thanks
Noel

hi wei,
ya, this is it.
thanks for the guide

Changing system name...

Sorry, but I'm VERY new to a mac's and my co. gave me a macbook pro to use but whomever had it before me, his name is attached at the 'base level' of my system. For example, i sign in under my own login and have my own home but when I print a calender page from Entourage it says the other guy's name at the bottom. And when I turn on the computer it says "john doe's macbook pro' Can anyone tell me how to change this? I could ask my IT dept. but I would like to try and do it myself. Thanks!

It's in the Sharing system preference. Just change the Computer Name to whatever you want it to be.
Regards.

Copy function issue.

Hi,
In my actual cubes, i have data for the 12 months ie from 01.2006 to 12.2006,
I created copy planning function and in characteristcs usuage "Create Row"
From change----T0 Change
1. Calyear--2006--
2007
2. Calmonth--01.2006 to 03.2006--
01.2007 to 03.2007
3. Vtype--10--
20
4. Version--0--
1
5. Infopro--Actual--
Plan
When i execute the copy function. I am getting the value No of rows *3
ie.
2007-01.2007----
$1000 (Actual Jan value)
2007-01.2007----
$1500 (Actual Feb value)
2007-01.2007----
$3900 (Actual March value)
2007-02.2007----
$1000 (Actual Jan value)
2007-02.2007----
$1500 (Actual Feb value)
2007-02.2007----
$3900 (Actual March value)
2007-03.2007----
$1000 (Actual Jan value)
2007-03.2007----
$1500 (Actual Feb value)
2007-03.2007----
$3900 (Actual March value)
I was expecting only one line for each row from actual to plan cube
2007-01.2007----
$1000 (Actual Jan value)
2007-02.2007----
$1500 (Actual Feb value)
2007-03.2007----
$3900 (Actual March value)
How does the system perform the copy function. Is it not row by row as per the result. Can anyone explain me how it calculates?
Thanks
Annie
02.2006----

Hi.
It is expected result if you use range in Calmonth.
You have to map one-to-one if you want correct result.
Just add 2 additional rows in copy function for Calmonth (in toal you should have 3 rows for Calmonth) and in each row map monthes accordingly (01.2006 to 01.2007 etc).
Regards.

Copy function simple question

Dear all,
i need to copy values from 2008 to 2009,
from version 0 to version 1.
in my aggregation level i have equipment type and months.
when i create conditions do i have to write down all conditions.?
should i just write :
from 2008 version 0 to 2009 version 1?
or:
from 2008 version 0 January EQTYPE1 to 2009 version 1 January EQTYPE1
from 2008 version 0 February EQTYPE1 to 2009 version 1 February EQTYPE1
from 2008 version 0 March EQTYPE1 to 2009 version 1 March EQTYPE1
from 2008 version 0 April EQTYPE1 to 2009 version 1 April EQTYPE1....
thanks

Hi,
In your aggregation level you have to include year and version as well.
then include Year and Version in "Fields to be changed".
If you are having only months in one of your characteristics to denote Jan, Feb etc.. then you don't need to include that in "Fields to be changed" and in the Copy function you can simply write
"from 2008 version 0 to 2009 version 1"
but if you have year also in your month characteristic for eg. if you have taken Fiscal Year / Period to denote your months where year is also part of the key then you have to map the old values of months also to new values in the copy function by writing January 2008 to januray 2009 and consecutively for all months .
You don't need to include Equipment in "Fields to be changed"
Regards,
Deepti

Change logical system names after system copy

Hi!
We successfully installed SAP ECC 6.0 system as system copy.
All the logical system names of old system have been copied to new system.
Question
What is the approach to change the logical system names for new SAP system?
a) just via tcode SCC4
b) via BDLS
c) other tcodes, reports
Thank you very much!
regards
Jürgen

Hi,
Go though the system copy guide.
http://service.sap.com/instguides
After system copy,
If you need to change logical system names in the system that results from the copy, change the logical system names as described in SAP Notes 103228 and 544509.
https://service.sap.com/sap/support/notes/103228
https://service.sap.com/sap/support/notes/544509
Before running BDLS to change the logical system name, you have to define the correct logical system name in the new copied system. in tcode BD54.
- while running BDLS, execute in background.
Regards,
Debasis.

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

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 after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2) If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3 the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

Logical System name in RSA7 Delta Queue wrong because of BW System Change

Hello All,
we changed our BW System landscape. Before we had one BW development system (System ID: DBW) and now we are using BW development system (System ID: EBW).
Now we face the problem, that in our R/3 system in the delta queue the wrong / old development system is written (DBWCLNT100), but instead of this there should be EBWCLNT200.
Has anyone of you got a clue where we can change this?
BR
Ilona

Hi,
hope you can do the client copy function to transfer the things from one client to other client no.
before doing the operation. please read the oss note carefully
Please refer to Note 552711 - FAQ: Client copy - subsequently See Note 557132 for further information.
and also check these threads
Remote Client copy error
how to do remote client copy ?
Regards
Harikrishna N

How to change or rename the logical system name T90CLNT090 IN BI 7

HI Expert's,
i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
because of this i am not able to create the source system between r/3 also.
so how to change this source system name for T90CLNT090.
regards
harikrishna N

Hi,
Pls follow this OSS note : 325525.
Note 325525 - Copying and renaming systems in a BW environment
Summary
Symptom WARNING: THIS NOTE HAS BEEN REPLACED. FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
           Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
           Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
           Reactivate all partner agreements that carry the new logical system name after renaming.
Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
           Solution scenario 2):
If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                    Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                    Reactivate all partner agreements that carry the new logical system name after renaming.
Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
Scenario 3) You want to copy a single BW system of the group by database copy.
Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                     Solution scenario 3)b): See Note 184754.
Scenario 4) You want to copy a single source system of the group by database copy.
Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
           Solution scenario 4)b): See Note 184322.
Scenario 5) You want to import a client copy in a source system.
           Solution scenario 5): See Note 325470.
Thanks & Regards,
Suchitra.V

Change Receiving System Name in BD64

Hi folks,
               We have our production instance and QA instance; we have copied all data from Production to QA ENV (Client Copy). After that when I login in to QA system I saw in BD64 all the system pointing to receiving production system. I ran BDLS ( transaction ) which convert production logical system name to QA logical system name in tables and as well as in SCC4 transaction.
I again went to BD64 and I noticed after running BDLS my production system name replace to QA system name. But Receiving systems names are still pointing to production systems. I know that BDLS just change the sending system logical name not receiving.
My question is that how I can change or modify the receiving system production names to testing name. Is there any way or program?
I try to change the receiving system name but its not letting me change. You guys have any idea how to change the receiving system production name to test name.
I dont want to create all distribution model names with test systems as I have 30 distribution models and client copy is keep on going after every 1 or 2 months.
Please help me in this regards.
Thanks

The OSS notes just tell about the BDLS. I already done with BDLS Scenarios is like that say we have one distribution model name in Production
Model name = ZXYZ
(Sender system) Production system name = PRD_123
(Receiving production System in UK)      = PRD_UK
These above are the setting for Production client.
We copy data from Production to Quality, so its copy all the data and Distribution name in QA ENV
So now my QA looks like
Model name = ZXYZ
Sender system) Production system name = PRD_123
Receiving production System in UK)      = PRD_UK
After that I ran T-code BDLS and give logical system name = QA_123, then when I go back to BD64 the model is looks like following
Model name = ZXYZ
Sender system) Production system name = QA_123
Receiving production System in UK)      = <b>PRD_UK </b>
But PRD_UK isnt change because its the production system for receiving one , so Now I need to modify <b>PRD_UK to QA_UK in BD64</b> , How Ill do it ?
I am trying to change receiving system but it doesnt allowing me.
I hope, now I made my self more clear.
Thanks in Advanced.
Bye
Message was edited by: Suleman Javed

Changing system name in copied function

Similar Messages

Maybe you are looking for