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

Similar Messages

G/L account picked for the "wrong" source system entry

Dear Experts,
in SRM 7.0, Classic Scenario, i am facing the following issue with respect to G/L account determination in the SC:
We have three R/3 systems connected to SRM. All these R/3 systems use the same Material Groups, but the G/L accounts are different in each R/3 system.
In the Table "Determination of G/L Account using product categories", i have maintained the repsective combinations. For each combination of product category and account assignment category, the respective G/L account is defaultet for the respective source system.
But in the shopping cart, the determination of the correct G/L does not always work. When a user enters the shopping cart initially with a line item that is accounted to his default account assignment category, than the correct G/L account for his source system is derived. But if he changes the account assignment category of the line item, than a G/L account from a "wrong" source system is getting picked up from the table.
I have checked the GUIDs of the product categories between "Comm_category" and "bbp_det_account" and they are correct.
What can be the reason for the picking of the G/L account from the wrong source system?
Can the note 1357871 bring the correction?
Thank you very much!

Hello Dima,
I think your problem comes from your source system for product category management.
Could you clarify one point: if you change account assignment category, does new G/L account have to be determined for same backend system too or not ?
If yes, correct new G/L account will be determined using your customizing (IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Account Assignment > Define G/L Account for Product Category and Account Assignment Category ).
If it does not work, log an OSS message.
If no, you need to switch value for each SC item field BBP_PDIGP-LOGSYS_FI from old backend source system to the new one. For this, use BBP_DOC_CHANGE_BADI.
Then, your customized G/L account definition for product category and account assignment category should be OK.
Regards.
Laurent.

Wrong Source System

Hi, Experts:
We moved transports for a new application from development into 2 QA systems (QB1 and QB2) in BI. The migration went OK for one of the system QB1, but got 2 problems with wrong source system for QB2.
1. The ODS can't be acitivated with an error message: "Invalid source system PB1CLNT100 entered."
2. The datasource connected to the ODS has the wrong source system "PE1CLNT100". It should be "QE2CLNT100" instead. I could manually replicate the source system from QE2 in QB2. But I can't link the datasource from the correct source system to ODS. When I tried to create transformation, it gave error that "ODS is not active due to invalid source system".
How should I fix this please?
Thanks,
Jenny

As praveen says you have to make your transporting scheme correct.
When transporting a datasource from dev to another stage you have you define how the names from your source system have to change.
In your case i expect the two QA system to be connected to different R3 source systems.
You have to change that in the way praveen says and then do some re-transports.
Success
Marco

IView and system admin objects appear changed or not registered when transported

Hi,
Recently we moved a few objects - iViews, pages and roles as epa and system admin objects as config archive and imported them manually to Test system. But when checked in the next landscape, the iView properties appear different. Eg. In Development system, the iView was unchecked for visibility option i.e. iView should not be visible. But when transported to test system, the property was checked and gave error. On reimporting, the same thing happened and we had to manually correct the property. This is not an expected behaviour and manual changes are not to happen after development changes.
Similarly, though config archive import showed the 2 new system objects in the respective location of Test system, the expected functionality was not working. I checked this by deleting one of them and manually creating the same entry and it worked fine. So I also had to delete the 2nd one and create a manual entry. The system admin objects we used pertained to System Configuration --> Content Mgmt--> Form Based Publishing --> Forms Availablity --> Folder Settings
We also moved kmcs and they are reflecting properly with correct folder permissions.
We don't understand why this is so occurring (iView and system admin entry appearing different or not getting registered )and never experienced such a case in previous projects. We don't want to face the issue going forward when transporting changes to staging and Prod systems.
Please assist as to what went wrong or any probable cause and solution for same.
Thanks,
Janani

Hi,
Has anyone faced such a situation before and know the reason for same ?
Regards,
Janani

System slow during loading data from source system

hi,
I am trying to load master data from r/3 into bw in quality envirnoment by means of a process chain. The problem is it being a master data load is consuming a lot of time. My development and quality environments are maintained on the same server. I doubt about this being something related to memory. If anybody could mention the ways through which memory can be monitored along with the reason for the slow nature of the system would be very helpful.
Source system: R/3.
Environment : Q03(quality)
Load : Master data(full load)

Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
Also see if there is any 'sysfail' for any datapacket in SM37.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)
5) SM58 and BD87 for pending tRFCs.
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the data tables.
Thanks,
JituK

BI Content Activation going for wrong source system

Hi,
I am trying to activate business content for the Customer cube in BI 7. The problem is that although the source system selection shows client 200 selected, the content activation goes for client 500 (which is the BI client). That is, during the activation process the process diverts to client 200 for no apparent reason. I have tried selecting other source systems, but the system still goes for client 200. Any idea of what is going on?
Many thanks!
Regards,
Adeel Hashmi

Hi Reddy,
I checked it already and it shows the T90CLNT090 - IDES ALE Central system (client 800) which is shown as "Self-def'd" and not R/3, infact i dont have any source system specified under R/3 option. How do i fix this, as mentioned earlier we have both ECC and BI in the same box, will this affect???

Creation of System Alias between Portal and E Sourcing System

Hi Team,
I would like to create a System Alias between SAP Portal 7.4 and E Sourcing System 10.0. I would like to know during the creation of System Object which template i need to take (is it http System or R/3 System using Load Balancing).
If it is a HTTP System, I am getting ""Could not find Connector Factory value: null"".
Could you please help me in knowing what could be the issue.
Pls. Note: E Sourcing is a Java based SAP System.

Hi Sankar,
Please go through the below SAP Note and see if that helps.
711769 - SSO between SAP Java Software Products
BR,
Anurag

Connecting two BW systems to the one R/3 source system

Hi all!
I have to connect two BW Systems to one R3 system. In our last tests we have had problems trying to connect two BW servers simultaneously with R/3 source system because it allows only a logical system name for each R/3 client, and (We guess that we need to define tow diferent logical system name, one for each connection). This has been generating errors when we try to load data from R/3 to BW because, we guess, R/3 does not recognize the BW source system in the ALE connection for someone BW systems at transfer data. In this moment I have one connection active (BW1-R3). The BW2-R3 connection is already inactive. Does anybody know how perform this? we need solve the transfers problem as soon as possible.
Thanks! Judi

Ah...
please don't post twice the same question...in these forums we are always the same !!!
You can close this thread to avoid to look in two different posts...
Bye,
Roberto

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

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

Source System mapping while transporting objects from Q to P

Hi All,
I have moved all my transports from BW DEV to Q twice with different source system mappings, say R3D to R3Q and again R3D to R3X, as I have to do testing from both the source systems.
Now, I have to move all those transports to PROD and I found out that they will be moved from Q to P and not from DEV to P. In such case, what source system mapping should I maintain in P? Is that R3Q to R3P or R3R to R3P?
Hope I am clear with my question. Please let me know if it is not clear.
Thanks,
RPK.

Hi Nasiroddin,
Itseems I am not clear with my question. Let me put it in another way.
My BWQ is connected to two R/3 source systems, say R3Q and R3X where as my BWP is only connected to R3P. While transporting the requests from BWQ to BWP, I know that I have to maintain the source system mappings(Tools->Mapping of the source system names). Now I am in doubt about what mapping do I need to maintain(either R3Q->R3P or R3X->R3P)? Which source systems transfer rules etc.(all source system dependant objetcs) will be transported, either R3Q or R3X?
Thanks,
RPK.

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

SAP Source System showing up as BI Source System in RSA1

I have 2 BW systems and 2 CRM Systems. In one BW system, when I create a SAP Source system in RSA1, It gets listed as a SAP Sources system along with ECC and all the rest.
The Logicial Systems and RFC Connections all appear to be the same between each pair.
In the other system, using identical procedure, it the source system gets listed as a BI Source System. The 2 CRM systems have identical components and version levels as do the 2 BW systems.
Any idea why and if this would make any difference and how to correct.

Hi,
To fix this, you need to do a restore (& not a delete) of the source system in BW, having deleted the RSBASIDOC entry in the source OLTP system.
This will force the BW system to interrogate the RSBASIDOC table entry in the source system again and it should then realise that it is an R/3 system (not a BW system) and move the entry to the SAP folder.
Rgds,
Colum

Source System Error While transporting

Hi SDN,
We are transporting requests to a deployment test box SN1 and we are getting this error message while we never got this error message transporting to QAS and in QAS we did not need to create DEV010 as a source system - setting up RFC connection was sufficient.
Any thoughts?
===========================================================
Source system DEV010 does not exist
Message no. RSAR409
Diagnosis
Source system DEV010 is not known.
System response
The imported data for data source 8ZM_C42 was deleted again as the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP to an available productive source system.
Procedure
Create the referenced source system in the Administrator Workbench or define a mapping to a known source system in table RSLOGSYSMAP.
You get to the maintenance using Tools -> Conversion of the logical system names.

Speak to your basis team and ask them to make entries in table:
RSLOGSYSMAP .
Are you trying to transport info source or any source system dependt object? If so, this error is understandable.
This has been discussed several times and pl search the forum.
Ravi Thothadri

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

Similar Messages

Maybe you are looking for