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.

Similar Messages

  • 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 can’t 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

  • Question regarding Transport of System Dependant Objects after Refresh

    Hi, We are doing a System Refresh of our Non-Productive BW Systems (DEV and QA).  Once this is done all of our landscapes will be "Harmonized".  This also means for example that all DTP's will have the same Technical ID's.  
    In the new 7.x when you transport System Dependant Objects they are assigned a different Technical ID than the source system.
    What will happen in our case if we transport one of our DTP's from BW DEV into QA?
    Will we end up with 2 DTP's in QA or will it know which one to replace (and how)? 
    Thanks!

    Hi,
    After your transports move in, if the object is a new one, it will be added to the target system & if the object already exists in the target system, then it will be replaced i.e. you will not have 2 objects but just one..
    Regards
    Vishal.

  • 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

  • Transporting SOURCE SYSTEM

    Hi Experts,
    I created a Flat File Source System in BW Development system based on that i created DSO,CUBE,MULTICUBE,PROCESS CHAIN and REPORTS.
    Issue :
    I need to transport them to Test and Production system.There is no Flat File source system avaliable in Test & Production....I know that we don't Transport Source Systems across BW Environments...how to deal with this...do i need to ask our basis team to create source systems in Test and Production before importing any transports.

    Yes - you basis guy will help you to setup the source systems.
    STEPS TO CREATE FLAT FILE SOURCE SYSTEM
    step:1 select source systems under modeling in AWB.
    step:2 select Source Systems root node.
    |---> context menu
    |--->create......
    step:3 select your required source system Icon.
    (in your case it is PC Icon).
    there it askes for a logical.......and source system name...
    here u can specify any name of ur wish
    for example:-
    logical sys name --- PC_FF
    source system name --- flat file source system*
    *press Continue * button.
    Observe the activation icon to confirm the successfull creation(_glowing lamp icon_ symbol)
    You also can have a look:
    http://help.sap.com/saphelp_nw70/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm
    Hope it helps..

  • Set Infoobjects as Source System dependent

    Hi Experts,
    How we set Infoobjects as source system dependent. Where can I find the flag or check box to make it Source System dependent
    Cheers,
    DV

    HI,
    Simple..
    GOTO Infoobject change mode.
    click on MASTERDATA /TEXTS TAB
    There we have checkbox " Character . is Infoprovider " you select that and give the Info area name  and actvate it
    Then you can find that in INFOPROVIDER MENU
    and SELECT THE INFOAREA WHICH YOU HAVE GIVEN in infoobject.
    I hope it will help you.
    Regards,
    Yerrabelli.

  • How to create Source System in BI 7.0

    Hi Experts,
    How to create Source System in BI 7.0, please urgent
    Thanks

    Hi Mark,
    Did you see the help site below which is telling how to create a source system .If not please take a look at it.
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a61e5e07211d2acb80000e829fbfe/frameset.htm
    Regards,
    ®

  • How to Check source systems in RSA1 and verify that connections are working

    How to Check source systems in RSA1 and verify that connections are working ok and how to Check Planning Area have green status.................

    Hi,
    In rsa1, go to 'Tools' and option 'Manage Source System' - the screens are self explanatory there after. To check the planning areas, go to transaction /SAPAPO/MSDP_ADMIN anc check the status of the relevant planning areas.
    Regards
    Vinod

  • 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

  • How to craete Source system in BW from R/3 box

    Hi,
    I requested to basis to create source system in bw with R/3 Box.they were created RFC connection and told me to create source system in the BW .
    Iam not sure how to create. please can any body help me in creating source system in BW with R/3 system.
    Thanks in advance.

    Hi,
    1.     You have made the following settings in the SAP Customizing Implementation Guide (transaction SPRO) under SAP NetWeaver ® SAP Business Information Warehouse  ® Links to Other Systems:
    ¡        General Connection Settings
    ¡        Links Between SAP Systems and BW
    ¡        Verify Workflow Customizing
           2.      You have made the following settings in the SAP Customizing Implementation Guide of the source system under the node SAP NetWeaver  ® SAP Web Application Server  ® IDoc Interface / Application Link Enabling (ALE) ® Basic Settings:
    u2022         Logical Systems
    -         Define Logical System
    -         Assign Logical System to Client
    u2022         Make basic settings for workflow (Perform Automatic Workflow Customizing)
    The name you used for the source system (logical system) has to be used again when creating the source system in the SAP BW Administrator Workbench.
           3.      You have taken the server name from the source system under Tools ® Administration ® Monitor ® System Monitoring ® Server.It is displayed as follows:
    Server_
    pswdf090_IDF_90
           4.      As a rule, system changes are not ever permitted in productive systems. However, connecting a system (as a source system) to an SAP BW, or connecting an SAP BW to a new source system, will require changes to the system change options. Therefore you have made sure that the following changes are allowed in the relevant clients for the system, when connecting to the source system:
    u2022         Cross-client Customizing and repository changes
    In the SAP Customizing Implementation Guide under SAP NetWeaver  ® SAP Business Information Warehouse  ® Links to Other Systems  ® General Connection Settings ® Assign Logical System to Client, select the relevant clients under Goto ® Details. In the Cross-Client Object Changes field, choose the Changes to Repository and Cross-Client Customizing Allowed option.
    In the source system, make the following settings in the SAP Customizing Implementation Guide under SAP NetWeaver  ® SAP  Web Application Server  ® IDoc Interface / Application Link Enabling (ALE) ® Basic Settings ® Cross-Application Components ® Distribution (ALE) ® Basic Settings ® Logical Systems ® Assign Logical System to Client.
    u2022         Changes to the local developments and Business Information Warehouse software components
    You use transaction SE03 (Transport Organizer Tools) to set the change options. Choose Transport Organizer Tools ® Administration ® Set System Change Option, then Execute. Make the following settings in the next screen.
    u2022         Changes to the customer name range.
    Again, you use transaction SE03 to set the change option for the customer name range.
    u2022         Changes to BW namespaces /BIC/ and /BI0/
    Again, you use transaction SE03 to set the change option for the BW namespaces.
    Thanks,
    Vinod
    Edited by: Vinod on Nov 26, 2009 10:54 AM

  • RSDS  transport - source system not exist

    Hello Guys
    i have a problem during transport of DataSource from DEV to QUA.
    The error is:
    Start of the after-import method RS_RSDS_AFTER_IMPORT for object type(s) RSDS (Activation Mode)
    Source system D18CLNT228 does not exist
    I have check already the transport table RSLOGSYSMAP and insert item to map the DEV system with QUA system (this done in both system,develop and quality). I check also the source system ID and everything seems update correctly (in both system develp and quality).
    Anyway during the transport i have this error and when check in QUA system i have the DataSource, seems map correctly with the right source system but is not active...
    do you have any suggestion
    please let me know
    regards
    B.

    Hi
    check in your QUA system if corresponding source system is linked to it. Also currpospong trasports in source systems are moved properly.
    Regards
    Sudeep

  • How to delete source system (popup window)

    Hi All,
    I want to delete the source system
    RSA1 - Source Systems - system and Delete
    but for every using "Transfer structure" i receive the popup information window and i have to confirm this window. It takes much time.
    Do you know anybody the another solution ?
    Thanks in advance for advice
    Martin

    Martin,
        That is the only way. It would ask you to put it in transports and larger the objects longer it takes. There is no other way as far as I know.
    Thanks
    Shabna

  • How to Transport the Business content objects using Transport connections

    Hi BI Guru's,
    I have installed the BW statistics cubes in BW Devlopment and i want to Transport the same things to Quality using Transprot connection. Please send steps and tips for Transporting the BW statistics collected objects.

    Hi ,
    While installing have you given any package and created request for this activation? If yes go to SE 09 and release your task and then request. And receive this in STMS in BWQ.
    If you do not have created request and saved it in $tmp while activation then you have to go to RSA1 > transport connections> select your cube > grouping> only necessary objects> collect automatically> and press transport button this will give you request no > and then release this request> then go to BWQ> stms> select source system> select your request> and press import request button(white truck sign)> do necessary settings > and say OK. Once your request status is green then its successfully received in BWQ.
    Hope this helps.

  • How to transfer source system?

    Hi all;
          I creat a source system in the DEV,and I want transfer it to PRD now,How to do ?
         Thanks.

    Hi Wang,
    Source system is the connection through which you can access data. It is not transportable.
    It's just a connection between 2 systems through IP address/RFC Destinations.
    Hope it gave an idea.
    With Regards,
    Ravi Kanth.

  • How to create Source Systems in BI or RFC ??

    Hi Gurus,
    I want to load data from an R/3 connection to BI.
    Now i have modified my Datasources in R/3 side.
    Question is how i connect R/3 to BI ?
    I will have to create RFC Connection , Yes ?
    I did following steps , so far, PLEASE LET ME KNOW WHAT ELSE TO DO ???
    1 To call the RFC we have to create destination.
    Means Source system and Target system.
    Source System: From where we are calling the RFC i.e. Source system. = R/3
    Target System: To where it is calling i.e. Target system. = BI
    2. In Source System, create DESTINATION
    Goto SM59 to Create a RFC Destination.
    3. In SM59 First screen you will get list of RFC Destions
    Select R/3 Connections and Click on list(+)symbol it will gives already created Destions, Select R/3 Connections click on Create buttion, it will takes you into another screen to create Destionation.
    Name, Password, Logon details.
    once it is saved you can test it. Click on Test Connection Button
    if it is executed successfully your destinatio is established
    NOW WHAT DO I HAVE TO DO IN BI SIDE ????
    i went to RSA1 -> source systems
    Here i dont see my R/3 in source systems...
    please give me step by step instructions.

    Hi
    See SAP Help
    http://help.sap.com/saphelp_nw2004s/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/content.htm
    Connecting ECC6.0 and SAP BI
    Setting-Up a Connection between BW and R/3 for Data Load
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/908836c3-7f97-2b10-4cb8-e6790361c152&overridelayout=true
    Configuring RFC in BI7 for connecting ECC6 server:
    Connecting ECC6.0 and SAP BI
    Thanks
    Reddy

Maybe you are looking for