BW Development Logical Name Change Impact

Hi,
what is going to be the impact on our BW system (extraction / modelling / reporting) if we change the BW logical name.
Example:- BW Development current logical name is BWCL005
New Name change to BW005.
Can you please help
Regards
Rajiv

some of the impacts i can comment on are as above.
1. wherever u have hardcoded logical name, there u have to modify to new name.
2. regarding the RFC connection with other servers make sure there is there is 2 way communication with the every server, this is basically a BASIS task and needs to confirm with great care.
hope it helps.
kindly assign the points if it helps.

Similar Messages

Source System Logical Name change

Hello,
We are refreshing our R3Qas system with a copy of our R3Prd system. As part of this task our R3Qas logical name is changing from QASC230 to QASC200.
I am at the point in the refresh where I am beginning tasks on the existing BWQas system.
I Right Click on the source system representing the R3Qas system "QAS client 230" technical name: QASC230. I choose 'Restore' I then provide the logon information but the system it jumps to is the Old R3Qas not the new R3Qas.
I know that it is jumping based on the RFC, So I assume I can change that RFC to jump to the new system, what do you think? Also what about the Source System name an technical name, will it always be QAS Client 230 and QASC230 or can that be changed to reflect the new name of QASC200?
Thanks for your advice and assistance!
Nick

Since the BWQ system was already an existing system that was attached to the previous R3Q system, this task was essentially busy work.
The change that occured was that the existing R3Q system (Physical Name: QAS01 Logical Name: R3QASC230) was being replaced with a new R3Q system (A copy of Production was used) (Physical Name: QAS02 Logical Name: R3QASC200).
The actions that I needed to take to connect BWQ to the new R3Q follow:
1. On QAS02 visit TX SE37. and run RSAP_BIW_DISCONNECT, Choose 'Single Test'. For I_BIW_LOGSYS: I provided BWP001 which corresponds to the logical name of our Production BW system. For I_OLTP_LOGSYS: I provided R3PRDC200 which corresponds to the logical name of the QAS02 system (this system). I then Click 'Execute' and 10 seconds later this step is done.
2. On QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide BWP001. For the 'New Logical System Name' provide BWQ001. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the 'Mapping System Name'.
3. Again on QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide R3PRDC200. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (BASIS already did this step so a message appeared to that effect)
4. On the BWQ box visit TX: BDLS. For the 'Old Logical System Name' provide R3QASC230. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the at the prompt and run.
5. On BWQ create new RFC's based on the old ones to point at the new QAS02 system. Modify the old ones with an X in the 'Target Host' so they do not function.
6. Open up the BWQ client in SCC4. (or perhaps try SM30 to modify the table in the next step)
7. On BWQ visit TX: SE16. Tablename: RSLOGSYSDEST. Change the 'Old' reference to the QAS box to the 'New' information. (ie: R3QASC230 became R3QASC200).
8. On BWQ visit TX: WE20. Expand 'Partner Type LS', Select 'R3QASC200', click the classification tabe, change the 'Partn.Status' from I to 'A' and save.
9. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. Click 'Only Activate' when prompted. you will then get a termination message regarding the port description.
10. On BWQ Back at WE20: Expand 'Partner Type LS', Select R3QASC200, double click on RSRQST. Under 'Outbound Options' click the drop down for 'Reciever port' Select the 'new' correct system and 'Save'.
11. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. You will get a prompt to Use or Check, choose 'Use'. When prompted about 'Connection cannot be used' click 'Delete'. Logon again as ADMIN account, Click 'Continue' when you get the 'User exists...' prompt. Click 'Replicate as well' when prompted. you will then get a termination message regarding the port description.
You should be all set now!
Nick

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

Report issue , logical name of the system has been changed

Hi
Recently our system has been upgraded to ECC5.0. In a particular report while drilling down we get error. The error says the original doc can not be shown as it belongs to logical system ( DRH-123) . Now we know that this logical name of the system was in old box . The new logical name is DRH-100 . We are saying it's a basis issue and the basis team is saying it's FICO issue.Has any body encountered this type of problem. ? In my report i have never mentioned logical name of the system.Hence unable to understand it. But so far what I have understood , that the each box has been partioned and given a system name which is called logical name.Now that logical name they have changed in new box.My initial response was change the logical name but basis says that is a big task and more over it has been a while when they changed it.
Gurus, Kindly shed some light on this mess.
Thanks in advance
Satya

Which report are you pulling out? T-code?
This link has some that may help you:
www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli
Do CTRL+F to find Logical Systems
If the link doesnt work use the following keywords and google it, shoose second result: EDI IDOCS interface axel angeli sap
You may also want to get in touch with the person who was involved in developing LS. Talk with your ABAPer, they normally have an idea about these things (well atleast my ABAPer knows!)
Message was edited by:
Vj

I have a siebel application in english and i do have built the framework in oats,now if the application changes to arabic , do i need to change the logical name of the object?

Hi
Iam currently working on OATS automation for siebel application.
I am having the marketing site in siebel in english language currently and i have developed framework for the same.
Now, customer is changing the marketing site from english to arabic, now my question is will the logical name of the objects change?
do i need to again build the Object repository for arabic as well or will the logical name remains the same?

Hi,
If you developed framework based on objects id, then that will work.
If you used text of objects to identify them( say example click on a link with text 'SignUp') then script will fail - fail to find object with text mentioned in script
Regards,
Deepu M

Side effect of SQl server upgrade from 2008 R2 to Server 2012, logical name of log file changed for one database

I came to know that name has changed when I tried to shrink the file. Here is the error message I got:
Shrink failed for LogFile "Tfs_TESTTFS_Log'. (Microsoft.SqlServer.Smo)
Additonal information
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.COnnectionInfo)
Could not locate file 'Tfs_TESTTFS_Log' for database 'Tfs_TESTTFS' in sys.database_files. The file
either does not exist, or was dropped. (Microsoft Sql Server, Error: 8995)
This is test environment upgrade and I checked on production environment which is still on SQL 2008R2, shrink works fine.
Please help.

I did in place Upgrade.
Before Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: Tfs_TESTTFS_Log
After Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: TfsVersionControl_Log
Thx

Change Developer/Publisher Name

Dear Apple, my account going to expired soon, but I want to change my developer/ publisher name. Although I have the option to create a new one, but the current one Apple still owed 100 USD (you need 150 USD for checkout right?)
Please advice

I have no idea what you mean by " Although I have the option to create a new one, but the current one Apple still owed 100 USD (you need 150 USD for checkout right?)".
BTW, this is a user forum; you're not addressing Apple here.

BW / SolMan Logical System Change

Hello all, I am having a BW related issue and would really appreciate some advice. I realize some of this is for the solMan forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1.
I am embarrased I missed this section in the master guide the first time around. I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

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

Physical path and Logical name in File adapter

Hi All-
I am using a file adapter, in which i need to specify the physical path or logical path.
In dev environment my file adapter's input path is /c01/interface/dev/input, but in my test environment it is /u01/interface/test/input.
So everytime I have to change the path and deploy it in two different environment.
I am using unix environment, is there any way i can use some environmental variable $INPUT_DIR and use it in logical name so that in logical name i can use as $INPUT_DIR/input, where in dev $INPUT_DIR will be /c01/interface/dev and in test environment it is /u01/interface/test.
I have tried this but there is still some probelm, I want to know is the approach I am using is correct? or is there any other solution for it?
Regards,
Sreejit

Hi,
1. physical name: use a specific directory (e.g. /u01/....
2. logical name: use a LogicalDirectory like "InputFileDir" and rewrite this inside the bpel.xml
http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28994/adptr_file.htm#CACDEBBH
and
http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/appx_deploydesc.htm#CHDBDIIF
But what about creating a softlink like this on your testsystem:
ln -s /u01 /c01

Does mxctrllib provide a call which returns a reference to all the logical names in MAX?

I'm looking for a call that returns all the MAX logical names on a system. I would populate a drop-down box with those names to allow the user to select a name at program run-time. Currently I hard code a particular logical name as a string and init the session. This is not flexible. Thanks ...

The NiMxCtrl.dll which is the server for the mxctrllib objects is meant for National Instruments internal product use only. There is no documentation for developing 3rd party apps that utilize its functionality.
I'm not sure if you are talking about the IVI logical names listed in MAX or not, but if you want to know where you can get a list of these, they are in the ivi.ini file found in your C:\VXIpnp\Win95\niivi directory. Just parse this file to read all of your IVI logical names and setup parameters.
Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

Fwd engineering entity name changes to relational model?

I changed an entity name in my logical model after generating a relational model. But, I cannot figure out how to have SDDM (3.0.0.665) propagate this change to the relational model.
In the Engineer To Relational Model screen, if I select the changed entity from the tree view, in the Details pane there is a "Selected" check box next to the Name property (this line shows the discrepancy between logical name and relational name) but I can't check it. Under the Compare/Copy Options tab in that same dialog, the check box next to Name is checked. But, when I forward engineer the name is not changed.

BTW I just noticed that if I enable "Name Translation" then it seems to work. This is not at all intuitive or obvious, nor does it seem to be explained in the documentation.
According to the help:
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.

MS Access developer with a change of career, so need PL/SQL type tools pls

Hello,
I am a recent MS Access developer, my position went away, so now need to bone up on PL/SQL 101 sort of knowledge. I have very little SQL experience, so am starting from square one in my learning Oracle. I would like available to me to-the-point examples of code when working with Oracle data using SQL Navigator 5 as my "Enterprise Manager" type tool. I need to quickly understand the basics in creating\constructing Stored Procedures and PL/SQL statements, need examples of naming conventions in the code and what the conventions achieve for me. I don’t want full details, just more to the point info please, unless you feel the details will be very useful in my understanding of the dbase tool.
Any info that you are willing to share to get me up and going would be appreciated!

1) If at all possible, use plain SQL instead of PL/SQL. See the O'Reilly book 'Mastering Oracle SQL'. A very high percentage of procedural code developed against Oracle is caused by not understanding how to code in 'plain' SQL.
2) Learn Oracle PL/SQL - any book by Steven Feuerstein will do. Again, look at O'Reilly.
3) Learn to read the Oracle docco. See http://tahiti.oracle.com
4) Understand 'effective Oracle coding' by reading any Tom Kyte book (at http://www.apress.com)
5) Use Oracle's SQL Developer as your basic development tool, and Oracle's JDeveloper as the advanced development tool - JDeveloper has a PL/SQL debugger built-in.
6) Get very, very familiar with the available PL/SQL library API ... look for the Supplied PL/SQL Procedures and Packages manual for the version of interest. (Name changes with versions, but that should give you the idea.)

Manipulations with physical and logical names

Hello ppl,
Is there any way to see/change phisical and logical names of object in one place/screen? I mean I want to set them to different values and see that change, but without fuzzu, complex way of changing naming and propagate modes.
TIA,
Alex

Mark,
Under project, preferences (from the main console) you can set the naming and also the propagation method. That's what I hate to do :) However, thinking deeper I find it ok - first finish with modelling and physical names, than correct logical names as needed without propaation to physical.
Alex

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.
can anyone please give me the solution
thanks and regards
n,chakradhar

Also u need to delete the entry with the old logical system name in TABLE CRMPRLS in MM.
Check SAP Note # 765018

BW Development Logical Name Change Impact

Similar Messages

Maybe you are looking for