Processing is Overdue

Hi BW Experts,
       I have a problem in my process chain.
   We r loading HR processs chain (Full Load) daily.
   Today i got a problem in HR Process Chain.
   The message has shown like this.
                                      Request still running
                            Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
in the source system
      But iam unable to understand this problem.
Could u pls anyone solve this problem.
Iam very helpless here.
   Thanks & Regarsd
               Anjali

Hi Teja,
Thanks for the good response .
But when iam trying to do Manually Update, but its not working.
Iam unable to do Manually Update.
Then what should i do.
The message displays like this.
                         (Green) Requests (messages): Everything OK
>> (Red) Extraction (messages): Missing messages
                         (Green) Data request received
                         (Green) Data selection scheduled
                         (Yellow)Missing message: Number of sent records
                         (Yellow)Missing message: Selection completed
>> (Red) Transfer (IDocs and TRFC): Errors occurred
                              (Red) Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
>>(Green) Processing (data packet): Everything OK
>(Green) Data Package 1 ( 100029 Records ) : Everything OK
                        (Green)Update PSA ( 100029 Records posted ) : No errors
                        (Green) Transfer rules ( 100029 -> 100029 Records ) : No errors
                        (Green) Update rules ( 100029 -> 200058 Records ) : No errors
                        (Green) Update ( 200058 new / 0 changed ) : No errors
                        (Green) Processing end : No errors
>> (Red) Process Chains : Errors occurred
Please tell me process
Thanks & Regards
Anjali

Similar Messages

Infopackage: Processing is overdue

Hello:
I'm trying to load data in an Infopackage connect to MS SQL datasource. In RSA1, the defined source system runs successfully, I´m be able to view tables/view and the data test (20 records).
But when I created an infopackage and try to load it, the system returns, after time out set up, Processing is overdue, with 0 records retrieve.
I think that problem is regarding with role DB user problems, but my user can get data from RSA1 and not trouhgt load data to infopackage. My DB user have DB_OWNER role.
Thanks in advance,
Abel

Hi all:
Thanks for your help, but my problems still happend. After error, I checked the short dump in BW and it´s empty, the system log is empty too. The system error is:
No IDocs created; Database system
Diagnosis
No IDocs were created. The IDocs are created in BW with database systems as source systems. Since no IDocs were created, a short dump in BW probably occurred.
System response
Procedure
Check the short dumps in BW.
Procedure for System Administration
Thanks

Error : Processing is overdue

when loaing data to psa from SAP R/3 .
RSMO - 7777 From 0 and request status is showing Yellow.
complete message given below.
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
Edited by: venkatraju m on Feb 7, 2008 7:57 AM

Hi,
Try this.
Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
Thanks,
JituK

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

How to solve Caller 70 Missing-Processing overdue

Hi Folks,
Plz tell me how to rectify Processing overdue error which i m getting during data loading from PSA to Data Target.
Thanks
Ranjan Singh

Hi,
processing time for loading is too long.
You can manually book data if all records from source system has arrived into PSA. Just right click on the data packet that was not updated and select "Manual Update".
See the below links.
Short dump in the Warehouse Caller 70" is missing
collor 70 missing
Error :Processing is overdue
GTR

Process Chain - Processing overdue

can any one tell me when do i get this error in a process chain object.. n also what do i need to do to correct this error.. we have started it manually ..
ERROR MESSAGE is as follows on an object :-
Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse that are not updated. Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.

HI,
following could be done to avoid this.
1) Increase the background processes i the bw system.
2) Prioratize the chain with class job A by going to sm37.
3) try the data loads when the system load is low.
4) same withe r/3 system too. if the r/3 systems processors are busy it leads to time out errors.
Hope it helps.
sampath

Regarding the process overdue

hello everybody,
i got an error saying that process is overdue.please tell me what shud i do ?
thank you,
madhusudhan

hi,
atually this process overdue error comes only if the transfer of data is taking much time.
go to status tab make the QM status to red .then goto edit->update reversal->readeverything manually.then automatically every thing will be corrected.
regards,
jack

Process overdue error

Hi all,
How to reslove the process overdue error and TRFC errors.Plz tell me
Rgds
Bharath

HI
Follow these threads
Process Overdue error
error: process overdue
Process is overdue (during dataload)
error like process ovedue in extraction data
Khaja

Process overdue error:Idocs inflow BW

Hi All,
When we are scheduling an infopackage we are encountering an error as "Process is overdue" and also says Idocs inflow BW.In the status tab we are finding the following details:
Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
When we go to Detail tab we found red status in the extraction itself as:
Extraction (messages): Missing messages
If we are going for manual updation of the IDOCs by process manually we get :Data packets were found that have not yet been read
Data packets have to be processed manually
and finally we recieve a message as
You can only process data idocs in simulated form in warehouse.
How to go about resolving this issue.

Hi,
Try this
solution to these kind of problem is to use your mouse to click on every possible drill down field/line
You can use We05/We02 ..a lot many other Xns to see the status and actual error message associated.
But as I said use drill down & find the real error.
Re: ALE IDOC inbound processing
Regards
Siddhu
Message was edited by: sidhartha

Issue while loading Master Data through Process Chain in Production

Hi All,
We are getting an error in Process chain while loading Master Data
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
I had checked the PSA also but I could not find any record and the strange thing is, Job itself is not getting scheduled. Can any one help me out in order to resolve this issue.
Regards
Bhanumathi

Hi
This problem is not related to Process chain..
u can try this..
In RSMO, select the particular load you want to monitor.
In the menu bar, Environment >>> Transact. RFC >>> Select whichever is required, BW or Source System.
In the next screen you can select the Execute button and the IDOCS will be displayed.
Check Note 561880 - Requests hang because IDocs are not processed.
OR
Transact RFC - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
(from JituK)
Hope it helps
Darshan

Arrived in BW Processing: Data packet not yet processed

Hello Gurus,
Data is being loaded from export datasource (8RL*****) ti 2 data targets
The overall QM status is red (says processing is overdue)
The details tab shows
Extraction: Error occurred
Transfer(IDoc and TRFC): Error occurred
Processing (Data packet): Error occurred
   -- Transfer rule: Error occurred
     Bewegungsdaten received.Processing being started
     Message missing(35676 records) : Transfer rule finished
Update rule (0 records):Missing messages
Update(0 new/0 changed): Missing message
Processing end: Missing message
I checked the LUW in SM58 but didnt find anything.
I checked infosource (PSA) - one request is in RED, but when i check the data in PSA there are no errors.
What should I do in this case?
What might be the excat error.
Kindly inform.
Regards,
NIKEKAB

Hi,
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then checl the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
Thanks
Reddy

Initialialized delta process(very urgent)

Hi all,
I am loading transaction data into master data table and the update mode is initialized data process.Today the loading were failed showing processing is overdue and i have made the QM status red and deleted the request.When i reran the infopackge its giving the message " delete init request requ_dr1.... before running init with same selection".I have checked in data request this request number is not there.
the datas are loaded daily as "initialized delta processc" update method..
Could anybody tell me how to delete the request and again reload the data..its very urgent...
Thanks
Manjula

hi...
did u upload to target level or not...?where u got the red alert in update level or target level...?before dis you should know the delta mode functiion...intially you can upload the datas using full mode....if use full mode that will take the datas only once for target...for example....if you are loading 40 records...when the uploading process method have done without any mistakes...it's showing 40 records in the target level also..
DELTA MODE:
but you are getting only 30 records...you may upload the remaining 10 datas by delta mode function...through a new source file...
if you can't get my point ...mssg me....
regards,
ramanan..

IDOCS Process Manually

Hi
Extraction is getting terminated with red status (0 for 0 records). The message in the status tab is:
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
There is a Button "Process manually". After i clicked on that button, i got a msg "Incorrect data packets are now updated again.". After this i could not see any action.
How to go about solving this problem. When do we face this kind of problem and wats the reason?
Help is reallly appreciated.
Regards
Rak

Hi
my status is 23409 from 23409 records and in red status.
In status
Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
MEthod 1
Then Environment>ALE management>In datawarehousing.
Then given the IDOC number and executed. The next screen appeared is idoc list where 64 status is in yellow color. But there is no option to process or execute that idoc.
Method 2.
BD87 in BW..Given the IDOC number and executed..There is a node "IDoc entries in tRFC queue. But when i select that and click on process, a error msg is being displayed "the operation cannot be carried with this node type".
What should do it to process.
REgards
Rak

Info Package in Process Chain - Performance Issue

Dear All,
We have some Info Package in Process Chain which when triggered initially turns red, then again yellow, after sometime red/green. These status keeps changing and finally results in green status. These infopackage takes 15-30 mins to complete.
And the info package error message shows "Processing time overdue". The chain runs daily and this issue also occurs on a daily basis.
Does anyone one of you have an idea of how to deal with this performance issue?
Regards.

Hi
As you said--
"initially time out time was set to 10 mins, so it was turning red at 10 mins. Later i changed it to 30 mins, then it is turning red at 30 mins, this info package takes maximum 20 mins to complete.
thatsy i asked whether there will be any problem if we remove this time out time."
I guess, its not mandatory to include the timeout value. Just try to execute the IP without entering the timeout value.
It should work.
Let me know if this helps.
Regards
SaiPrasad

Hi, I am getting the following error while booting up cisco asa firewall .

Hi,
I'm getting the following error form console when booting up Cisco ASA firewall...
How do we determine the issue if its hardware or software related?
ERROR: Type:2; Severity:80; Class:1; Subclass:3; Operation: 3

Dear Ravi,
You are getting the message of time out because you must be loading huge volume of data and BW runs for a specific peroid of time and then it gives a dump with message as processing is overdue.what you can do is first you should drop the indexes of the cube and then you should manually load the data-packets.I think you can again load the failed data package.select the failed data package in the monitor screen.then go to edit(on upper left next to monitor).In Edit select Init update then select "settings for further update" now select that process should be run in the background.Now right click on the failed datapacket and select Manual update.
Hope this works for you.
With Regards,
Prafulla

Processing is Overdue

Similar Messages

Maybe you are looking for