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

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

  • 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 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.

  • 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.

  • Mapping of objects from source system to BW

    Hi Experts,
      Here is a problem in my source system I declared objects as ZTECHNICAL  but while defining in BW as it will not accpet more than 9 characters so I named it as ZTECNICAL here does it matter for the mapping of the object to ZTECHNICAL to ZTECNICAL.
    ZTECHNICAL IN SOURCE SYSTEM
    ZTECNICAL IN BW.
    Thanks in Advance.
    Vassu.

    Hi Vasu,
    It deos not matter as long as you map the same info-object to the same fields from the source system.
    For example Company Code BUKRS in R/3 is always mapped to 0COMP_CODE info-object in BW.
    No issue. Go ahead.
    Bye
    Dinesh

  • Creation of Source System

    Dear all,
      i am new to BI 7.0. can you help me how to create source system.

    Hi,
    You can actually create many type of source systems depending on your business requirements.
    Go to RSA1 transaction in BI.
    choose Source system. Depending on the type of system you require, right click and choose create.
    then you have to follow the procedure it says.
    As in case of SAP source sytem you have to give the R/3 system name/ID etc and user name/password to connect to and from R/3 system.
    For this you have to maintain RFC destination to communicate to and from R/3 system to BI system. Then it will login to the R/3 system and will comeback to BI and start transferring matadata and BI contents  from R/3, choose without dialog option when it ask you otherwise it will ask you every time it will transfer new object.
    Assign points if it helps..........

  • BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

    Background:
    I am relatively new to BW team and will be going through my 1st source system upgrade.
    We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
    We are upgrading to the source system to ECC 6.0.
    In Development and QA Environments:
    we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
    We have a opportunity to compare the BW Objects, data flow and data loading from
    both source systems.
    In Production, however, we will just upgrade over 3 days downtime.
    One Question that comes to mind in this regard...
    What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
    Some of the suggestions that were given to me include following points.
    Before Upgrade:
    1 Check data, taking pre images of it for testing with post upgrade.
    2. Perform proper analysis of Source system related BW objects.
      - A complete listing of actively used Datasources,.. etc.
    3. Make delta queues empty,
    Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
    4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
    After Upgrade:
    1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
    (depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
    2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
    3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
    Maintain Control Parameters for Data Transfer
    http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
    4. Check for Changes to extract structures in LBWE Customizing Cockpit 
        - OSS Notes 328181, 396647, 380078 and 762951
    5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
    7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc. 
    Below is a link for some useful programs in this regard.
    https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
    6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
    As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
    7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
    new/changed datasources,if needed. 
    8. Check all CMOD enhancements.
    If we are using a customer exit with the extractor in the OLTP, see Note 393492.
    7. Check for unicode (all custom programs or Function Modules for DataSources)
    5.  Check all the queues in RSA7, start delta runs and test data consistency.
    For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
    9. Take back up of data posted during upgrade for contingency planing.
    10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
    Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

    Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
    We have similar scenario -
    We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
    Our strategy in ECC deployment  ->
    In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
    In production we are going to use same system PRXX upgraded from 4.7 to ECC.
    Now we are in testing phase of ECC with all interfaces like BI in Dev.
    My questions are below ->
    How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
    Also in new ECC sourcesystem copy  we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
    Is there any easy way for above scenario ?
    Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
    I have found some other links which have some pieces of information regarding the topic -
    Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
    BI 7.0: Source System upgrade  from R/3 Enterprise to ECC 6.0
    Re: ECC 6.0 Upgrade
    Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
    ECC 5.0 to ECC 6.0 upgrade
    Thanks
    Prasanth

  • Disconnet a Source system from RSA1

    Hi!
    I changed all the neccessary BW objects from one SAP ECC system to another one in my SAP BW system via tcode BDLS (e.g. EC1CLNT500 --> EC2CLNT500).
    Now I would like to delete the old entry of EC1CLNT500 in RSA1 --> source systems.
    When I do so I get the following error:
    Source system cannot be deleted in Content system
    Message no. RSAR670
    Diagnosis
    If a source system is deleted in the Content system, the shadow tables
    for all source system-dependent objects for this source system release are also deleted. You can configure a user as a non-Content user by using a SET-GET parameter. You can then use this user to delete the system, and then the above-named objects are not changed duringdeletion.
    System Response
    The function is completed.
    Procedure
    Logon as user ACTIVATE, and repeat your actions.
    Can some one tell me how to proceed here?
    regards
    Jürgen

    Hi!
    The table RSBASIDOC does not have the entry for new SAP BW system that I would like to disconnect.
    Only the value of the old SAP BW system is there...
    How to proceed?
    Thank you!

  • Source System Deletion Process in BW

    I deleted the Sourse system (NQ2) in BW sandbox server (BSN) using RSA1 with right click option. During this deletion process, it  deleted all the dependent objects. Now i connected BSN system to another Source System (NSB) and  replicate and activate the datasource successfully.
    Now when i checked the infosources in RSA1, say 2LIS_13_VDITM, no datasouce is assigned to this infosource. I can manullay assign the datasource.
    is it the right approach to delete the source system and connect to another source system? Do i have to manually assign the source system to all inforsources?
    Regards
    Amarjit

    Hi,
    it wasn't necessary to delete your old source system. By doing so you have deleted all independant objects: transfer structures, transfer rules and most important, your PSA data which could be used for testing.
    You could have kept your old source system to use it a template.
    For instance it would have been possible to recreate all your TRules like for like from your old source system with a special transport by collecting all source system dependent Objects with a "save for system copy".
    You would have saved a lot of work!
    hope this helps...
    Olivier.

  • 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

  • Configuring of a new source system in BW

    Hi Experts
    We have to set up a BW system,  which will have 2 source systems( ECC)  clients 550 and 590 of the same ECC ( ECC QUALITY). One client is already there and we have to configure another client of source system with the sane BW Client 350. I understand that the dataflow is partly different (e.g transfer rules and datasources are source system dependent). My question are
    1.     How we can configure a Source System on BW.
    2.     What changes if any I have to make in the existing system (BW)
    3.     What will happens to the Existing Data-sources ( Do I have to replicate each and every data-source of the existing ECC clients to New ECC client.)
    4.     Do I have to create New transfer and update rule for the new client
    Any other point Pl. advice.
    Thanks in advance.
    Dinesh Sharma

    You can more than one source system to onw BW client.
    You have to use source system compounding to differentiate between characterstics values if you are loading to the same object. Otherwise you need to use separate characterstics for ex : Yxxxx object for one source system and Zxxxx object for another.
    Also the dataload timing should be setup properly. Otherwise it may leads to object locks.

  • Deletion of source system after an upgrade : consequences ?

    Hello,
    I'm a sap basis guy.
    We have a SAP BI 701 sytem mapped to our 4.7 Non Unicode source system.
    I have now perfromed the unicode migration and upgrade to ECC6 of the source system on another server.
    It means now, that I have two sourtce systems with exactly the same SID, and logical name.
    Sicne the BI connexion in RSA1, is based on the logical system name , I have no ther choice than delete the old
    source system, and recreate it with the same logical name but different connexion parameters (hosts, ...) and differentversion (
    I have talked with the BI team, but thnigs are quite unclear about the consequences of deleting a source system in RSA :
    Do all Transformations/ Transfer Rules between DataSources and targets are deleted ?
    Does it mean that they have to be manually recreated after the new source system has been recreated ?
    Is there any workaround ?
    Thank you in advance for your help.
    Regards.

    Hello,
    If you do not save the source system dependent objects to a transport request before you delete the connection then the objects will be lost , you can avoid this by saving the objects to a transport request and then release the transport before you delete the connection and import it in the new system, the steps in general are below:
    RSA1
    Transport Connection
    Button 'Collection mode'  set to 'start manual collection'
    Press 'Source system assignment' button (it's the one left of the
    'Request BEx' button)
    Select the source systems you want to save the transfer rules for
    Continue
    Button 'Grouping' set to 'Save for system copy'
    At the left border click on 'Object Types'
    Extend tree  'Source system' LSYS
    Double click on 'Select objects'
    Select the source systems you want to collect objects for
    the source system is now displayed in the right box
    Press collecting button ('gather dependent objects')
    this may take a while
    Right click on the root of the tree and select
    Transport all below
    Expand the whole tree and check if there isn't an object which is locked
    by an other open transport request !!
    (the column 'Transport request' has to be empty (BEFORE deleting the corresponding source system
    connection!)
    Best Regards,
    Des

  • BW: Connect to new source system via special transport

    Hello everyone!
    I have a BW system connected to an R/3 source system. I have made a copy of the source system. Now I want all my models to be connected to both source systems. I heard that this can be achieved via special transport (i.e. place all source system dependant objects into a special transport request to be imported back into my BW system, but with the new source system assignment). Does anyone have any documentation on how to do this?
    Best Regards and Merry Xmas!
    Luís Andrade.

    Hi Luis,
    There are two parts,
    1) If you want to transport all your objects from current R/3 system to newly created r/3 system then you can create a TR and use it in SCC4 transaction during client copy. In the same fashion you can use RSA1---> transport connection and use the TR for system copy. After that once you release this TR all the objects will move from one system to another.
    2) But if you have already moved all the objects in source system but now you want them to replicate in BI then go to SAP BI system select your source system and then from the context menu choose replicate datsources option, it will fetch everything from respective source system in BI.
    Regards,
    Durgesh.

  • New Source System Client for BW

    Hi All,
    Currently we have R/3 QAS Clint 102 connected to BW QAS. We want to get rid of this Client 102 and connect a new QAS Client 100 (same server but different Client) to BW QAS. I created a new Source System (QAS100) in BW QAS and did a restore. 
    My question: How do I get all the Source system dependent Objects like InfoSurces, InfoPackages etc for the new Client 100 in BW QAS? Please help me and I promse to generously reward points. 
    Thanks, very much in advance.
    Srini

    Hi A.H.P,
    I am pretty sure this will resolve the issue. I will come back again and reward 10 points once we apply a working solution.
    Thank you for a quick reply.
    Srini

Maybe you are looking for

  • How can I select more than one song from the search results?

    I want to create playlists based on certain words in the song title. For example, I may want to create a playlist of all my songs with LOVE in the title. Doing the search is easy, but I can't select more than one song at a time. Is there any way in i

  • ITunes 11 - how can I change the genre of a movie now?

    So I've had iTunes 11 for about 3 hours now and so far it *****.  One of my main problems is I can't find how I can change the genre of a movie anymore.  I used to do this from Get Info so I could organise all my movies in to my own genres that make

  • Apple remote app loses connection

    I am using the remote app to control my Itune on my computer on Vista. I am able to initiate the connection. But when I close the remote and re-open I still see the library but I am not able to open it. I able to reconnect if disable and re-enable ho

  • Tricky Database Modelling Issue

    My application needs to merge items of defferent types into items of one specific type. For example, 2dz Heinecken, 3dz Grolsch and 1dz Stella should be turned into 6dz of Heinecken whereas 2dz Heinecken, 3dz Grolsch, 1dz Stella and 3dz Carlsberg sho

  • Stemming on app keywords?

    Hey guys, quick question: does any of you know if Apple is performing stemming on submitted keywords, and respectively on the keywords that people use to search with in the app store? To give an example, let's say I plan on submitting an iPhone app a