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

Extracting Purchasing Data to PO Cube

Dear All,

Just for your information, We could able to extractthe Purchase info to the existing Purchase Cube without any problemstill 30-12-2004.

Just to reload the data we have deleted the existing data from Purchase Cube. We have not made any changes to the existing purchase cube. Now we tried todo Delta Initialization but it is not working.

The Error is , The job is running too long and also hanging.

Request still running

Diagnosis

No errors could be found. The current process has probably not finished yet.

System response

The ALE inbox of the SAP BW is identical to the ALE outbox of the source system

and/or

the maximum wait time for this request has not yet run out

and/or

the batch job in the source system has not yet ended.

Current status

in the source system

Please kindly help me.

Regards,

Tham Kannan

thamkannan@gamil.com

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

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

    Hi Tham,

    check sm37 and sm21 in your source system. May be there is a long delay time for the job, may be the job dumped for any other reason. In this case, BW does not recognize a error and the request will remain yellow.

    regards

    Siggi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 17, 2005 at 12:47 PM

    Hi Tham:

    Siggi's response was accurate. It is true that sometimes failures during extraction are not properly communicated to the RSMO data load monitor. You can utilze the features of the data load monitor to guide your troubleshooting, though. The step-by-step analysis can guide you to the background jobs SM37 for the extraction in the source system. You may want to look at systemic issues at the time of the extraction (source system - was it overloaded with jobs, etc). You can often find dumps in ST22 for the ALEREMOTE (or simillar) user - match the approximate time of the failure of the load with the time frame in which a dump may have occurred.

    Furhermore, the deletion of the data from the cube should have reset the delta status, but you may want to make sure you do that from the menu in the InfoPackage, prior to running the delta init.

    Also note that you can set a timeout parameter per InfoPackage. Look at the history of the loads to determine the reasonable maximum time for the completion of the load (for an InfoPackage), then add 30 min & set a timeout. That way, if the data load has been running for X amount of time the light goes from yellow to red. Thus any triggers you have set in the process chain to catch failures (email notification, for example) will let you know when the job has been moved to a failed status b/c of timeout.

    regards -

    Ron

    Message was edited by: Ronald Silberstein

    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.