Processing overdue error during delta extraction from datasource 0CO_OM_CCA

[Former Member]

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

[Former Member]

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

[Former Member]

Thanks Todd,

that was very useful information. We'll look into the note for alternative solution if needed.

Hari Immadi

http://immadi.com

SEM BW Analyst

[Former Member]

Hari Immadi,

Please confirm whether index 1 and 4 are active on table COEP in source R/3 system. Please see OSS Note 382329 for more details.

Todd

[Former Member]

Hi Todd,

Thanks for your quick reply. We don't have index 4 @ database level & we are currently working on that. Is this is what causing deltas not to work for us?

We have a requirement to pull in deltas every hour.

Also, Is it true that CCA_9 datasource has 2 hour limit for delta ? If this is the case, hourly deltas doesn't work for us right? What are the possible solutions for us to get hourly deltas?

Appreciate your help.

Hari Immadi

http://immadi.com

SEM BW Analyst

[Former Member]

I hope the delta issue is because of IDOC/Transact RFC error... You can go to SM58 -> Select the transID which is hanging (transaction recorded) and then execute the LUW...Else u can take the IDOC number from details tab of the monitor(IDOC which got struck) and then in R/3 can execute it in BD87...

For executing delta's frequently check whether ur DS supports real time data acquision...

Regards,

B

[Former Member]

Check if this may help :

/thread/628421 [original link is broken]

Note 416265 - BCT-CO delta DataSources: Technical background information