Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Unable to use RSA1/RSPC in Production - BW 7.4

Hi Guys,

Came across a strange problem. I am unable to access RSA1 and RSPC in BW 7.4. Key points to be noted:

- I am able to access RSA1 and RSPC in Development and Quality system, problem only in production

- Problem only for me and few other users. Most people are able to access RSA1 and RSPC

- Our system in BW 7.4 SAPKW74008

- Was able to access till last week

Session times out and throws a short dump :

Category           ABAP Programming Error
Runtime Errors     TIME_OUT
ABAP Program       CL_RSAWBN_TREE_MODEL_FOLDER===CP

Application Component  BW-WHM-AWB

Short Text

Time limit exceeded

What happened?

Program "CL_RSAWBN_TREE_MODEL_FOLDER===CP" has exceeded the maximum
  uninterrrupted runtime and has
therefore been terminated.

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

After a certain time, the program is terminated in order to free the
workspace for other users. This prevents workspaces from being blocked
unnecessarily, for example by an endless loop (DO, WHILE, ...), by
database accesses where the result set is too large or by database
accessess without a suitable index Index (full table scan).

The maximum runtime of a program is set by system profile parameter
"rdisp/scheduler/prio_[high|normal|low]/max_runtime". The current setting is
  600 seconds. Once this limit has been
exceeded, the system attempts to interrupt the SQL statement or to
instruct the ABAP processor to terminate the program. It waits for a
maximum of 60 seconds. If the program is then still active, the work
process is restarted.

How to correct the error

    It is best to start programs that take a long time to run as batch

    jobs. If this is not possible, system profile parameter

     "rdisp/scheduler/prio_[high|normal|low]/max_runtime" can be

    increased.

    Depending on the cause of the error, the following actions might also

    be necessary:

    - Endless loop: correction in program;

    - Database where the result set is too large: Use "SELECT * INTO

    internal table" for example instead of "SELECT * ... ENDSELECT";

    - Database access without suitable index: Check generation of index.

    If the error occurs in a non-modfied SAP program, you might be able to

    find a solution in the SAP Notes system. If you have access to the SAP

    Notes system, check there first using the following keywords:

    "TIME_OUT"

    "CL_RSAWBN_TREE_MODEL_FOLDER===CP" bzw. CL_RSAWBN_TREE_MODEL_FOLDER===CM001

    "CREATE_FOLDER_TREE"

    If you cannot solve the problem yourself, please send the following

    information to SAP:

    1. This description of the problem (short dump)

    To do this, choose  System -> List -> Save -> Local File (unconverted)

    on the screen you are in now.

    2. A suitable system log

    To do this, call the system log in transaction SM21. Restrict the time

    interval to ten minutes before the short dump and five minutes after

    it. In the display, choose System -> List -> Save -> Local File

    (unconverted).

    3. If these are programs of your own, or modified SAP programs: Source

    code of these programs

    To do this, choose  More Utilities -> Upload/Download -> Download in

    the Editor.

    4. Details regarding the conditions under which the error occurred or

    which actions and input caused the error.

Any Suggestions what is going wrong. Its only me and couple of users who are facing this problem and rest of the team can access RSA1 and RSPC.

Any suggestions ? What is going Wrong

Best Regards

Ritesh Singh

Former Member
Former Member replied

Hi Guys,

Finally the problem was solved. There was problem with table's RSCOMPTLOGO & RSCOMPTLOGOT. While importing some BPC transport (by Basis as part of OSS note) one entry for NODESNOTCONNECTED was not maintained correctly in table RSCOMPTLOGO and an extra entry for NODESNOTCONNECTED was inserted in table RSCOMPTLOGOT.

Collected only the entry for NODESNOTCONNECTED in table RSCOMPTLOGO (Transport request automatically collected the entry for NODESNOTCONNECTED for table RSCOMPTLOGOT) and imported the transport request to quality and production. After importing the transport the entry for NODESNOTCONNECTED was corrected in table RSCOMPTLOGO and the extra entry for NODESNOTCONNECTED was deleted automatically from table RSCOMPTLOGOT.

Happy to answer any more questions.

BR

Ritesh Singh

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question