BW Source system plugin upgrade

Hi,
  We are in a process of ungrading PI_BASIS component from 2004 to 2005 and I need to know if there is anything to be done on the deltas before it.
we have all sort of logistics applications like SD, PO etc.  and we dont want to lose any records. 
So can someone please put some light on what all steps to perform on the delta management side so that we dont lose any record and the SAPI pointers are still valid after the upgrade.
Thanks

hi,
check sap notes 328181 and 762951

Similar Messages

  • Deletion of Data from Infoprovider  after upgradation of source system

    HI All,
    In our project  source system is upgraded from 4.7 to ecc 6.
    I have kept the same logical name and changed the RFC connection so that it points to new source system.
    Now do i need to delete all data before uploading data from source system or it will be fine as source system name is same.
    If i need to delete data ,can u help me how to delete master data especially Hierarchy data. do we need to Delete Hierarchy and recreate it.
    Please help em to resolve this issue

    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

  • Initialization options for source system (message_type_x)

    Hi All
    My R3 source system is just connected to my BI, after the upgrade of R3. Now i saw in RSA7, all entries in RED. So i have deleted them manually in RSA7.
    Now, in RSA1, I wanted to run the Init delta IPAKs for all those deleted datasources, when i open the IPAK to run, its giving me MESSAGE_TYPE_X dump. So i cant go to the menu --> scheduler --> initialisation options for IPAK.
    I think i should have deleted from here than in RSA7 in R3. But now i cant even open the IPAK. The module name in the dump is RSM1_CHECK_FOR_DELTAUPD.
    How can i resolve this issue ? Do i have to replicate the datasource in RSA1 as Source system is upgraded ( we actually replicated all metadata by rt clicking the source system).
    Any help pls ?
    thx
    venkat

    hi,
    check this link ..
    Clicking on Delta Infopackage gives short dump MESSAGE_TYPE_X
    Re: Short dump MESSAGE_TYPE_X while trying to open infopackage
    reagrds,
    shikha

  • Steps in BW after the upgrade of the source system R3 in netweaver 2004s???

    Hi,
    1. Who can tell me which are the steps to execute in BW after the upgrade of the source system R/3 4.6 to Netweaver 2004s (ECC6) ?
    2. Do the delta loads continue to run or must be re-initialized?
    Thanks for your help
    Dominique

    hi Dominique,
    you should take care not after upgrade, but also before upgrade
    or your upgrade has been done ?
    also stated, before upgrade
    If you use Logistic Cockpit, please make sure that you know notes 328181, 396647, 380078.
    These are absolutely prerequisit notes for using Logistic Cockpit.
    Never change the extract structure (communication structure) when there is data in SM13 or in the DeltaQueue!
    Never upgrade your PlugIn System when you have data in SM13 or in the DeltaQueue!
    SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade your PlugIn system!!!
    SM13 and RSA7 have to be EMPTY also when you apply PlugIn Support Packages!
    458305-OLTP system upgrade: What should I be aware of afterwards?
    Note 458305 - OLTP: System upgrade or SP - What should I be aware of after
    Note 301192 - Procedure after upgrading an R/3 source system
    Note 359412, there may be some others
    hope this helps.

  • Upgrading Source System to ECC 6.0 - What is my role in BI

    Hi, Our Production R/3 System is being upgraded from 6.4 to ECC.60.  The machine and client will remain exactly the same.  Before and after the R3 Upgrade what will I have to do from a BI System Perspective?
    Hope and Pray?     
    Thanks...

    Hi......
    In general, you should take care of some things when you upgrade your BW system. If it is R/3 upgrade then you should look at functional areas you use from R/3 and analyze if R/3 features you use has been changed. You can find a lot of information about new features and changes in SAP R/3 Enterprise Release 4.70 Release notes .
    Before Upgrade
    If you use Logistic Cockpit, please make sure that you know notes 328181, 396647, 380078.
    These are absolutely prerequisit notes for using Logistic Cockpit.
    Never change the extract structure (communication structure) when there is data in SM13 or in the DeltaQueue!
    Never upgrade your PlugIn System when you have data in SM13 or in the DeltaQueue!
    SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade your PlugIn system!!!
    SM13 and RSA7 have to be EMPTY also when you apply PlugIn Support Packages!
    After Upgrade
    458305-OLTP system upgrade: What should I be aware of afterwards?
    Note 458305 - OLTP: System upgrade or SP - What should I be aware of after
    Note 301192 - Procedure after upgrading an R/3 source system
    Note 359412, there may be some others
    Some general information about R/3 upgrade you can get here:
    http://www.finsvc.duke.edu/finsvc/sapr3/Training/beyondbasics/BeyondBasics.pdf
    http://searchsap.techtarget.com/featuredTopic/0,290042,sid21_gci912111,00.html
    Hope this helps you.....
    Regards,
    Debjani.....
    Edited by: Debjani  Mukherjee on Sep 29, 2008 10:36 PM
    Edited by: Debjani  Mukherjee on Sep 29, 2008 10:37 PM

  • 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

  • Plug-Ins and Extractors - Related to Upgrade of Source system

    Hi,
    We are upgrading from R3 to ECC.
    Can I say that, if the Plug-in in current R3 system and the new system(post upgrade)(ECC) are same then, the extractors will also remain same ? hence, nothing will be affected in BW ?
    For example, if the current system(R3) has the Plug-in as PI 2004.1 and the upgraded ECC also has the same Plug-in PI 2004.1 , Can I say that the extractors will also be the same ?
    Regards,
    Rekha .

    You have to take care of all your deltas are picked into the bw before upgradation.
    Some times you may required to replicate the data sources after upgradation.
    You may lose the connection between your R3 and you BW.
    Please do a souce system check after the upgradation.
    You have to take care of all deltas :
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    /message/3221895#3221895 [original link is broken]
    OSS notes 328181 and 762951 as a prerequisites.
    http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B

  • Source System Connection Issue after BI 7 Upgrade

    Hi all,
    We have just upgraded from BW 3.1 to BI 7.
    After the upgrade, I checked the connection to our R3 4.6 source system.
    It is now saying the following message:
    Source system XXX is marked as inactive in BI.
    Check failed for RFC connection XXX ; check destination
    After going through the RFC connection, I tested the connection for this source system. It said OK. While doing the authorization test, it said: "Name or password is incorrect. Please re-enter".
    The thing is that our name & password ARE correct definitely.
    Is there any issues post upgrade because authorization stuff between R.3 4.6 (PI 2004.1 SP15) and BI 7?
    Any ideas?
    Thank you
    chris

    Hi,
    as from NW7.0, passwords are case-sensitive.
    If you define the passwords in the RFC in uppercase, it will work.
    This is a problem when you link an 'old' (not NW 7.0) system to a NW 7.0 (as in this one, passwords are case-sensitive).

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

  • 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

  • Will an BI Content upgrade from affect the source systems?

    Our current BW has BI Content 7.02 patch 003; we are planning an upgrade to 7.03 patch 012.  Will we have any impact on the source systems (ECC and SRM)?  We are trying to decide if we need to archive and backup the operational systems.  Since it is a lot of extra work and increases the number of people affected, we prefer not to do it unless necessary.
    What type of regression testing is most common after a BI Content upgrade?
    thank you very much,
    LLK

    Hi
    As a data fetching from Source system -- the BI Upgrade does nt have any impact on Source Systems normally -- But u need to prepare a check list with before and after upgrade with DS ( Some times DS get de activated while upgradation ) and the DS are source system dependent so you may have to re activate the same based on requirement/possibilites-- And also you may have to empty the Delta Queues on Source System side -- otherthan that no impact , as far I know.
    Hope it helps and celar

  • Can the Adobe PDF plugin carry exact phrase search criteria through from source system into Reader?

    In SharePoint 2013 if you search for an exact phrase and then view a PDF that is returned by the search (in Reader via the PDF plugin) then the Reader will treat the complete phrase as individual words.
    For example, search for "High Court" in SharePoint, get returned a set of PDF documents, and when you view one of them through the Reader the hit highlighting will be for each instance of "High" or "Court".
    What is wanted is hit highlighting only of instances of "High Court".
    I get the same behavior if the Adobe PDF plugin is installed with the Filesite DMS. So it seems to be standard behavior for the Adobe PDF plugin
    Is there a way to make the Adobe PDF plugin carry exact phrase search criteria through from source system into Reader? And then hit highlight the exact phrase only.

    Hi Sam,
    You can opt for 'Advance Search' option in Reader to match the whole words to get to the specific documents.
    Regards,
    Rave

  • Data load delay after DB upgrade in source system

    we have upgraded our source system DB to oracle 11g over the weekend. The first loads of our process chain the master data is taking huge time with the message as
    I am getting message as
    Data Package 000001: sent,not arrived
    Info IDoc 2 : sent , not arrived ; Data passed to port OK
    Info IDoc 1 : sent , not arrived ; Data passed to port OK
    Info IDoc 3 : sent , not arrived ; Data passed to port OK
    Info IDoc 4 : sent , not arrived ; Data passed to port OK
    Request IDoc : Application document posted
    processing (data packet) : No data
    can anyone share ideas on this
    thanks and regards
    Edited by: AAL123 on Sep 26, 2011 7:17 AM

    Hi,
    Check the below given SAP Notes,
    Note: 580869 ( RFC calls can be processed with report RSARFCEX) & 530997.
    Regards,
    Durgesh.

  • Patch upgrade in Source system ECC 6

    Hi,
    We are plannig Patch upgrade in the ECC 6 r/3 System. This is source system for BI7 (NW2004s).
    I want to know, we beibg a BI consultant
    1. What we need to check in ECC on patch upgrade.
    2. What precautions we need to take for better facilitating the patch upgrade in ECC 6
    3. Other related things.
    can someone please reply.

    Hi
    check patch level in BI system :---
    Logon to your SAP System
    SYSTEM>STATUS>Click the search buttion under SAP System Data
    Where you can find your patchelev.
    BI Content and Plug-in Information
    These are the links to get detailed information about BI Content and Plug-in.
    Check the release notes in this link:
    http://help.sap.com/saphelp_nw70/helpdata/en/bc/52a4373f6341778dc0fdee53d224c8/frameset.htm
    Dependencies of BI_CONT Add-Ons: Functional Correspondences
    https://websmp207.sap-ag.de/~sapdownload/011000358700007362962004E/func_corresp.htm
    Dependencies of BI_CONT Add-Ons: Technical Prerequisites:
    https://websmp207.sap-ag.de/~sapdownload/011000358700007362972004E/tech_prereq.htm
    BI Extractors and Plug-in Information:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000682135&
    http://sap.seo-gym.com/copa.pdf
    http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    /thread/178564 [original link is broken]
    Asset Mgt Data
    http://gnanamax.com/Documents/BI%207.0%20Functional%20Upgrade%20-%20Migration%20points.pdf
    /thread/507115 [original link is broken]
    Go to sap logon pad on the top left side of the logon pad u can see a small click option beside the logon gui for eg: sap logon710 or 640. click on that and select about sap logon there u can c the patch level, build, file name, file version etc,
    Hope it helps
    regards
    gaurav

  • Impact of upgrade of SAP R3 source system on BW system

    Hi Experts,
    Could you please help me to list down the impacts on BW system due to upgrade of SAP R3 source system?
    [1] Is there any impact if R3 is upgraded to Unicode restricted version from a version where Unicode restriction was not mandatory?
    [2] With respect to delta loads what will be the threat?
    [3] With respect to Business contents modifications by SAP's new upgraded version, can be there be any threat?
    Any inputs will be appreciated... Thanks in advance!
    Regards, Somenath

    Please specify which version of BW u r using.
    A direct upgrade to ECC6.0 is possible from a minimum lower version of R/3 3.1i and not below that and coming to BW an upgrade to BI 7.0 is possible from a minimum lower version of BW 3.0B and not below that.
    The compatibilty is possible with an addition of some Plug -In's or Patches.
    There will not be much of problem,

Maybe you are looking for