Skip to Content
0
Former Member
Jul 26, 2008 at 07:01 PM

SAPKB70013 stopped at XPRA_EXECUTION

18 Views

Hi All,

While importing Support Packages for NW 2004s, Basis component , Patch : SAPKB70013,

SPAM Phase stopped at XPRA_EXECUTION,

Reason for error : TP_STEP_FAILURE,

Return Code : 0012

Error Message : OCS package SAPKB70013 ,tp step R, return code 0012.

Before this error occurred, SPAM prompted for SPDD adjustment, i called up SPDD and checked in the system , all the elements under With Modification Adjustment are green tick in front of the object.

I returned back and choose Confirm Adjustment and continued with patching and strucked at XPRA_EXECUTION.

i have checked ST22, has short dump with SYNTAX_ERROR.

Runtime Errors SYNTAX_ERROR

-


-


Short text

Syntax error in program "SAPLSXMBCONF ".

-


-


What happened?

Error in the ABAP Application Program

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

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSXMBCONF " in include

"LSXMBCONFU20 " in

line 658:

"The field "CO_PARAM_TABLE_SWITCH" is unknown, but there is a field wit"

"h the similar name "CO_PARAM_ACL_CHECK". "CO_PARAM_ACL_CHECK"."

" "

" "

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_XMS_PERSIST_ADM============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 "SAPLSXMBCONF ".

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 SAPLSXMBCONF :

"The field "CO_PARAM_TABLE_SWITCH" is unknown, but there is a field wit"

"h the similar name "CO_PARAM_ACL_CHECK". "CO_PARAM_ACL_CHECK"."

" "

" "

-


-


User and Transaction

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Transactions ID..... "48891376E27F63AEE100000095C38BAA"

Program............. "CL_XMS_PERSIST_ADM============CP"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-


-


Information on where terminated

Termination occurred in the ABAP program "CL_XMS_PERSIST_ADM============CP" -

in "CLASS_CONSTRUCTOR".

The main program was "RSAL_BATCH_TOOL_DISPATCHING ".

In the source code you have the termination point in line 39

of the (Include) program "CL_XMS_PERSIST_ADM============CM008".

The program "CL_XMS_PERSIST_ADM============CP" was started as a background job.

Job Name....... "SAP_CCMS_MONI_BATCH_DP"

Job Initiator.. "DDIC"

Job Number..... "1630420C"

-


Any help is appreciated.

Naren.