Error in phase XPRA_EXECUTION in Support Package

[Former Member]

Dears,

We are getting an error in

XPRA_EXECUTION phase when I checked logs it says:

Program terminated (job: RDDEXECL, no.: 10591900)

See job log

Execution of programs after import (XPRA)

End date and time : 20080825105934

Ended with return code: ===> 12 <===

Log of Job says that :

5.08.2008 10:53:30 Job started

5.08.2008 10:53:30 Step 001 started (program RDDEXECL, variant , user

ID DDIC)

5.08.2008 10:53:30 All DB buffers of application server prosindia were

synchronized

5.08.2008 10:54:51 This action is not supported in system NET

5.08.2008 10:54:57 This action is not supported in system NET

5.08.2008 10:55:43 This action is not supported in system NET

5.08.2008 10:55:44 This action is not supported in system NET

5.08.2008 10:57:57 ABAP/4 processor: SYNTAX_ERROR

5.08.2008 10:57:57 Job cancelled

Please help .

[markus_doehr2]

Does the same error occur again if you repeat the phase?

Markus

[Former Member]

Yes Markus,

Repeated several times but same error.

Also checked that getting dumps "Syntax Error" everytime i execute Support Pack.

Runtime Errors SYNTAX_ERROR

Date and Time 25.08.2008 14:34:28

Short text

Syntax error in program "CL_FDT_ADMIN_DATA=============CP ".

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_FDT_FACTORY================CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"CL_FDT_ADMIN_DATA=============CP " in include

"CL_FDT_ADMIN_DATA=============CM010 " in

line 1:

"Method "SAVE_DOCU_DB" is not declared or inherited in class "CL_FDT_AD"

"MIN_DATA" - - - - - - - - - - -"

" "

" "

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 "CL_FDT_FACTORY================CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Please eliminate the error by performing a syntax check

(or an extended program check) on the program "CL_FDT_ADMIN_DATA=============CP

".

You can also perform the syntax check from the ABAP Editor.

If the problem persists, proceed as follows:

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

The following syntax error was found in the program

CL_FDT_ADMIN_DATA=============CP :

"Method "SAVE_DOCU_DB" is not declared or inherited in class "CL_FDT_AD"

"MIN_DATA" - - - - - - - - - - -"

" "

" "

Simialrly I was also getting Syntax error in other programme that i solved manually by creating a method.

But now i am feeling that there is some problem with database like might be there are inconsistencies.

Please suggest.

Deepak.

[markus_doehr2]

Did something happen during the import? Machine/database crash?

Markus

[Former Member]

No.Markus...Nothing like this happened.

But somedays one more issue was in Support package that after applying support pack also ther were not visible in system means like in System->Status and on other places also.

Deepak.

[Former Member]

Hi,

Syntax error in class CL_FDT_ADMIN_DATA

method SAVE_DOCU_DB is not define.

if you have any other system with same release then create a workbench request from se80 -> class ->CL_FDT_ADMIN_DATA -> in method select method SAVE_DOCU_DB -> right click -> other function -> write transport entry

edit this request using SE09 and add following content also in request

LIMU CLSD CL_FDT_ADMIN_DATA
LIMU CPRI  CL_FDT_ADMIN_DATA

release the request and import in in problematic system.

regards,

kaushal

[Former Member]

Hi Kaushal,

Issue is that this is not the only class that is creating problem for us,Same problem was also in other classes that i resolved maually by creating methods.

So now i am thinking that there is some problem with the database consistency or problem with particular support pack,I am applying SAPKB70013.

Kernel is already upgraded and SPAM version is 23.

Deepak.

[markus_doehr2]

Are you able to check if you implemented

Note 1023163 - X message when you save enhancement implementations

prior to the start of the SP13 installation?

Markus

[Former Member]

Hi,

I gave the solution for given problem.

i did not think so there is problem with the database consistency, problem with only importing SP13 for basis

check Note 822379 - Known problems with Support Packages in SAP NW 7.0 AS ABAP and search for SAPKB70013

regards,

kaushal

[markus_doehr2]

There´s a documented error in the note you just posted - that´s why I refer to the other note...

Markus

[Former Member]

No Markus,

I have not applied Note 1023163 - X message when you save enhancement implementations.

Deepak.

[markus_doehr2]

Ok - in that case I see two possibilities:

- use the workaround provided by Kaushal and go on

- open an OSS call under BC-UPG-OCS and let the support have a look on the system so you know the reason for this error and can avoid it next time you install SP13 on a different/production system.

Markus

[Former Member]

Hai,

You can try by increasing the SPAM level and also the kernel level. Also check the tablespace sizes..

Thanks and Regards,