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

How to trick DELTA Update?

Hi to All,

We wanted to implement a Minimized Downtime for our live R/3 when BW comes along. As we all know, INITs take a long long time to process specially if you have 1 year worth of data to load to BW and we cannot afford downtime even for a day. Thats where the PDF Document "How to Minimize Downtime for DELTA Init" comes to life.

For info of others on how this thing works. These are the basic steps.

1.) Make the BW User as DEBUGGING User under RSADMIN

2.) Send an INIT Request via Info Package to R/3 Live

3.) Perform Flash Copy of the Server

4.) Connect BW Prod to Flash Copy

5.) Trigger the request IDOC from Flash Copy (BD87) and proceed with extraction...

Now the problem is if an error occured during the extraction process in Flash Copy to BW Prod (say table space issues). How could we resend a new request whose Request Number is still the OLD Request Number so that it is still in SYNC with R/3 Live...As we all know, any discrepancy with the REQUEST NUMBER will cause ABAP Runtime Error "Message TYPE X".

--Jkyle

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 14, 2005 at 10:22 AM

    Hello? Anybody please???

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 15, 2005 at 07:11 AM

    Hi Jkyle,

    In order to resolve the table space problem (due to overload in PSA) temporarly, you can deactivate the aggrregates of any large cube and for a permanent solution, you can increase the table space for the PSA.

    Thanks,

    Gokul

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Gokul,

      Thanks for the answer.

      Unfortunately, the table space problem is only an <i>example</i> of an error. We can fix that easily and theres no problem about it.

      The problem is how to <b>RESEND</b> the request using the <b>OLD Request Number</b> in the info package without creating a new one because in my scenario the <i>old request number</i> is the one present in R/3. Creating a new request will therefore cause inconsistencies when we reconnect BW to R/3 Live...

      <i>--Jkyle</i>

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.