Skip to Content
author's profile photo Former Member
Former Member

Plug-in Upgrade in R/3 what's needed on BW Side

We are in the process of upgrading from 3.0b to 3.5 on the BW side. In order to do this, the R/3 Plug-in was upgraded to 2004.1 patch level 5. This is the first time we've done this kind of thing. My question is, I have numerous process chains that failed in BW because of the timestamp difference in R/3 and BW. The message tells me I need to replicate the datasource. I ran RS_TRANSTRU_ACTIVATE_ALL in BW thinking this would solve my problem but it didn't. Do I need to transport the DataSources again from R/3 into BW and then replicate the source system and then run RS_TRANSTRU_ACTIVATE_ALL? If this is the case, I ran the 'delta' in SBIW and loads of datasources popped up as changed most of which we've never transported to BW in the first place and nothing is activated on the BW side to go with them. Can someone tell me what it is I should do so that my transfer rules will get an updated timestamp and my process chains will again run correctly?

Thanks for any help,

Diane Merrill

Oak Ridge National Lab

UT-Battelle

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Feb 03, 2005 at 07:25 PM

    Hi Diane,

    We just finished an upgrade from 3.0b to 3.5. The steps we took before upgrading the plug-in:

    1. lock out all end users & stop all scheduled jobs in R/3.

    2. Run V3 jobs in R/3 and run all delta jobs in BW.

    3. After data is updated in BW, run all delta jobs again, they should be 0 of 0 to BW.(This insures that you have updated all data in BW)

    4. Then upgrade the plug-in.

    5. After upgrade is finished replicate all data sources.

    6. If all was done correctly to this point you should not loose any delta data loads.

    7. If you have to replicate individual data sources do so.

    We had some replication issues but between replication and reactivating transfer rules we loaded everything and did not loose a single delta.

    Hope this helps

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 03, 2005 at 07:07 PM

    Hi Diane,

    I would try these steps:

    - Replicate the source system, then try running your infopackage again

    - If that does not work, re-activate your transfer rules then try running your infopackage again

    Cheers! Bil

    Message was edited by: Bill Faison

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 03, 2005 at 09:43 PM

    Thanks to both of you. After the replication, the process chains ran correctly. At least this time I didn't have to re-activate the transfer rules.

    Thanks for tuning in and helping people with issues.

    Diane

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.