Skip to Content
0
Former Member
Nov 27, 2008 at 01:12 AM

BP error : NO_ACTIVE_TAB

2435 Views

Hi, all

I did technical upgrade R.3 ent to ECC 6.0.

during testing, BP transaction was terminated cause raised exception

NO_ACTIVE_TAB.

I searched SAP notes and then found some notes.

Note 872591 - BP_BDT BP maintenance terminates with NO_ACTIVE_TAB

this is not useful. I confirm this entry "2600000 FS5001 Additional

Data" aleady existed.

Note 696189 - SAP BP Error message NO_ACTIVE_TAB

this is not yet. but I guess not useful too.

and I aleady chekc r notes 389793, 600318 and 618123 but all unuseful.

I attach part of short dump in st22

Runtime Errors RAISE_EXCEPTION

Date and Time 2008.11.26 09:47:52

Short text

Exception condition "NO_ACTIVE_TAB" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

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

exception

condition "NO_ACTIVE_TAB".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

User and Transaction

Client.............. 100

User................ "M1KD0100"

Language key........ 3

Transaction......... "BP "

Transactions ID..... "492BEB6EF00E7446E10000000A8701FA"

Program............. "CL_BUS_TABSTRIP===============CP"

Screen.............. "SAPLBUPA_DIALOG_JOEL 1100"

Screen line......... 4

Information on where terminated

Termination occurred in the ABAP program "CL_BUS_TABSTRIP===============CP" -

in "MODIFY_TABSTRIP_PBO_BEGIN".

The main program was "SAPLBUPA_DIALOG_JOEL ".

In the source code you have the termination point in line 15

of the (Include) program "CL_BUS_TABSTRIP===============CM00D".

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.

thanks all