DW Workbench - Source System : Object Information

I recently applied some bi support packs through spam, and I realize now in my BW Workbench Source Systems
under Modeling, the active/inactive sign under Source System : Object Information column is no longer showing,
which, usually indicate whether the connection to the source system is ok or not.
Does anyone know what configuration is changed?
Thanks.
Edited by: BI Junior on Jul 16, 2009 8:04 PM
Edited by: BI Junior on Jul 17, 2009 2:36 AM

Thanks Mohan Kumar,
I check the source system, it is ok.
However, under that column, I used to have a active/inactive symbol which will tell me whether
the connection is ok or not, now the symbol is gone, so I have to check to see whether the
related source system ok or not.
Could you see the symbol in your system? My BI7 ides was SP70009, now I updated to SP70016...

Similar Messages

Locationg source system object transport request number in target system .

Hi,
After the object is pushed from source system to target using SCC1 for cross clients but same systems or STMS for cross-systems, if we want to see the object's source system's transport request number in the target system, how can we see that ?
Regards,
Rajesh.

Hi Rajesh
If my understanding is correct you want to know the source server in the target system( i.e where we have transported).
For cross-system objects, as you know we use STMS to transport them...
In the target system:
1. SE10
2. Click on Transports button.
3. Select the required request and expand the node.
4. You will have the first one which has log only for Export.
The node with only Export log is the source system...
Hope this helps...
Kind Regards
Eswar

How to delete a source system in BW?

Hello All!
Can anone please inform me about the procedure to delete a source system or inform me in which document i can find this information. Actually i wish to assing my newly installed BW3.5 system to a new logical system (i.e) its currently assigned to some other logical system where it has ME as default source system. to change the logical system we need to delete all the source systems in the old logical syste. So please explaing me how to delete the source system Myself(current BWsystem). there is no data and no data sources existing in the system its abosolutly fresh.
Thanking you for help in advance
with regards
Ashwin Kumar Gadi

Hello Roberto!
Thanks for ur response. But there bo such delete option available under the context menu for the source system for the Myself source(current BW). only change buton appears but when we click that it say changes are no posible. Is the any other way to delete it manually.
with regards
Ashwin

ECC6.0 upgrade and BW steps for mapping the new ECC6.0 source system

Hello gurus
We are upgrading from R3 4.6C to ECC6.0. We use BW 7.0 SP 18. We will create the new ECC6.0 source system in BW, replicate metadata and everything. The question is how do we copy or reassign the existing objects pointing to our current 4.6c dev system (transfer rules, transformations, infopackages, process chains) to point to the new ECC6.0 dev system ? As a note, we also need to keep the current 4.6c source system objects until go-live o ECC6.0.
What is the common practice in such a case ? I am sure we are not unique...
A prompt response would be appreciated.
Thank you all.

So the plan is to copy dev R3 and upgrade that - then Q r3 copied and upgrade that - then upgrade directly prod R3?
If so - then if it were me - I would firstly prove all this in a sandbox environment where BW dev points at an upgraded sandbox R3 ecc
ie same logical system
Then once that is proved I would organise downtime of BW development for a few months whilst the d-q-p ecc happens
Then when they copy dev r43 to ecc r3 i would then just point BW dev at the new ecc box and go from there (ie clear the deltas - change the logical system name to the new ecc box - replicate meta data - transtru all the datasources - run the process chains nothign to worry about)
However if you cant afford the down time - you may have to have an alternative transport route - ie copy dev BW to a another dev bw box and have an alternative path to production for issues
Then once everything is upgraded redo the changes through d-q-p to get the transports back in line (thats what we did)

ERROR - no available datasource for source system exist

I tried to load the master for 0Bill_Type
1) Install infoobject business content and Create infoobject
2) Activate datasource in R/3
3) Replicate datasource
4) Assign infosource ---> the error said no available datasource for source system exist
When I go to source system--> Object overview --> I don't see anything at all?
Please advise what went wrong ?

Hi Pandadda,
I think you have not transferred the APPLICATION COMPONENT HIERARCHY yet. If not, then do the following:
1. In your R/3 system execute TCODE = SBIW.
2. Go to BUSINESS CONTENT DATASOURCES
3. Execute TRANSFER APPLICATION COMPONENT HIERARCHY by clicking the CLOCK.
Replicate you datasource then check it on your BW system
R,
Adwin

BI Content collecting objects from wrong/old source system??

Hi Gurus! Lovely day here on the westcoast of Sweden - springtime is coming!
I have selected an infosource for installation in trx RSOR. I also want to pick up some objects in the dataflow before and after that specific infosource. So I guess the system keeps trying to collect metadata from diffrerent source systems that we have assigned.
I don't know the complete history of the systems - other than it's a bloody mess. We have right now a ECC 6 system connected to BI - but before that we had an older version connected (I guess 4.x something) on a diffrerent server.
Somehow the collection process picks up some data from the ECC 6 system - but sometimes it asks for a login to the old system as well.
This is my problem. I don't have an issue with logging on to the old system - because I have all the necessary rights to do that. But I don't want BI trying to collect metadata from our old system. So somewhere there's a pointer of some sort to the old system that I need to delete....
The old system is not visible in the "source system assignment" view so I can't really find out where to change this settings....
Any ideas??

It's probably so. Would I still carry out the instructions Andreas gave me for checking this? Or should I just delete everything and do it all over again, just to get the connections straightened out?
I'm more or less the only one at this point using the system - as it is a kind of sandbox environment. So extreme measures is not a problem

Prevent objects being transported for Sandpit source system

Hi there,
We have a 3-tier systems landscape for BI: DEV, QAS, PRD (we do not have a sandpit BI). In our R/3 development system we habe two clients which are both setup as source system for BI DEV. One of the clients in R/3 DEV serves as sandpit in that system and objects can't be transported from it. However, since this client is connected to BW, objects related to this source system can be transported from BI DEV. We want to prevent that, so only the objects in BW DEV for the real R/3 DEV development client are allowed.
Is there a way in BI to configure a source system in such a way (other than via security roles/profiles), that objects related to this source system can't be transported?
Cheers.

Sander, you should post this in BASIS also. By posting in both the forums, you have a better chance.
In case BASIS folks say that they cannot stop this, try this work-around.
In BWQ, in RSA1, there is a Source System Mapping in one of the tools menu. There, your DEV is mapped to QAS, etc.
There, you may have your R/3 DEV mapped to R/3 QAS.
See if there is an entry for your R/3 Sandpit/Sandbox. If there is one, leave the mapping for it as Blank.
See, the only Objects that are related to Source System in BW are InfoSource-DataSources. If there is no mapping for SOurce System in BWQ, then the transport will fail.
This is just a thought.
Uday-Ram Chamarthy

Test System (BQ1) Objects showing up wrong Source System after Transport.

Hi Experts,
We are working on IS-U BI7.0 Project. We have finished with our Development and have transported the DataSources, Transformations and DTPs from Development (BD1) into Test (BQ1) Systems.
We have entered values in the Conversion of Logical Source Systems correctly.
When we select the DataSource and Click Object Directory Entry from the Extras Menu, we found that the Original Source System is defined as BQ1 instead of BD1 (Development System), which is where the Object is getting Transported from.
We have implemented an SAP Note:1008633 (Incorrect Source System after Transport (RSTRAN 514) but couldn't resolve the issue.
We basically want all the Objects in the BQ1 (Test System) showing the Original Source System as BD1 (Development System) but only the DataSources and it's connected Transformations and DTPs are originating from the BQ1 (Test) System itself (The Transformations when Transported from BD1 to BQ1 are Transported with a different Technical Name which is very strange).
Had anyone faced similar problem and if so, what was the effective solution implemented.
Any help in this regard is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.

It is resolved by our Basis.
Thanks,
Chandu

Source System Dependent BI Objects

When working with Source System Dependent Objects like
1) DataSources (based on source system ABC)
2) InfoPackage (based on source system ABC)
3) DTP (source is datasource that is based on source system ABC)
Question 1)
Once we create the obove objects in DEV system.
If we update the IMG activty in QA (Source system conversion after transport).
and transport the above objects to QA system.
All the above objects should be available with new source system in QA? Is this the right way to do it?
Question 2)
Once we create the obove objects in DEV system.
If we DO NOT update the IMG activty in QA (Source system conversion after transport).
and transport the above objects to QA system.
Some of the above objects are not available with the new source system?
Workaround: Go to RSA1 (Top Menu -> tools --> they are couple of options where we can enter 1) source and target source system info AND 2) do a check, activate and replicate source systems.
After this some more objects are visible but not all? Is there any other way i can complete the conversion?
Question 3) I tried the below in an other landscape
Once we create the obove objects in DEV system.
we DID NOT update the IMG activty in QA (Source system conversion after transport).
and transported the above objects to QA system.
FYI: All objects with source system in QA are available. I am wondering how the source system conversion took place?
Question 4) When we enter source system for DEV and QA in QA system, Do we need to enter even PC file source systems?
Example:
1) ABC in DEV = BCD in QA
2) PC_FILE in DEV = PC_FILE in QA
Thanks for your help.

Below are the following ways to do the mapping in Target System for Sourse System Conversion:
1) rsa1->tools->source system mapping OR
2)rsa1->transport connection->'conversion of log.system'(yellow box with 'x' and 'conversion' icon) OR
3) spro->bus info warehouse->transport settings->change source system name after transport (transaction rslgmp) OR
4)maintain table RSLOGSYSMAP (sm30)
Que1.
Yup
Que2.
if no maintenance done, system will transport as the same source system name. You have to convert everything manually...cumbersome process.
Que4.
Normaly for flat file we use the same name, to avoid any warnings, we just maintain the 'conversion' with the same name

How to transport source system dependent objects

Hi everybody,
I've read several questions about how to transport source dependent objects between systems and I still don't get whole picture
say I have BWDEV attached to R3DEV and
BWQA attached to R3QA
and I want to transport transfer rules from BWDEV to BWQA
1) should I create, by hand, the source system R3QA in BWQA and replicate its datasources in the first place?
2) or it has to be transported from BWDEV and "some how" converted in BWQA
3) where does the source system name mapping has to be done: in BWDEV, BWQA or in both
4) in order to do the mapping of names in BWQA I need to create the corresponding R3QA, otherwise I don't have the entry under TargSrceSy when executing tc RSLGMP
I really apreciate an step by step process for the above scenario
thanks a lot

Hi Juan,
Let me try to shed some light. Before you can transport dependent objects in the BW side, you have to make sure that the necessary dependencies in the R/3 side have already been transported. For example, if you have a datasource in R/3, you have to transport that from dev to QA first (before you transport anything in BW). Then, in the BW QA box you have to replicate the datasource before you can transport any BW objects in the BW QA. Then before transporting anything to BW QA and after replicating the datasource in the BW QA you have to go to RSA1->Tools Menu->Assignment of Source System to Source System ID menu item and make sure that R3DEV is mapped to R3QA. It is only after all the said checks have been done that you can transport objects in the BWQA.
Here are my answers to your questions:
Q1: This depends on your datasource. Some datasources can be transported. Some can be created in the QA box itself. But in both cases, you have to make sure that DataSource exists in R3QA and then replicate it in the BWQA.
Q2: The conversion follows the setup in "Assignment of Source System to Source System ID" in RSA1.
Q3: The "Assignment of Source System to Source System ID" in RSA1 has to be done in the BWQA.
Q4: Yes, you have to setup the R3QA Source System in the BWQA.
Hope this helps.

Virtual Transport Path to move BI source system dependant objects.

Currently, our BI Test system (which contains all Transported Objects from BI Dev) is connected to ECC client 100. We want to change BI connection to different Client i.e ECC 115 (this client contain better test Data). We have removed BI connection from Client 100 and connected to Client 115. But our entire Source System Dependent Objects in BI still point to ECC Client 100. To change these Objects to point to the correct Client 115, we are executing the following steps:
1 Remove Source System ECC Client 100 from BI2
2 Connect New Source System ECC Client 115 to BI2
3 Ensure that New Source System Connection to Client 115 have been set up
4 Create a virtual transport path within BI2 for re-import into BI2 queue for the ? Transport Package
5 Open BI2 to assign user authorization in order to be able to create a transport in BI2
6 Copy Source System dependent rules & create Transport
7 Change the Source System Assignments on the target client
8 In SE09 - check that only the required source system has been copied
9 Move the transport in through the import queue
We are stuck at step 4. Basis team says it is not possible to create a transport path from BI2 system to the Virtual System (in the same BI system) and move it. But I am pretty sure that this can be done as I did this earlier in my previous project. This is something related to Basis so I cant help them.
Do you have any idea, how this can be done?
Any help will be highly appreciated.

Hi
I do not understand few things :
- why did you remove the source system ?
- what do you mean by BI2 ? It is the same QA system as before....So why do you need to create a virtaul path for transport ?
The steps you should have followed is to use BDLS transaction to rename ECC100 to ECC115
The source dependant objects would have been renamed automatically.
By the way, you now can start over from your dev and collect the source system dependant objects
Transport the request in QA, paying attention to change the transcodification table to target ECC115 and not ECC100...
Hope it helps
PYG

Importance of "Source System Assignment While transporting the objects

Hi Friends,
What is the Importance of "Source System Assignment While transporting the objects. And when do we select this icon. what is the exatly significance for this.
Thanks in advance for all......
Regards,
Ramesh.

HI Rameshpennabadi ,
This option is only enable for object like transfer rule, data source and IP if you want them to assign source systems,other wise the dialog box Choose Source system by Default? appears.
Thanks,
Deepak

How to change original source system of objects at one time

Hi, experts !
I installed extra devlopment server using system copy of orignal
delveopment system.
We have planed that new objects applied to orginal server after developing
finished on extra devlopement server.
The problem is we can not modify or add old objects for specific
package because orignal source system is different
and I know this is SAP policy.
Of course original source server can be changeed on t-code SE03 or
function module TRINT_TADIR_MODIFY
but it should be applied to every objects. This is big job to BC admin.
Is there any solution to possible it at one time?
Best Regards

You can transport all relevant packages from the old to the new development box including a change of the original system using a special transport request of type "relocation of complete package". Check with your system administrators.
Please close your similar post here:
How to change original system SID to objects by batch?
Thomas

ST22 information at Source System.

Hi ,
        mine is a webservice to PI to proxy scenerio. I prefer a synchronous process, but I have the choice of making it asynchronous also.
   However my requirement is , if information sent from webservice reaches sap abap proxy through Pi and then throws a short dump in ST22 of sap, then source system i.e. webservice will never get to know about the same. Is there any option to check it/ tracce it??
Experts, your comments pls .
Regards,
Arnab.

Hi Raghu ,
                     your concept appreciated. I planned this long back. But there was a catch. I noticed in ST22 , most of the short dumps have an exception , but there are a few, which dont have exception. Strange but true. You know what, ultimately, we are moving into this type of coding, but the hitch lies in the mind , if there is a dump, without an exception , and the cllient is unaware of the same , we miss the business !!
   Thanks and Regards,
Arnab ,

Deletion of data objects from already not existed source system

Hello, Everybody,
In BI 7 i had QASCLNT500 source system and have been created datasource with transformation. Later QASCLNT500 was deleted or changed (i don't know very well) to QASCLNT300, but old datasource with transformation is still in new system. When i try to delete these objects i get a message - "Source system QASCLNT500 does not exist".
Could you give me a suggestion how can i delete that datasourse and transformation?
Thanks in advance.
Best Regards,
Arunas Stonys

Hi,
It depends on your requirements whether you have to keep the history or not.
If you delete the data from your info providers, you have to reload everything from scratch.
If you want to delete the data from all
1. first delete the data in data targets such as cubes, DSO's or ODS then
2. master data
use these programs to delete from se38
-> rsdrd_delete_facts - for Cubes and DSO or ODS
-> rsdmd_del_background - for master data in background
-> rsdmd_del_master_data_texts - for master data right away
manage your master data info objetcs after the deletion, if you still find them....
go to se14 and delete individually each and every table such as attributes, texts, sids, hierarchy.
hope it helps you better.
But I dont recommend you to delete try to load full repair options for all yur loads

DW Workbench - Source System : Object Information

Similar Messages

Maybe you are looking for