"Conversion of Source System names after the transport" : O

Experts:
Environment : BI 7.0 and SP 12
Tranports related to transformation rules are failing with inactive status...
Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
Everything looks fine to me with reference to actual techinical names of source/target system...
My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
OR do i need to create another entry with same source/target system and check the 7.0 box.
OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
Finally, please advise the exact steps that need to be taken here...pros and cons
Your inputs will be of great help....
Thanks,
BI
Message was edited by:
B I

Hi,
Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if your client is modifiable, if not you need to transport the setting from DEV. Go to
SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
you also need to maintain the Source system IDs .
Hope it helps.

Similar Messages

Conversion of source system names after transport

Hi gurus,
Please someone can tell me how to configure the "conversion of source system names after transport" in the BI system as my transport is not working on a new BI System ?
Thx in advance

Hi Firmin,
You can do this in RSA1 in tools under conversion of logical source system names.
Here you maintain the development system or the system used for development as the source system.
You will have to mention the logical name of the development system.
In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
Check the folllowing link for more informationn on this.
[Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
Hope it helps you ,
Best regards,
Sunmit.

Conversion of Source system name after transport

Dear All,
I need one clarification.
Say you have developed a fresh modelling in BW Dev server and your source system is R3 dev system. Now you need to transport all the request to BW Quality system but the source system will be R/3 quality system.
For this change of source system name we need to maintain some mappings.... From Tools menu there is an option to do this...
My doubt is in Production server how do we maintain the mapping...
Quality system ---> Production
or
Development system---->Production.
Hope i am clear....
Thanks & Regards,
Anup

Hello Anup,
The question you raised particularly is about the change of source system when your transports are alredy done. For this, i would like to say is that when you do any transports in the R/3 or BW front, the source system change is done only when :
1. It is done, when you have a single base system and different R/3 (source system)
2. If you have a single source (R/3) and a single destination (BW Quality), you do not need to map the source system.
Well, i case that is needed, you may do it via :
1. Go to RSA1
2. Go to Tools.
3. Tools -> Conversion of source system.
In the right most table column, provide the source system you need to connect with your BW system.
This will internally connect you with the specified R/3 system.
Hope it helps!
Neha.

Conversion of source system names --- error in transport

hi
i want to transport my object from Dev111 to Quality222
but the transport ended up in error 8
it gave the error...
Source system PRODUCTION333 does not exist
I am confused,
shouldnot it should give error related to Quality system ???
how should be the mapping in Source system names?
after research it seems it should be maintained in
RSA1-TOOLS-mapping of SOURCE SYSTEM NAMES.
i have following systems...
BW- DEV111 QUTY222 PDN333
R3 DEV121 QUTY242 PDN363
What should the entries look like in which system

Landscape is -Transport should be send from Deve-Quality---Production
BW....................................
DEV111 QUTY222 PDN333
R3.....................................
DEV121 QUTY242 PDN363
CAN you advise if the entries SHOULD look like below in Quality and Production System???
Quality system should have entries like:
bw DEV111.............. bw Quality 222
r3 DEV121................ bw Quality222
Production system should have entries like:
bw Quality222.............. bw Production333
r3 DEV242................ bw Production333
Q1 ......IS THIS HOW ENTRIES SHOULD BE IN Quality & Production system???

Conversion of source system names

Hello Experts,
After having some transport problem (transporting infopackages), I notice that the source system mapping is not the same in DEV compared to PRD.
Other than change log which was not turned on, is there any other way I can find out who or when was the last change to this mapping table?
Am I right to say the mapping entries should exist in all systems? My DEV currently only has 1 entry compared to 6 entries in QAS and PRD.
The source system underwhich the infopackage resides is not shown in the DEV source system mapping table.
Is this the cause of my transport problem?
Regards,
Mirella Russo

Dear Experts,
Thanks for the useful information. Points awarded.
Am I right to say that mapping in target system cannot be transported and is set directly in target system QAS, PRD via RSA1 and no mapping is required even if there are other source systems, like flat file source systems, when the source system name is to be the same in all systems? In this case, my source system is a flatfile. Does this mean I need not maintain it? The 'no mapping' warning received in transport log shows that the flatfile source system concerned exists in the target system but no mapping. As I do not need source system name change, can I say I need not maintain in the mapping table? I still cannot understand why the error come about.
Many thank you in advance.
Regards,
Mirella Russo

Transport Issue - no conversion of source system name

Hi Experts,
I'm desparetly trying to import an transport request containing a transformation into my PRD System . At stage of method execution it fails with RC=8.
Error MSG:
The DataSource MY_DS (MY_DEV_SYS) does not exist in object version A
in PROD MY_DEV_SYS should be converted to MY_PRD_SYS, entries in RSA1 are maintained.
MY_DS exists in active version in PRD. It seems like conversion of source sytem doesn't take place. Any ideas?
Thanks in advance
Joe
System BI 70, SP21

Hi Everyone,
I've experienced the same problem on a BW 7.01 system on Support Pack 6. I was able to solve it through implementing the following notes:
- 1412414 (SP24) Content is not generated/transport errors; and
- 1489612 Objects of the type DTRF deleted after method is executed (supplemental note to 1412414)
See my reply on the below message for further details:
Re: Source RSDS DS_CA_CLIFID DBW_150 does not exist
I hope you found this useful as 'solved with workaround' wasn't particularly helpful to me.
Cheers,
Campbell

Incorrect Source System name after System Copy

Hello Friends,
When we copied Source system from Production to our Qulaity system, the DTP s are still displaying Production Source system.
We are in BI7.0 SP13 . I have run TC BDLS to convert Old Source system to new Source system.
But still displaying Old source system .
Please help me with this Issue .
Any advice appreciated .
Thanks

Hi,
Take a look at OSS notes below.
o 184447 Building a BW-system landscape
o 121163 BDLS: Converting logical system names
o 369758 BDLS: New functions and better performance
o 524554 Storing destinations in the BW environment
o 325470 Activities after client copy in BW source systems
o 538052 Maintenance of Myself destination in BW
o 305527 Details for correct BW Source System Connection
o 325525 Copying and renaming systems in a BW environment
o 184971 Notes on BW source system connections
o 184754 Procedure after BW database copy
o 305527 Details for correct BW Source System Connection
o 547314 FAQ: System Copy procedure
o 140276 Error in source system assignment
Regards.

Conversion of source system while transport

Dear Experts,
We have following landscape:
BID (BI dev)
BIQ (BI QA)
BIP (BI Prod)
and
R3D (R3 dev)
R3Q (R3 QA)
R3P (R3 Prod)
For transport we have made following settings for
"conversion of source system name after transport":
In BID system (BI dev)
BID->BIQ
R3D->R3Q
Question-
-Where do I mention settings for production?
-Can I make folowing settings in Dev so that it works for all the transport?
BID->BIQ
R3D->R3Q
BID->BIP
R3D->R3P and no settings in BIQ and BIP environment.
-Do I need to mention below settings in BIP (BI prod)
BID->BIP
R3D->R3P
Thanks

Hello,
Please log into the system in which you are trying to import the transport in and go into transaction code RSA11 and then ino "Tools --> Conversion of Logical System Names".
In order to change the values the system needs to be modifiable and the person having the change access should be doing this (which would be the BASIS team if the security is set properly).
So, in BIP system in your case please go into the above path and maintain the entry for BID --> BIP and also R3D --> R3P.
The whole purpose of doing this is to make sure that the datasources which have the source system property get converted into the appropriate source system names when transported over multiple environments.
Please assign the points if this answers your question.
Let me know if you need additional information in this regards. If you don't have the access you can check if these parameters are set or not by accessing the view "V_RSLOGSYSMAP" in the system.
Thanks
Dharma.

Conversion of logical system names in queries

hello,
We have the following problem in our multisource model.
Constant values have been assigned in queries in development : for instance, in line 1, the profit center is restricted to the constant value D3/9000/TTBC600
D3 : development source system
9000 : controlling area
TTBC600 : Profit center code
When we transport the query, we were expecting a conversion of the source system ID in this constant value but it is not the case.
could you tell me if this is a normal behaviour??
If yes, it means that we have to enter constant value in hard code without reference to the source system ID (indirect input, you cannot enter more than the length of the object i.e. TTBC600 in this case) and this can be at the origin of conflict if we have same code in different source system.
Thanks in advance for any answer
OD

Did your transports move up ok to your target system?
I am asking because your problem could be your mapping of source system to source system ID is not set up correctly or your "conversion of source system names after transport" is not set up correctly in your target system.

Mapping of Source System Names

Hello,
Has some body done the mapping of Source System for "Transport" to go through which is done using the following steps:
RSA1 --> Tools --> Mapping of Source System Names(Conversion of source system name after transport)
You have to enter the source system name and target source source.
So if I have following Landscape
1) R3DEV -> R3QA --> R3QPROD --> R3Prod
2) BWDEV -> BWQA --> BWQPROD --> BWPROD.
What should be entries in the table
OrSource TargSrceSy
1) R3DEV R3QA
2) R3DEV R3QPROD
3) R3DEV R3Prod
4) BWDDEV BWQA
Thanks,
-Hari
5) BWDDEV BWQPROD
6) BWDDEV BWPROD
or
1) R3DEV R3QA
2) R3QA R3QPROD
3) R3QPROD R3Prod
4) BWDDEV BWQA
5) BWQA BWQPROD
6) BWQPROD BWPROD

Thanks A.H.P. So just a click clarification. My question is
So BWQPROD will contian
OrSource TargSrceSy
 R3DEV R3QPROD
OR
 R3QA R3QPROD.
Because my basis the transport path is as shown below.
 R3DEV --> R3QA
 R3DEV --> R3QRPOD
 R3DEV --> R3PROD
So dev will transport to QA,QPROD,PROD
Thanks,
-Hari

Wrong conversion of source system after transport

Hello,
We ve got a a transport problem in our 3-3 Landscape. Connections for extraction are only between same systems ( f.e. dev to dev)
BI Dev BI Test BI Prod
R3 Dev R3 Test R3 Prod
The conversion of source systems is on the BI test:
BI Dev becomes BI Test
R3 Dev becomes R3 Test
The conversion of source systems is on the BI Prod:
BI Test becomes BI Prod
R3 Test becomes R3 Prod.
With this it tells me the after transport (BI Test to BI Prod) of objects with source system assignement that the R3 Dev System is not known.
The transport before from the BI Dev to BI Test worked well without any problems.
We`ve got the BI Test and the BI DEV on the same host.
Has anybody got an idea what is wrong?
Thank you folks.

It must be R3D (dev system)
Something like following should be maintained in production
R3DCLNT100 R3PCLNT100 [Assuming R3PCLNT100 is your production system]
Don't forget to assign points,
-jayant

Transfer rules to the new source system not visible in Transport connection

Dear All,
Recently our source system has been changed from R3 4.7 to ECC 6.O. Corresponding to that all the activities in BI have finished successfully. All my datasources in 4.7 have been replicated in ECC 6 in BI and transfer rules re-assigned. I have also collected them in a Transport request.
Now when I am checking the entire flow in Transport connection, it shows me the transfer rules pointing to the old system only. That is, in RSA1 it shows the new system assignment. But in Transport connection not.
What I have to do so that I can crosscheck in Transport connection all my objects having transfer rules to new system ?
Regards,
Srinivas

I think you should check the source system assignment in the transport connection. It might have directed to the old sytem.
Cheers
Chanda

Mapping of Quality System (Source System) after the Transport

Hi,
We have two quality source systems like 300,400 in sync with the development ,to extract the data . I am transporting Transfer rule mapping from the development .After the transport to Quality , the changes are reflected in 300 . But I want to change it from 300 to 400 i.e.Transfer rule mapping should be reflected in 400. What is the transaction code used to change this mapping in BW System?
Thanks for your time.
Thanks & Regards,
Raja

Raja,
When you transport - you have a transport mapping in your dev system that tells BI which system connects to which system in the QA system for instance
FLAT_FILE in DEV could be Z_FLATFILE in QA - accordingly the datasources are mapped. Also the transfer rules are source system specific which means that you change the source system - the transfer rules will have to be recreated.
Instead what I am asking you is to maintain the mappings for client 400 in DEV and then maintain the mappings as 400 - 400 in the qa system and then transport the same. If your dev systems are linked to QA300 and your mapping says QA400 the same will hold good.. however if you have QA300 in dev to be sent to QA as QA300 and then change the source system .. it will not work since this will be seen as a source system change and you cannot change the same. You could try BDLS and try changing the logical client name ( I am not sure if it is BDLS ) or change the RFC connection parameters in SM59 but am not sure if it would work....

Conversion of source system after tranport

Hi
Im planning to to transport BI-Obejcts from DEV to QA . Where can i give
'conversion of sourcesystem after transport' and how can i give them.
can i give in DEV or QA .please let me know
kumar

Hi Ravi,
Log into your QA system. Go to RSA1 -
> Transport connection. Click on the icon Source system conversion or just press F8. Click on new entries in the next screen. Here just maintain the source system conversion. For example in Dev if the R/3 source system name is R3DEVCLNT100 and in QA it is R3QACLNT200 then in the original source system field enter R3DEVCLNT100 and in the target source system field enter R3QACLNT200. All the source system dependent objects like datasources, transformations etc which are assigned to R/3 dev system in BW Dev will be assigned to R/3 QA system in BW QA.
Similarly maintain entries for all other source systems defined in BI. Hope this helps.
regards,
Sumit

BDLS for conversion of logical source system name

Hello All,
I am trying to reassign a new source system NEW1 by replacing old source system OLD1 using BDLS in the source system.
But the NEW source system logical system name already exists as I created it . Can I delete the new source system and then use BDLS?
How do I make sure that the reassignment happens correctly?
And what precautions should be taken to avoid further consequences?
Regards,
NIKEKAB

BDLS does a pretty good job... Never had issues with it when using it... Always execute a test run, look for warnings or errors...
Yes, you can delete the source system before doing BDLS... I assume, since it is new, nothing is connected to it...
You always will have to check RFC connections, datasources replicas, rules, etc, once the conversion is done...
Make sure you take a look at note 886102, it has very good information and make reference to other relevant notes specific for BDLS, like 121163, 369759, etc... Read the notes carefully, follow the steps and you'll be fine...
Once everything is done and in place, you shouldn't have any surprises in the future... It's just normal maintenance...
Good luck...

"Conversion of Source System names after the transport" : O

Similar Messages

Maybe you are looking for