XPRA_EXECUTION error during EHP 1 for SAP NetWeaver 7.0

[Former Member]

Hi gurus!!

During ABAP upgrade to EHP1 using SAINT, we receive the

following XPRA_EXECUTION error when system try to upgrade the component SAPK-701DWINSAPBASIS

Short text

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

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_WS_MD_VIF_FUNC=============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_WS_MD_VIF_PARAM============CP " in include

"CL_WS_MD_VIF_PARAM============CI " in

line 24:

"Type "SEWS_TTY_TYPES_IN_PARAM" is unknown"

" "

" "

" "

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

terminated because it has come across a statement that unfortunately

cannot be executed.

Any ideas??

Many thanks.

Juan Triulcio.

[sunny_pahuja2]

Hi,

Could you please check log files of this phase at OS level and also paste error here ?

Thanks

Sunny

[Former Member]

Hi, Sunni

Actually this error is not an ABAP DUMP, this error occurs when the upgrade try to execute the job u201CRDDEXECLu201D . And the text that I put in the first message is the log of that JOB.

The problem is : u201CType "SEWS_TTY_TYPES_IN_PARAM" is unknownu201D

Thanks.

Juan.

[sunny_pahuja2]

Hi Juan,

What is the kernel version of your system ? Update system to kernel with latest release.

Also check this [link|http://www.sap2048.com/known-problems-with-support-packages-in-sap-nw-71-as-abap-381.htm] For probable reason for cancellation of this job.

Thanks

Sunny

[Former Member]

Hi Sunny

We are running SAP kernel 701

[jorge_velasquez]

Hi,

Type T-code SGEN and execute ''Regenerate Existing Loads'' .Continue with your patching after this finishes.

It will work for you

Regards.

[Former Member]

Hi, Jorge, We run the SGEN, but we steel having the same error... Thanks for your help..