Transport collecting incorrect Source System.

Hi SDNers,
In my BW DEV i got source systems to both R3 DEV and R3 Production.
reason for this is that the data in Dev is not correct.
When i use transport connection it only transfers Source System from the R3 DEV and not R3 Prod. I need the Source System from Production and not Development. How can i force it to use Source system from Prod and not Dev.
Thanks.
Andre.

Hi
in the transport connection before collecting your objects maintain the source system assignment sceen (toolbar or Shift+F7)
hope this helps...
Olivier.

Similar Messages

Inconsistent Dev System: Infosource assigned to incorrect Source System

Hello all
Our Development box contains inconsistent assignments of infosources to source system.
When I compare the dev, quality and production boxes I find:
> Quality and Prod are consistent and all infosource systems are assigned to correct source systems - all loads execute as expected.
> However I find ips defined in the process chains in Quality and Production under incorrect source systems in the Development box.
> Also, the inconsistencies are varied for ex: SALESORG_ATTR is assigned to source system Y, while SALESORG_TEXT is assigned to source system X, while 0CUSTOMER_ATTR is assigned to source system Z ( where Z is the correct source system).
I have not been able to figure what lead to this inconsistency except that I am aware that there were plugins installed and some refreshes done followed up by BDLS.
I did try having BASIS execute BDLS to convert all logical systems X to Z ( but there were errors in the log stating that destination Z already exists - which is correct since for ex 0CUSTOMER_ATTR is assigned correctly to source system Z)
I was considering the following to rectify this situation:
1> Make the rectifications manually
1a> Identify all the infosources in all the process chains in quality/production
1b>Manually reassign all infsources/datasources to the right source system
1c>Check all the mapping rules (transfer rules) and ensure they are same as quality/production
1d> Activate the transfer rules
1e>Create infopackages
1f> Transport the ips to quality and reassign them to the process chains.
> This is a very labourious task and invovles high risk due to manual effort
2> Refresh from quality into dev
2a> Recreate the transport routes
2b> Resynchronize all the loads with the R3 dev box
> This would cause loss of version history and therefore not recommended by SAP
3> Rollback to a restore point
3a> We would need to find whether we maintain a restore point in the past before which the system were consistent.
3b> Reimport all the transports from the restore point till date
4> Rerun BDLS
4a> This might involve deleting all occurences of source system Z from the dev box
Please advise what would be the best approach / if theres a better way to address this issue.
Thankyou
Edited

Hi,
Goto RSA1 in yy BWQ system.
In the Menu ---> Tools ---> Mapping of Source System Names ( Shift + F6)
Change the Target Source System as BWP server.
Now move the transport to BWQ. Your BWP will be assigned as source system.
Regards,
Balaji V

Collection in source system error

Hi,
Recently we just performed a BW SP upgrade to 3.0B level 28. During our first extraction after upgrade on production for 0HR_PY_1 (Payroll Data) infosource, we encountered a message "Collection in source system ended".
Anybody has any clue about the cause and how to go about resolving it?
Thanks.
Best regards,
Taly

hi Taly,
datasource need to be replicated from source system (r/3) in production.
area to check -> in monitor request, menu 'environment' check job overview both bw(datawarehouse) and r/3(source system - equal to transaction sm37 - see if job cancelled and any helpful error message like sql error., from menu-environment check the same bw and r/3 for shortdump (st22), transaction rfc, ale management, system log(sm21) and so on, please let's know what's your finding there, possibly source system problem with that message, may ask basis for help. hope this helps.

Collection in source system ended

Hi Experts,
Need your help on the below issue.
Due to error at R/3 the status of my load for one of the
infosource is YELLOW with
status: Collection in source system ended.
The Request (REQU_4CXV37IJY08OX4UVF4YCPREAR) in R/3 under SM37 is Completed successfully.
BUT in BW
In the Details tab of Monitor all the 4 steps are green( 1. Request , 2.Extraction , 3.Transfer , 4.Processing)
EXCEPT ---> 2.Extraction
The Extraction step is as follows
( Yellow ) Extraction (messages) : Errors Occured
        Data Request received
        Data Selection Scheduled
        (Yellow) 9157 Records sent ( 9157 Records received)
Waiting for your response.
Thanks,
Veeru.

Hi Krishna ,
Thanks for faster response.
I checked the log in R/3 it has finished successfully
Below is the log
Note : the records recieved in BW is exactly equal to the no records show in the R/3 request log below.
LOG OF JOB IN R/3
Job started
Step 001 started (program SBIE0001, variant &0000000057813, user name BWALEREMOTE)
DATASOURCE = ZBW_MDRS_V
          Current values of selected profile parameter                *
abap/heap_area_nondia......... 2000683008                              *
abap/heap_area_total.......... 2000683008                              *
abap/heaplimit................ 40894464                                *
zcsa/installed_languages...... E2                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 64                                      *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000683008                              *
0 LUWs confirmed and 0 LUWs to be deleted with FB RSC2_QOUT_CONFIRM_DATA
Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 9,157 records
Result of customer enhancement: 9,157 records
Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 9,157 records
Result of customer enhancement: 9,157 records
Asynchronous sending of data package 000001 in task 0002 (1 parallel tasks)
Through selection conditions, 0 records filtered out in total
tRFC: Data package = 000001, TID = 0AB80A0D6ADB49A37D4F558D, duration = 00:00:10, ARFCSTATE =
tRFC: Begin = 24.02.2009 12:53:35, End = 24.02.2009 12:53:45
Job finished
Do u still think tht i should turn it to red and repair?
If yes wts the steps can you please tell me.
Thanks,
Veeru.
Edited by: Veerendra Kumar on Feb 24, 2009 12:57 PM
Edited by: Veerendra Kumar on Feb 24, 2009 12:57 PM

Collection in source system ended-Process chain error

Hi friends,
I have got a PC which failed due to error : Collection in source system ended.
My flow of PC is .
start--
       --Load IP 1
      ---Load IP2
      _--load Ip 3
Load IP4
      ---Load Ip 5.
I got this error at IP2 and so my pc fail .
can i manually upload this IP2 and make the process chain OK?
what are the steps involved in rectifying this?
regards,
siddartha

First try to find out the reason for the load failure. Once you fix this, do a manual run of the infopackage and when successful you can continue with the rest of process chain.
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.

Loading and with error message :COLLECTION in SOURCE SYSTEM ENDED

Hi,
Facing problem with master data object while loading and with error message :COLLECTION in SOURCE SYSTEM ENDED
This load is getting failed every day. It is a full load and records are getting transferered and added.
when we check in details tab in RSMO all data packets in processing is green but in extraction some of the data selection scheduled are in yellow.We are changing QM status to green as records are added.
Version i am using is BW 3.5
Please let me know what will be the problem???
Thanks,
Edited by: lokesh thonsyd on Feb 18, 2009 8:55 AM

First try to find out the reason for the load failure. Once you fix this, do a manual run of the infopackage and when successful you can continue with the rest of process chain.
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.

Transport Collection includes Logical System?

Hi, I am collecting up Object for the BW Admin Cockpit and the collected list includes the BW Logical System as well. I can't understand why this would get picked up and I don't know what the consequences are for transporting this. The Transport Connection will not allow me to unselect it!
So I am thinking of just creating the transport with it and then manually deleting it in the transport.
Can anyone shed any light
1. why this is being included in my transport?
2. what the consequences of sending it might be
3. Is it OK to just manually delete it from the actual transport and not worry about it.
Here's a picture of the Transport Collection for review http://i44.tinypic.com/ofx1lv.png
Thanks for any insight...

1. why this is being included in my transport?
This would get connected, if u selected 'Grouping' option In dataflow before or In dataflow before and afetrwds
2. what the consequences of sending it might be
The corresponding logical system would be there in target system. Hence this is not required to transport
3. Is it OK to just manually delete it from the actual transport and not worry about it.
U can delete that manually

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

Transporting with diferent source systems.

Hi experts,
I am quite new in BW.
I have been developing some thing in sap BW.
I have Development, integration and Production in both BW and R3 source system. Each one should be connected with each other. So, development with development, integration with integration and production with production.
Here comes my doubt. All i have done is in the development systems. Now I want to transport and i don't know how to do this c'ause I want all the same things but connected to a different source system, and I think that when i am transporting I will have the Integration Business Warehouse connected with the development R3 system.
What should I do to avoid this and transport all but with a connection with a different system? Can anyone give me a clue please?
Thank you all!
Artur.

Hi,
BASIS team will comfigure the connection betwen BW systema nd R/3 system for all three environments.
R/3    DEV     -
>            QTY   -
>             PRD
              I                              I                        I
BW    DEV    -
>            QTY -
>               PRD
for transports, source systems Transports (R/3 datasource and tables) will be transported to QTYand PRD systems
and
for transports, BW Transports (BW infoobjects, DSO, Cube, Transformations....) will be transported to QTYand PRD systems.
[CTS and BW Transports]
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e]
Regards
Daya Sagar

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.

The transport track TR000003 (source system DEV-100) is locked

Experts:
I get above error when trying to create a transport request.
Could you help how to unlock it?
Thnaks!

Hi,
Just go in TCode SE01 and check whether your transport request is released or not.
If not than, first release the request.
Or Other case may be that it is a local change request and such request can never be transported.
Thanks
Deepak

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

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

Transporting Process Chain - error Source system does not exist

Hi,
I tried to transport a local PC by itself (not including its main meta chain) since I have only done modifications in the local PC only. In the PC, there are PSA Processing, ODS Processing, ODS Activation, ABAP Program w/ variants and Infocube Rollup.
However, I got the following transport error: Source system does not exist
=======
Diagnosis
Source system is not known.
System Response
The imported data for DataSource was deleted again because the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP on an existing productive source system.
Procedure
Create the referenced source system in the Data Warehousing Workbench or define mapping to a known source system in table RSLOGSYSMAP.
You get to maintenance using Tools -> Conversion of the logical system names.
============
I have checked at the table RSLOGSYSMAP and all source system mappings are in order.
And the weird thing is, upon checking the PC itself in the transport-to box, I can activate it without any error.
FYI, we are currently upgrading to BI Accelerator. Am not sure if this could be one of the reasons.
Any inputs and tips are highly appreciated and will be rewarded with points accordingly.
Thanks

Hi,
This error is due to the fact that the
mapping table for the after import (RSLOGSYSMAP) is not correct maintained in PB7 system.
You need to maintain table RSLOGSYSMAP in each system
You can find the steps to do it in the attached note 127326:
o Maintain table 'RSLOGSYSMAP' in the target BW with view
   'V_RSLOGSYSMAP' and enter as 'original source system' the logical name of the source system in the source BW and as 'target source system' the logical name of the source system in the target BW.
   This maintenance is required since it allows the correct source system reference of the InfoSources to be transported.
This source system reference in turn is absolutely necessary to activate the transfer structure.
   Example:
   Source BW with source system AAA.
   Target BW with source system BBB where the source system AAA
   corresponds to the source system BBB.
   Entry in RSLOGSYSMAP in the target BW:
   Original source system: AAA, target source system: BBB.
   Give the DDIC user in the source BW in client 000 the
   authorization profile S_RS_ALL to create BW objects.
Cheers
Rajesh

Assignment of Source System in quality after transport

Hi Experts,
We have implemented the Inventory management standard flow in Development,
Now to tell you, we have multiple landscape over here,
Depending on the project, and the fesiblility for the client, the tranport layer is been decided,
But for sure we have multiple source system,
By multiple source system, i mean not the other components like R/3, SRM or APO,
but for R/3 itself we have multiple boxes at each layer,
Now when transported to quality,
the standard objects are reflecting after few errors corrected and re transports,
But the source system which it has picked for the BF BX and UM datasource is not that i require according to the transports landing for the R/3 developments,
AT DEVELOPMENT LAYER,
BW development is GDA, which is having the source system connection to development R/3 (GD0),
AT QUALITY
We have BW as EQ3,
For R/3 we have EQ0 and NR0,
All the transports have reached in the respective target quality system,
But the data sources are having source system connection to NR0 and not EQ0,
I want it to be EQ0 as the data lies over there.
How do i resolve this ?
Thanks and should be appricated for your efforts in helping.

Hi Daljeet,
You should set the Source system Conversion option in Transport Connection before Transporting the objects to QA and PRD.
You can do this using the button 'Conversion' next to the button 'Source System Assignment'. Here you can specify the Target source system name after the Transport.
If you want to change all the assignments from NR0 to EQ0, this article will be helpful for you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81
Get the help of your BASIS team also.
Refer this thread.
Re: source system in RSA1 is diiferent to the datasource in infoprovider

Transport collecting incorrect Source System.

Similar Messages

Maybe you are looking for