EWA Error

[Former Member]

Hi,

The EWA is showing data is available , but when i try to run the SM:EXEC SERVICES job manually, it creates the dump

Error in the ABAP Application Program

The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "RDSVASCEW_DBORA____________05

" in include "RDSVASIEW_DBORA____________059 " in

line 69:

"INCLUDE report "/1CAGTF/IF_LOGFUNC_000482" not found."

" "

" "

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "SAP "

Error in the ABAP Application Program

The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The same is the error if i track through the session number in DSA.

Also the /DBL/Task Processor job is not running.

I have tried with the service definitions reset, and SESSION_REFRESH job in the solman system , still no use.

Also checked with the function module /BDL/_GENERATE_LOGFUNCINCLUDES

it also generates errors.

Logical function: ADA_CACHE_STATISTICS :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000001

Interface data missing.

Logical function: ADA_DBTAB_OHNE_DBIDX :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000002

Interface data missing.

Logical function: ADA_DB_FILLING :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000003

Interface data missing.

Logical function: ADA_DB_PERFORMANCE :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000004

Interface data missing.

Logical function: ADA_LOG_STATISTICS :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000005

Interface data missing.

Logical function: ADA_MISSING_INDICES :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000006

Interface data missing.

Logical function: ADA_PARAMETER :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000007

Interface data missing.

Logical function: ADA_REGION_STATISTICS :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000008

Interface data missing.

Logical function: ADA_ST04 :

Error 10 during generation of /1CAGTF/IF_LOGFUNC_000009..............................................................................................................................

lot of them..

any Idea how to solve this ??

I am on ABA and BASIS SP 14.

Rest all upto Stack 15 level.

Regards,

Kaustubh.

[former_member209604 · Accepted solution]

Hi Kaustubh,

the reported SYNTAX_ERROR is well known.

With SolMan Stack 15, you can perform the following steps

- Run transaction SDCCN

- Choose in the menu Menu Utilities -> Maintain Service Definitions -> Select 'Delete and Replace Service Definitions

- Confirm this selection -> Confirm that you want to delete the definitions -> Confirm that a new task 'Service Definition Refresh' was created

- Take a note of the task id -> Review the log for this task id when it is completed. You should not see any errors for either the update of a Service Definitions table or the generation of any re-import include.

See for details

[SAP Note 727998 - Complete Replacement of Service Definitions for SDCC/SDCCN|http://service.sap.com/sap/support/notes/727998]

Best regards,

Ruediger

[Former Member · Accepted solution]

Hi Reudiger,

The problem is solved.

I just copied and rescheduled the BDL/task Processor task ,, and it was successful this time..

why was this not runnig before i have no idea, even though i had replaced the service defn, and created a session refresh task in solman.

Regards,

Kaustubh.

[Former Member]

no comments for my querry.

closing the thread.

[Former Member]

I have seen many watchers for this thread.

So just wanted to ask if anyone has idea for,,

why was the job not running before and why did it start now?

what might be the possible reasons?

I think this may be due to the authorization for the users.

first time i used a general user.

then i re-scheduled the job using solman.

was this the only problem for the function module to fail also?

Regards,

Kaustubh.

[Former Member]

Solved by re-scheduling the BDL/Task Processor job