timeout after opening change history assignment block in account overview

[Former Member]

Hi experts,

we have Problem that our Change history is not viewable in same cases (timeout occures only with "big" customers. this account has thousands of relationsships). After ten minutes we get timeout. What are the possibilities to avoid this issue, WITHOUT increasing timeout Settings?

Here is error message:

• The following error occurred in system CRP : No more storage space
  available for extending an internal table.
• The termination type was: RABAX_STATE
• The ABAP call stack was:
  Form: SELECT_CDPOS of program SAPLSCD1
  Form:
  READ_CDPOS_FROM_DB_NO_TABKEY of program SAPLSCD1
  Form: READ_CDPOS_FROM_DB of
  program SAPLSCD1
  Function: CHANGEDOCUMENT_READ_HEADERS of program
  SAPLSCD1
  Form: AENDERUNGSBELEGE_LESEN of program SAPLBUSA
  Function:
  BUS_CHANGE_DOCUMENT of program SAPLBUSA
  Function: CRM_BUPA_IL_READ_CHANGEDOCS
  of program SAPLCRM_BUPA_BOL
  Method: READ of program
  CL_BUPA_IL_CHANGE_HISTORY=====CP
  Method: PROCESS_CHILDREN of program
  CL_BUIL_ABSTR=================CP
  Method: PROCESS_CHILDREN of program
  CL_BUPA_IL_HEADER=============CP

Thanks in advance.

Anna

[navn_metts]

Hi Anna,

The error description itself says its memory problem. Please contact your basis team for this issue. They will suggest you the solution.

Or else you can check where exactly the program was terminated in the error analysis. and check why the specific internal table is getting too many entries.

Br,

Navn

[Former Member]

Thanks for reply. The Problem is that there are to many relationships on this account. But how can this got resolved? Extend the database memory? Or any other Suggestion?

Thanks!!

Best Regards,

Anna

[Former Member]

Hi Anna

If they're not prepared to purge the data and Basis have no other configuration changes that they can apply, then I think the next course of action is an investment in memory.

Have a chat with the Basis Team and get their recommendations on what would be required.

In addition, you could log an Incident with SAP for them to investigate, they may have some notes / recommendations on how to resolve without investing further.

Regards

Arden

[Former Member]

Hi Anna

The only thing I can recommend is to purge Old Change History Entries after X Period.

Regards

Arden

[Former Member]

Thanks for reply but this is not a good solution as our user needs all entries!

Any other Suggestion?

Best Regards,

Anna