topic Re: ossnote in Application Development and Automation Discussions

ossnote

Former Member — Tue, 03 Apr 2007 13:23:10 GMT

Error analysis

After a certain length of time, the program is terminated. In the case

of a work area, this means that

- endless loops (DO, WHILE, ...),

- database accesses producing an excessively large result set,

- database accesses without a suitable index (full table scan)

do not block the processing for too long.

The system profile "rdisp/max_wprun_time" contains the maximum runtime of a

program. The

current setting is 600 seconds. Once this time limit has been exceeded,

the system tries to terminate any SQL statements that are currently

being executed and tells the ABAP processor to terminate the current

program. Then it waits for a maximum of 60 seconds. If the program is

still active, the work process is restarted.

successfully processed, the system gives it another 600 seconds.

Hence the maximum runtime of a program is at least twice the value of

the system profile parameter "rdisp/max_wprun_time".

the above information is the abap dump for the fico

for this dump iam implementing the oss note it match this not can you tell me

Symptom

You start a totals record report (for example, report group 5AO2) and you want, for example, examine the costs for internal orders.

For a more detailed analysis you want to branch from there into the line item report. This results in very long runtimes which may result in a timeout.

Other terms

Key words: TIME_OUT, LI report, line item report, COVP, COEP, COBK,

background job, object selection, account assignment object, background,

reconciliation report

Function modules: K_LINE_ITEM_ACT_CALL_WITH_DATA,

K_LINE_ITEM_PLN_CALL_WITH_DATA,

K_LINE_ITEM_DEV_CALL_WITH_DATA,

K_LINE_ITEM_CM_CALL_WITH_DATA

Program: RKAEP000, SAPLKAEP

Transactions: KSB1, KOB1, S_ALR_87013611

Reason and Prerequisites

The error occurs particularly in cases in which a very large number of line items must be selected. Therefore, take particularly SAP Note 115219 into account.

Solution

Correct the cost centers which are described in the attachement in the specified function modules.

Re: ossnote

Former Member — Tue, 03 Apr 2007 13:31:27 GMT

Hi!

Go to:

http://service.sap.com/notes

Regards

Tamá

Re: ossnote

Former Member — Tue, 03 Apr 2007 13:44:42 GMT

Hi,

Alwways restrict the selection of entries in selection screen.

Don't leave blank and execute.

enter one cost center group or few range of cost centers or elements, so that it executes within the less time.

Ask your basis person to increase the run time from 600 seconds to little more.

Or schedule such type of reports in the back ground.

reward if useful

regards,

Anji

Re: ossnote

Former Member — Tue, 03 Apr 2007 14:07:43 GMT

in the selection screen there is mandatory field i should give and i have to excute.

then its going the dump.

can i use these oss note for the runtime error for the actuval line items(when i excute the report its taking time and going to the dump)

thats iam using the oss note,its match or not

here is the dump

Error analysis

After a certain length of time, the program is terminated. In the case

of a work area, this means that

- endless loops (DO, WHILE, ...),

- database accesses producing an excessively large result set,

- database accesses without a suitable index (full table scan)

do not block the processing for too long.

The system profile "rdisp/max_wprun_time" contains the maximum runtime of a

program. The

current setting is 600 seconds. Once this time limit has been exceeded,

the system tries to terminate any SQL statements that are currently

being executed and tells the ABAP processor to terminate the current

program. Then it waits for a maximum of 60 seconds. If the program is

still active, the work process is restarted.

successfully processed, the system gives it another 600 seconds.

Hence the maximum runtime of a program is at least twice the value of

the system profile parameter "rdisp/max_wprun_time".

here is the oss note description

Symptom

You start a totals record report (for example, report group 5AO2) and you want, for example, examine the costs for internal orders.

For a more detailed analysis you want to branch from there into the line item report. This results in very long runtimes which may result in a timeout.

Other terms

Key words: TIME_OUT, LI report, line item report, COVP, COEP, COBK,

background job, object selection, account assignment object, background,

reconciliation report

Function modules: K_LINE_ITEM_ACT_CALL_WITH_DATA,

K_LINE_ITEM_PLN_CALL_WITH_DATA,

K_LINE_ITEM_DEV_CALL_WITH_DATA,

K_LINE_ITEM_CM_CALL_WITH_DATA

Program: RKAEP000, SAPLKAEP

Transactions: KSB1, KOB1, S_ALR_87013611

Reason and Prerequisites

The error occurs particularly in cases in which a very large number of line items must be selected. Therefore, take particularly SAP Note 115219 into account.

Solution

Correct the cost centers which are described in the attachement in the specified function modules.