cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Error RAISE EXCEPTION

Former Member
0 Kudos
2,534

Hi All,

Repeatedly getting runtime error 'RAISE_EXCEPTION' in SCM system.

The details of error is given below:

Exception condition "GENERATE_SUBPOOL_DIR_FULL" raised

The current ABAP/4 program encountered an unexpected

situation.

Error Analysis:

A RAISE statement in the program "CL_ALV_TABLE_CREATE===========CP" raised the

exception

condition "GENERATE_SUBPOOL_DIR_FULL".

Since the exception was not intercepted by a superior

program, 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.

SCM system is currently at SCM 500 SP level 13.

Can any one please let me know what is the exact reason of this dump or how can I find reason of this dump.

Thanks !

Varun

-

View Entire Topic
DavidLY
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

The reason is that the method

CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE

that gets called, needs to create a dynamic subroutine (I don't know

why). There is a limit for the number of these, which is 36.

CL_ALV_TABLE_CREATE belongs to software component BASIS and is therefore

relevant for your system. Otherwise you could not use (call) the objects

of this component.

Check SAP note 505644.

And that's why we see the dump, when there will be more than

36 (it may happen earlier as there may ne other processes having

generated some as well) navigation steps.

Regards,

David

Former Member
0 Kudos

Thanks David !

I already checked NOTE 505644 but its for older releases.

Can you please advise that can we do something for this issue or this is a totally ABAP issue and I seek help from ABAP team.

DavidLY
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

The note 505644 does not mean that the error

GENERATE_SUBPOOL_DIR_FULL

will never apppear anymore, but states clearly that it makes this error

explicitly catchable by the caller. And that is exactly why we see the

dump.

And that's why we see the dump, when there will be more than

36 (it may happen earlier as there may ne other processes having

generated some as well) navigation steps.

Regards,

David

Former Member
0 Kudos

Thanks David for the information.