Problem While accessing GLPCA & BSEG

[Former Member]

Hi,

After 4.7 to ERP Upgrade, Some of the Dipslay T-codes Where we are using GLPCA & BSEG table For ex

MB03 & MIR4 we are getting abap dump at select SQL statements ( ABAP DUMP) with Time out.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

What happened?

The program "SAPLPCRW" has exceeded the maximum permitted runtime without

interruption and has therefore been terminated.

______________________________________________________________________________

How to correct the error

Programs with long runtime should generally be started as background

jobs. If this is not possible, you can increase the system profile

parameter "rdisp/max_wprun_time".

Depending on the cause of the error, you may have to take one of the

following measures:

- Endless loop: Correct program;

- Dataset resulting from database access is too large:

Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table

(for example);

- Database has unsuitable index: Check index generation.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"TIME_OUT" " "

"SAPLPCRW" or "LPCRWU09"

"COPCA_DOCUMENT_RECORD"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:v

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

User and Transaction

Client.............. 301

User................ "WIPRO-SUPP"

Language key........ "E"

Transaction......... "MB51 "

Transactions ID..... "485CADED3C346A56E1000000AC14408A"

Program............. "SAPLPCRW"

Screen.............. "SAPLMIGO 0001"

Screen line......... 18

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Information on where terminated

Termination occurred in the ABAP program "SAPLPCRW" - in

"COPCA_DOCUMENT_RECORD".

The main program was "MB_CALL_MIGO_DIALOG ".

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

of the (Include) program "LPCRWU09".

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

SELECT * FROM glpca INTO TABLE lt_glpca

WHERE rldnr = gc-ledger

AND refdocnr = cop_awref

AND awtyp IN lr_awtyp "4.7

AND aworg IN lr_aworg " 701907

AND refdocct = cop_refdocct

AND kokrs IN lr_kokrs

AND rbukrs IN lr_bukrs

AND poper IN lr_poper.

++++++++++++++++++++++++++++++++++++++++++++++

Same Transaction is running perfectly in our old version 4.7.

[matt]

If you have a problem with a standard SAP transaction - log a call with SAP.

In the meantime, check the indexes on GLPCA. Using SE14, check that they are all active in the database.

I believe there are four standard indexes:

1 Profit-center-based index

2 Index with document number

3 Index Through Reference Document Number

7 Index with origin object / activity

matt

[Former Member]

Well I have checked all the indexes in se14 and all are active , The Program is doing Sequential read on the table and data is in huge amount around crores but The same is working in SAP 4.7 with in seconds.

[Former Member]

This message was moderated.