cancel
Showing results for 
Search instead for 
Did you mean: 

RAISE_EXCEPTION-SYSTEM_FAILURE while doing Stock CCR in background

Former Member
0 Kudos

HI Guru ,

Im getting this message whenever my stocks ccr job running in background gets cancelled..

Following is the dump we get in st22

***************************************************

<b>ShrtText</b>

Exception condition "SYSTEM_FAILURE" raised.

-


<b>Error analysis</b>

A RAISE statement in the program "/SAPAPO/SAPLCIF_DELTA3" raised

condition "SYSTEM_FAILURE".

Since the exception was not intercepted by a superior program

in the hierarchy, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

-


<b>Information on where terminated</b>

The termination occurred in the ABAP program "/SAPAPO/SAPLCIF_DELTA3" in

"/SAPAPO/CIF_DELTA3_STOCK".

The main program was "/SAPAPO/CIF_DELTAREPORT3 ".

The termination occurred in line 80 of the source code of the (Include)

program "/SAPAPO/LCIF_DELTA3U40"

of the source code of program "/SAPAPO/LCIF_DELTA3U40" (when calling the editor

800).

The program "/SAPAPO/SAPLCIF_DELTA3" was started as a background job.

Job name........ "CCR-STOCK-DAILY"

Job initiator... "CIF"

Job number...... 01000801

********************************************************************

Regards

Anthony

Accepted Solutions (0)

Answers (2)

Answers (2)

sebastian_goebel
Explorer
0 Kudos

Hi Anthony,

this sounds like the message that is thrown when APO calls to R/3 and the parallel task can either not be started or gets canceled. You should look for a dump in R/3 that occurs at the same time.

My guess for this is that the parallel task in R/3 for selecting data gets canceled due to a time out. Even when calling CCR in a background task the RFC-calls to R/3 are foreground tasks (this is a technical restrictions) and therefore only have a limited runtime (see profile parameter 'rdisp/max_wprun_time'). Increasing the maximum runtime or using smaller datasets (parallelization?) will help in this case.

Best regards,

Sebastian

former_member788297
Participant
0 Kudos

hi,

seems issue with performance,

check number of entries in table BDCPV, if more clear the same.

update table statistics: CIF_IMMARC

Regards,

Chava