1AETR012XProgram terminated (job: "RDDEXECL", no.: "11463401") at XPRAS_UPG

Hi,
we are perfoming an upgrade of CRM 4.0 to CRM 5.0. First there was a problem at the phase XPRAS_UPG executing the job RDDEXECL it generated the short dump SYNTAX_ERROR but it was solved following the note 961410 - Add. info. on upgrading to SAP ECC 6.0 SR2 ABAP. After this the upgrade process continue but now we got an error at the same phase (XPRAS_UPG) during the execution of the same JOB (RDDEXECL), but the diference is that now it is generating the short dump CALL_FUNCTION_NOT_FOUND, as is shown at the bottom (just a part of this).
I have been looking for notes and posts in many different forums, but I couldn't find a solution, please help me to solve this issue.
Regards,
Jorge Ramírez Carrasco.
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          23.04.2008 16:42:53
Short text
Function module "CRM_IPM_DPL_O_EXTDELTA" not found.
What happened?
     The function module "CRM_IPM_DPL_O_EXTDELTA" is called,
     but cannot be found in the library.
Error in the ABAP Application Program
The current ABAP program "SAPLCRM_IPM_TEMPLATE_IF" had to be terminated because
      it has
come across a statement that unfortunately cannot be executed.
What can you do?
     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
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
      not caught in
     procedure "CRM_IPM_GENERIC_IF_XML" "(FUNCTION)", nor was it propagated by a
      RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program "SAPLCRM_IPM_TEMPLATE_IF" contains the CALL FUNCTION statement.
The name of the function module to be called is "CRM_IPM_DPL_O_EXTDELTA".
No function module exists with the name "CRM_IPM_DPL_O_EXTDELTA".
All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attention to
   upper/lower case and underscores ("_").
   or
b) Transport error
c) In the case of an enqueue/dequeue module,
   the lock object may not have been activated
   (ABAP/4 Dictionary).
to correct the error
Check the last transports to the SAP System.
Is the program "SAPLCRM_IPM_TEMPLATE_IF" currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CALL_FUNCTION_NOT_FOUND" "CX_SY_DYN_CALL_ILLEGAL_FUNC"
"SAPLCRM_IPM_TEMPLATE_IF" or "LCRM_IPM_TEMPLATE_IFU25"
"CRM_IPM_GENERIC_IF_XML"
Function modules with names similar to "CRM_IPM_DPL_O_EXTDELTA":
CRM_IPM_DPL_P_EXTDELTA
CRM_IPM_DPL_O_EXTSELOPT
CRM_IPM_DPL_O_EXTRACT
CRM_IPM_DPL_O_ENQUEUE
CRM_IPM_DPL_O_SAVE                                                          CRM_IPM_BVAL_O_DELETE
    CRM_IPM_DPL_O_CREATE
    CRM_IPM_DPL_O_PROCESS
    CRM_IPM_DPL_O_REFRESH
    CRM_MKTPL_DELTAB_TO_EXTRACT
If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
    (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
The exception must either be prevented, caught within proedure
    "CRM_IPM_GENERIC_IF_XML" "(FUNCTION)", or its possible occurrence must be
     declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
System environment
    SAP-Release 700
     Application server... "SRVJRZPCRC"
     Network address...... "10.10.0.5"
     Operating system..... "Windows NT"
     Release.............. "5.2"
     Hardware type........ "8x Intel 801586"
     Character length.... 8 Bits
     Pointer length....... 32 Bits
     Work process number.. 14
     Shortdump setting.... "full"
Database server... "SRVJRZPCRC"
     Database type..... "MSSQL"
     Database name..... "CRS"
     Database user ID.. "crs"
Char.set.... "Spanish_Spain.1252"
SAP kernel....... 700
     created (date)... "Feb 4 2008 01:00:09"
     create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
     Database version. "SQL_Server_8.00 "
Patch level. 146
     Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
     SAP database version. 700
     Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
      NT 6.0"
Memory consumption
     Roll.... 8112
     EM...... 36585360
     Heap.... 0
     Page.... 409600
     MM Used. 28622832
     MM Free. 2731464
     User................ "DDIC"
     Language key........ "S"
     Transaction......... " "
     Program............. "SAPLCRM_IPM_TEMPLATE_IF"
     Screen.............. "SAPMSSY0 1000"
     Screen line......... 6
Information on where terminated
     Termination occurred in the ABAP program "SAPLCRM_IPM_TEMPLATE_IF" - in
      "CRM_IPM_GENERIC_IF_XML".
     The main program was "RDDEXECU ".
In the source code you have the termination point in line 104
     of the (Include) program "LCRM_IPM_TEMPLATE_IFU25".
     The program "SAPLCRM_IPM_TEMPLATE_IF" was started as a background job.
     Job Name....... "RDDEXECL"
     Job Initiator.. "DDIC"
     Job Number..... 16320601
     The termination is caused because exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"
      occurred in
procedure "CRM_IPM_GENERIC_IF_XML" "(FUNCTION)", but it was neither handled
      locally nor declared
     in the RAISING clause of its signature.
The procedure is in program "SAPLCRM_IPM_TEMPLATE_IF "; its source code begins
      in line
1 of the (Include program "LCRM_IPM_TEMPLATE_IFU25 ".
Source Code Extract
Line SourceCde
74 *              raising internal_error.
    75 *    endif.
76
77     if sr_ixml is initial.
    78       sr_ixml = cl_ixml=>create( ).
    79     endif.
User and Transaction
     Client.............. 000
       User................ "DDIC"
     Language key........ "S"
     Transaction......... " "
     Program............. "SAPLCRM_IPM_TEMPLATE_IF"
     Screen.............. "SAPMSSY0 1000"
     Screen line......... 6
Information on where terminated
     Termination occurred in the ABAP program "SAPLCRM_IPM_TEMPLATE_IF" - in
      "CRM_IPM_GENERIC_IF_XML".
     The main program was "RDDEXECU ".
In the source code you have the termination point in line 104
     of the (Include) program "LCRM_IPM_TEMPLATE_IFU25".
     The program "SAPLCRM_IPM_TEMPLATE_IF" was started as a background job.
     Job Name....... "RDDEXECL"
     Job Initiator.. "DDIC"
     Job Number..... 16320601
     The termination is caused because exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"
      occurred in
procedure "CRM_IPM_GENERIC_IF_XML" "(FUNCTION)", but it was neither handled
      locally nor declared
     in the RAISING clause of its signature.
The procedure is in program "SAPLCRM_IPM_TEMPLATE_IF "; its source code begins
      in line
1 of the (Include program "LCRM_IPM_TEMPLATE_IFU25 ".
Source Code Extract
Line SourceCde
74 *              raising internal_error.
    75 *    endif.
76
77     if sr_ixml is initial.
    78       sr_ixml = cl_ixml=>create( ).
    79     endif.

I think that I found the source of the problem, when I started the upgrade the system CRM 4.0 had the support package level SAP ABAP & BASIS = 63, when the prepare asked if I wanted to include some support packages I selected "NOT". The problem here is how to find the support package which include the function module "CRM_IPM_DPL_O_EXTDELTA" and then try to apply it. There is an other option, stop the upgrade and then restart it and include all the support packages involved.
Any suggestion or recomendation?? am I right??
as soon as I Solve this problem I'm going to let you know, may be some body will need it.
Regards,

Similar Messages

1AETR012XProgram terminated (job: "RDDEXECL", no.: "15172901") durinmg XPRA

Hello,
We are in the process of upgrading CRM 4.0 to CRM 5.0 and the below error occured in the phase of XPRAS_UPG
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZDA.CDU
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "15172901")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""15172901""CDU"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
Background:
Source release : CRM 4.0 in Windows 2003 with SQL 2000 (ABAP Stack)
Target Release : CRM 5.0 in Windows 2003 with SQL 2005 (ABAP Stack)
Appreciate your quick response on this.
With Warm Regards,
Vadivambal

Hi,
I could login to the original system with DDIC and here is the job log for RDDEXECL
09.04.2008 15:17:29 Job started 00 516 S
09.04.2008 15:17:29 Step 001 started (program RDDEXECL, variant , user ID DDIC) 00 550 S
09.04.2008 15:17:29 All DB buffers of application server MTW02SDCR01 were synchronized PU 170 S
09.04.2008 15:17:31 ABAP/4 processor: SYNTAX_ERROR 00 671 A
09.04.2008 15:17:31 Job cancelled 00 518 A
Short Dump:
09.04.2008 15:17:29 Job started 00 516 S
09.04.2008 15:17:29 Step 001 started (program RDDEXECL, variant , user ID DDIC) 00 550 S
09.04.2008 15:17:29 All DB buffers of application server MTW02SDCR01 were synchronized PU 170 S
09.04.2008 15:17:31 ABAP/4 processor: SYNTAX_ERROR 00 671 A
09.04.2008 15:17:31 Job cancelled 00 518 A
09.04.2008 15:17:29 Job started 00 516 S
09.04.2008 15:17:29 Step 001 started (program RDDEXECL, variant , user ID DDIC) 00 550 S
09.04.2008 15:17:29 All DB buffers of application server MTW02SDCR01 were synchronized PU 170 S
09.04.2008 15:17:31 ABAP/4 processor: SYNTAX_ERROR 00 671 A
09.04.2008 15:17:31 Job cancelled 00 518 A
09.04.2008 15:17:29 Job started 00 516 S
09.04.2008 15:17:29 Step 001 started (program RDDEXECL, variant , user ID DDIC) 00 550 S
09.04.2008 15:17:29 All DB buffers of application server MTW02SDCR01 were synchronized PU 170 S
09.04.2008 15:17:31 ABAP/4 processor: SYNTAX_ERROR 00 671 A
09.04.2008 15:17:31 Job cancelled 00 518 A
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 %_CSCPR :
 "The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
 "n the Dictionary control structure introduced with "CLASS". "CLASS". ""
 "CLASS". "CLASS". "CLASS"."
How to correct the error
 Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
 notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
 (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
 Restrict the time interval to 10 minutes before and five minutes
 after the short dump. Then choose "System->List->Save->Local File
 (Unconverted)".
Runtime Errors SYNTAX_ERROR
Date and Time 09.04.2008 15:17:29
Char.set.... "English_United State"
SAP kernel....... 700
 created (date)... "Mar 3 2008 01:20:17"
 create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
 Database version. "SQL_Server_8.00 "
Patch level. 150
 Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
 SAP database version. 700
 Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
 NT 6.0"
Memory consumption
 Roll.... 8112
 EM...... 7317072
 Heap.... 0
 Page.... 32768
 MM Used. 891304
 MM Free. 1197840
User and Transaction
 Client.............. 000
 User................ "DDIC"
 Language key........ "E"
 Transaction......... " "
 Program............. "SAPLSCPRPR"
 Screen.............. "SAPMSSY0 1000"
 Screen line......... 6
Runtime Errors SYNTAX_ERROR
Date and Time 09.04.2008 15:17:29
Information on where terminated
 Termination occurred in the ABAP program "SAPLSCPRPR" - in
 "SCPR_DB_ATTR_GET_LIST".
 The main program was "RDDEXECU ".
In the source code you have the termination point in line 0
 of the (Include) program " ".
 The program "SAPLSCPRPR" was started as a background job.
 Job Name....... "RDDEXECL"
 Job Initiator.. "DDIC"
 Job Number..... 15172901
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 2
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1 CORR
SY-MSGV2 MERG
SY-MSGV3
Runtime Errors SYNTAX_ERROR
Date and Time 09.04.2008 15:17:29
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080409
SY-UZEIT 151729
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
 Name
7 FUNCTION SAPLSCPRPR ??? 0
 SCPR_DB_ATTR_GET_LIST
6 FUNCTION SAPLSCPRPR ??? 0
 SCPR_DB_ATTR_GET_ADDITIONAL
 5 FUNCTION SAPLSCPRCRITICAL ??? 0
 SCPR_SCP2_AFTER_IMPORT
4 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 342
 CALL_IMP_METHODS_IN_CLIENT
 3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 87
 CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 103
 TRINT_CALL_AFTER_IMP_METHOD
 1 EVENT RDDEXECU RDDEXECU 171
 START-OF-SELECTION
Chosen variables
Name
Val.

Error in transport, ended with return code: 12, job RDDEXECL cancelled

Hi Friends,
When I am trying to import a request in a BW preproduction system, it is giving below error: However, the transport is imoprted successfully in Quality.
===================================
Program terminated (job: RDDEXECL, no.: 09222300)
See job log
Execution of programs after import (XPRA)
End date and time : 20080509092238
Ended with return code: ===> 12 <===
Job log:
Date Time Message
09.05.2008 09:22:23 Job started
09.05.2008 09:22:23 Step 001 started (program RDDEXECL, variant , user ID DDIC)
09.05.2008 09:22:23 All DB buffers of application server unix0001 were synchronized
09.05.2008 09:22:25 ABAP/4 processor: UNCAUGHT_EXCEPTION
09.05.2008 09:22:25 Job cancelled
=======================================
Kindly advice.
Thanks & regards,
Kunal Patel.

Hello,
I ran a search for this error and found the following notes:
SAP Note 966234 - 70SP10: DTP transport and content error
SAP Note - 1074388 SAPBINews NetWeaver 7.0 BI Support Package 16
Check if they are relevant for your system.
Regards,
Siddhesh

Transport of Transformation failed with RC= 12 and job: RDDEXECL cancelled in Target sytem

Gurus,
When i am importing the workbench request from dev to qty.
I am getting error : Program terminated (job: RDDEXECL, no.: 22321300).
Transformation contains only Endroutine.
Job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxxxxx were synchronized
The internal session was terminated with the runtime error UNCAUGHT_EXCEPTION (see ST2
Job cancelled.
When i see the dump it is througing errror at the method of following class.
CL_RSO_TLOGO_PERSISTENCY-CHECK_INITIALIZED
Could you please help. Thanks in advance.
Ashok

Hi Ashok,
In QA use program "RSTRAN_ROUT_RSFO_CHECK" to check and remove any inconsistencies for the transformations. After that again transport those transformations in new TR and import in QA.
Also you have to search "Transport of Transformation failed with RC= 12 and job: RDDEXECL canceled in Target system" by Dinesh Tiwari.
Check the reply of Fun Sébastien in http://scn.sap.com/message/13795238#13795238.

Job RDDEXECL terminated with error.

Hi!
I am facing with hanging SPAM error in phase IMPORT_PROPER (patch of SAPKB70013 - SAPKB70016).
The SPAM patch terminates after a few sec. in DDIC activation action.
I have looked into log file and founded folllowing:
The job RDDEXECL terminated with error.
The reason seems to be sysntax error in program "CL_PROXY_SERVICE=======CP".
Futhermore I could detect that table SI_WD_FIRST_MAIN_SCREEN cannot be activated.
Can some one help me to solve this problem?
Of great interest was the following:
rescedule possibilities of job RDDEEXECL in order to contibue patch
start of SPAM or tp-commando by ignoring this error
Any helpful information will be very appreciated!
Holger

What do you mean with reimport?
I tried for almost 100 times to restart the import.

Problem with job RDDEXECL (STMS)

Hi Coleagues
The problems is that job RDDEXECL(Execution of programs for post - import processing) is canceled during execution.
with the error:
*What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLPRGN_UTILITIES" had to be terminated because one
     of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLSUPRN ", the following syntax error occurred
    in the Include "LSUPRNF3J " in line 117:
    "Different number of parameters in FORM and PERFORM (routine: AUTH_NEW_"
    "AUTH, number of formal parameters: 3, number of actual parameters: 2)."
    Author and last person to change the Include are:
    Author "SAP "
    Last changed by "SAP "*
I have performed the checking of syntax for programs involved and checked if occur some change in this programs recently.
I not found nothing.
My sap is ECC 5.0 on Unix with oracle .
Could anyone let me know where is the issue please ?

Hi Deepika
The version of this report is the same in the all environments. In the others environments this report works without problems.
More details about error:
A Thu Jan 5 21:57:51 2012
A *** ERROR => Syntax error in program SAPLSUPRN
A *** ERROR => > Include LSUPRNF3J                                line 117
A *** ERROR => > Different number of parameters in FORM and PERFORM (routine: AUTH_NEW_AUTH, numb
A *** ERROR => > er of formal parameters: 3, number of actual parameters: 2).
tks
Edited by: Marcos A. Magalhães Jr on Jan 5, 2012 10:32 PM

Error in transport, job RDDEXECL cancelled, ended with return code: 12

Hi all,
When I am trying to import a request in a BW system from development to quality , it is giving below error:
Program Terminated (job:RDDEXCEL no:11315700) messg no:TR012
Please do needful
Thanks and Regards,
srinivas.m

Hi Gurus,
I have the same error "Error in transport, job RDDEXECL cancelled, ended with return code: 12" (Programa cancelado (job RDDEXECL, nº 09292900)).
I have checked all the steps that are in the "Note 1101187 - The OLAP tunnel" and they are implemented.
Find below the information about my BW system:
SAP_ABA     700     0024     SAPKA70024     Componente multiaplicaciones
SAP_BASIS     700     0024     SAPKB70024     Sistema Base SAP
PI_BASIS     2005_1_700     0024     SAPKIPYJ7O     PI_BASIS 2005_1_700
ST-PI     2008_1_700     0004     SAPKITLRD4     SAP Solution Tools Plug-In
SAP_BW     700     0026     SAPKW70026     SAP NetWeaver BI 7.0
BI_CONT     703     0016     SAPKIBIIQ6     Business Intelligence Content
ST-A/PI     01N_700BCO     0000          -     Servicetools for other App./Netweaver 04
I am trying to transport "Business Content (Statistics)", if this information can help you.
What can i do to solve the problem? I am finding some clue and i dont find anything. It will be much appreciated any idea to solve the problem.
Thanks in advance and kind Regards,
Manuel
Edited by: Manuel Guijarro on Oct 11, 2011 3:46 PM

XPRAS_UPG phase terminated

Hi all,
I am doing CU&UC "Combined Upgrade & Unicode Conversion", during Upgrade "XPRASUPG_" phase terminates, when checking in SM37, can see that RDDEXECL report was terminated, I executed the report manually in SE38 with success, and repeated the phase again, unfortunately with same result.
EXPRASUPG LOG
root@kvxi010 /usr/sap/put/log # view XPRASUPG.ELG
"XPRASUPG.ELG" [Read only] 51 lines, 2208 characters
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZG1.X82
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "08270700")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
"XPRASUPG.ELG" [Read only] 51 lines, 2208 characters
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZG1.X82
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "08270700")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""08270700""X82"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
Is there someone who can help me.
Thanks for help in advance

hello,
pls check that there are enough batch workprocesses
available. In transactino SM37 you can see the joblogs
of the failed jobs.
hope this helps.
kind regards,
andraes

Urgently Upgrade Stop In XPRAS_UPG Phase

Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
 Remaining change request found in buffer TVD.
 Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
XPRASUPG.ECO and R3up.ECO
the problem is with the RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
 22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17

The conversion of some code pages is not supported.
What happened? 
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
 An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
 'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
We saw this note:
122597 Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
676135 Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
This are the logs:
XPRASUPG.ECO
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
R3up.ECO:
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree Cardenas

Hi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas

Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative

Hi Gurus,
am upgrading from ecc 6.0 to ehp5 on dual stack system OS:Windows 2003 DB:oracle 10.2.0.2
i got below error in the MAIN_NEWBAS/XPRAS_UPG phase
XPRASUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-500AGINCPRXRPM.IJE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14152200")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""14152200""IJE"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server admin0001 were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
Dump at ST22:
Error analysis
 The following syntax error was found in the program
 CL_DPR_TASK_O=================CP :
 "Formal parameter "IV_PLANSTART" does not exist."
please help me solve
Thanks,
Venkat

Hi Sunny,
here is dump details..
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program CL_DPR_TASK_O=================CP
Application Component PPM-PRO-STR
Date and Time 06.12.2011 16:34:41
User and Transaction
 Client.............. 000
 User................ "DDIC"
 Language key........ "E"
 Transaction......... " "
 Transaction ID...... "04FA1FE12F6DF16DB7E400145E69764F"
 EPP Whole Context ID.... 34454438393637453445443839363745
 EPP Connection ID....... 34454442374143323445444237414332
 EPP Caller Counter...... 1
 Program............. "CL_DPR_STATUS_CHANGE_OBSERVER=CP"
 Screen.............. "SAPMSSY0 1000"
 Screen Line......... 6
 Debugger Active..... "none"
What happened?
 Error in the ABAP Application Program
 The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=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_DPR_TASK_O=================CP " in include
 "CL_DPR_TASK_O=================CM021 " in
 line 74:
 "Formal parameter "IV_PLANSTART" does not exist."
 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_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
Error analysis
 The following syntax error was found in the program
 CL_DPR_TASK_O=================CP :
 "Formal parameter "IV_PLANSTART" does not exist."
Information on where terminated
 Termination occurred in the ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" -
 in "SET_HANDLER".
 The main program was "R_DPR_PROJECT_ROLES_XPRA ".
 In the source code you have the termination point in line 12
 of the (Include) program "CL_DPR_STATUS_CHANGE_OBSERVER=CM00A".
 The program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" was started as a background job.
 Job Name....... "RDDEXECL"
 Job Initiator.. "DDIC"
Thanks in advance
Venkat

XPRAS_UPG error in DOWNTIME phase in EHP4

Hi,
I am getting the below error in XPRAS_UPG in DOWNTIME phase of EHP4 installation in ERP 6.0 on HP-UNIX and Oracle.
XPRA ERRORS and RETURN CODE in SAPRW70104.HD1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10302400")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10302400""HD1"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I was successfully able to umlock the system and in SM37 I could see the job log pointing to ST22. In ST22 we have many dumps related to error PXA_NO_FREE_SPACE. I found many notes in marketplace but all are referring the parameter abap/buffersize which needs to increased. I am a bit apprehensive about the fact that since we are in DOWNTIME phase and in the middle of XPRA execution phase should we increase the parameter and restart the system and then continue with the upgrade???
I have also tried to run the phase many times but the same error persists.
Please can anyone help me to come out of this problem.....
Thanks & regards,
Rozal

Hello Rozal,
You are correct XPRAS is a downtime 2 phase, but actually your system is up and running. It was started way back in phase "STARTSAP_NBAS" its just that you cannot use your system productively. XPRAS executes the XPRAS methods in the running system.
Its absolutely safe, you can change the parameter take a restart and continue further.
- Niraj

Error in XPRAS_UPG phase on SCPR_FLDV_TAB

Hi,
Has anyone experienced this error before when upgrading to ECC 6.0?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZDA.FR1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "00273700")
Long text:
    Cause
      Program "&V#&", which was started in the background, was terminated
      abnormally.
    System Response
      The system created a job log for the terminated program.
etc.etc.
When I then go to SM37 to look at the job log i find an ABAP syntax error message that generated a short dump:
Runtime error          SYNTAX_ERROR
Datum en tijd          16.11.2007 00:24:27
Korte tekst
Syntaxfehler im Programm "%_CSCPR ".
Wat is er gebeurd?
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Im Programm "%_CSCPR " ist im Include "%_CSCPR " in Zeile 17
der folgende Syntaxfehler aufgetreten:
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary control structure introduced with "CLASS" . . . . . ."
|    Autor und letzter Änderer des Includes sind:
Autor "SAP "
|    Letzter Änderer "SAP "
So for some reason this type SCPR_FLDV_TAB is defined in two places and SAPup won't allow me to ignore it.
I have opened a message with SAP on this problem as well, but this system is due to go live on Monday so any help that would speed up the resolution process will be very much appreciated.
Kind Regards,
Sander

Hi ,
Please refer to note 122597 and 816057 i request you to check the job logs in sm37 as well.
Regards,
iqbal

XPRA_UPG ERRORS UPGRADING TO ECC6

Hello Gurus
i am getting some errors during XPRAS_UPG.Ugrading from 4.7 to ECC6sr2 on Win2k3 64,SQL2005
I have checked R3up.ECO logs entries:
STARTSAP continues...
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 9616 terminated with status 12
Deleting file c:\usr\sap\put\log\XPRASUPG.ELG
Moving file c:\usr\sap\put\log\PROT.TMP to c:\usr\sap\put\log\SAPR700ZEA.NTP
Moving file c:\usr\sap\put\log\XPRASUPG.ELG to c:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file c:\usr\sap\put\tmp\MSGIN.LST
Deleting file c:\usr\sap\put\tmp\MSGOUT.LST
Deleting file c:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file c:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file c:\usr\sap\put\log\TP.ECO
Deleting file c:\usr\sap\put\bin\TRLIST.DMP
Deleting file c:\usr\sap\put\tmp\upalert.log
Deleting file c:\usr\sap\put\tmp\upalert.log
Copying file c:\usr\sap\put\buffer\NDP to c:\usr\sap\put\buffer\AFTXPRAS.BUF
Then i checked ACTUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAAAA700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC701.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC702.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG701.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG702.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAD70024.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60008.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60009.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
and
XPRASUPG.ELG:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZEA.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "16371300")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""16371300""NTP"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I tried to execute the job RDDEXECL as DDIC in client 000 and it doesn`t run it quickly cancels with an ABAP dump SYNTAX_ERROR.I checked notes 980194,905029,821032,813658
So i went and checked in SE09 ,request/task,display individually,the transport logs
c:\usr\sap\put\log\*SAPLA70010.NDP* and discovered what might be the source of the problem:in SAPKA70010
different nametabs for table SEOCLASSDF (field CLSSHAREDMEMORY).
different nametabs for table SEOCLASSDF (field WITH_UNIT_TESTS).
different nametabs for table SEOCLASSDF (field DURATION_TYPE).
different nametabs for table SEOCLASSDF (field RISK_LEVEL).
in all the listed transport requests/support packs by ACTUPG.ELG log so how do i fix this problem in order to finish the upgrade?
Any ideas are most welcome

Hi Attached is the dump:
Runtime Errors SYNTAX_ERROR
Date and Time 19.04.2008 16:47:26
Short text
Syntax error in program "%_CSCPR ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "%_CSCPR " in include "%_CSCPR "
in
line 17:
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary . control structure introduced with "CLASS" . . . . ."
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 "SAPLSCPRPR" 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 "%_CSCPR ".
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 %_CSCPR :
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary . control structure introduced with "CLASS" . . . . ."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "BDX1-sap02"
Network address...... "10.50.74.207"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "BDX1-SAP02"
Database type..... "MSSQL"
Database name..... "NDP"
Database user ID.. "ndp"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Feb 3 2008 22:36:38"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 146
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16128
EM...... 29329328
Heap.... 0
Page.... 32768
MM Used. 12958608
MM Free. 3797776
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "E384EEDB5E10F1EC892B001A64C1074E"
Program............. "SAPLSCPRPR"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSCPRPR" - in
"SCPR_DB_ATTR_GET_LIST".
The main program was "RDDEXECU ".
In the source code you have the termination point in line 1
of the (Include) program "LSCPRPRU17".
The program "SAPLSCPRPR" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 16472600
Source Code Extract
Line
SourceCde
>>>>>
FUNCTION SCPR_DB_ATTR_GET_LIST.
2
3
""Lokale Schnittstelle:
4
*" IMPORTING
5
*" VALUE(CATEGORY) TYPE SCPRATTR-CATEGORY DEFAULT SPACE
6
*" VALUE(COMPONENT) TYPE SCPRATTR-COMPONENT OPTIONAL
7
*" VALUE(RELEASE) TYPE SCPRATTR-MAXRELEASE OPTIONAL
8
*" VALUE(MAX_COUNT) TYPE I OPTIONAL
9
*" EXPORTING
10
*" REFERENCE(SEL_COUNT) TYPE I
11
*" TABLES
12
*" PROFS STRUCTURE SCPRXPROF OPTIONAL
13
*" VERSIONS STRUCTURE SCPRXVERS OPTIONAL
14
*" PROFTYPES TYPE SCPR_XPTYPES OPTIONAL
15
*" CLI_DEPS STRUCTURE SCPRXCLDEP OPTIONAL
16
*" CLI_CASS STRUCTURE SCPRXCLCAS OPTIONAL
17
*" REFTYPES STRUCTURE SCPRXRTYPE OPTIONAL
18
*" REFERENCES STRUCTURE SCPRXREF OPTIONAL
19
*" MODDATES STRUCTURE SCPRXDAT OPTIONAL
20
*" MODIFIERS STRUCTURE SCPRXMOD OPTIONAL
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
2
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
CORR
SY-MSGV2
MERG
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080419
SY-UZEIT
164726
SY-XPROG
SAPLSYST
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
Name
7 FUNCTION SAPLSCPRPR LSCPRPRU17 1
SCPR_DB_ATTR_GET_LIST
6 FUNCTION SAPLSCPRPR LSCPRPRU19 60
SCPR_DB_ATTR_GET_ADDITIONAL
5 FUNCTION SAPLSCPRCRITICAL ??? 0
SCPR_SCP2_AFTER_IMPORT
4 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 342
CALL_IMP_METHODS_IN_CLIENT
3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 87
CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 103
TRINT_CALL_AFTER_IMP_METHOD
1 EVENT RDDEXECU RDDEXECU 168
START-OF-SELECTION
Chosen variables
Name
Val.
No. 7 Ty. FUNCTION
Name SCPR_DB_ATTR_GET_LIST
CATEGORY
S
5
3
COMPONENT
222222222222222222222222222222
000000000000000000000000000000
MAX_COUNT
0
0000
0000
RELEASE
2222222222
0000000000
SEL_COUNT
0
0000
0000
CLI_CASS[]
Table[initial]
CLI_DEPS[]
Table[initial]
MODDATES[]
Table[initial]
MODIFIERS[]
Table[initial]
ORGIDS[]
Table[initial]
PROFOUT[]
PROFS[]
PROFTYPES[]
REFERENCES[]
REFTYPES[]
VERSIONS[]
CONTEXT_CLASSIC
2
0
CF_SOL_MANAGER
M
4
D
RTYPE_CUSTREC
CREC
4544
3253
RTYPE_TRANSPORT
TRAN
5544
421E
RTYPE_COPY
COPY
4455
3F09
ACT_DELETE
06
33
06
ACT_SHOW
03
33
03
OTYPE_TABLE
S
5
3
OTYPE_TLOGO
L
4
C
OTYPE_SPECIAL
T
5
4
OTYPE_UNKNOWN
U
5
5
RTYPE_NO_REFTYPE
2222
0000
ACT_MODIFY
02
33
02
OTYPE_VIEW
V
5
6
OTYPE_CLUSTER
C
4
3
ACT_CREATE
01
33
01
COL_BLUE
1
0000
1000
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLSCPRPR
5454545555222222222222222222222222222222
310C330202000000000000000000000000000000
ICON_CLI_DEP
@0V@
43542222222222222222
00600000000000000000
CFLAG_ANY
VAL
544
61C
No. 6 Ty. FUNCTION
Name SCPR_DB_ATTR_GET_ADDITIONAL
CATEGORY
S
5
3
READ_ATTR
X
5
8
READ_DOCU
2
0
READ_SWITCH
2
0
READ_TADIR
2
0
READ_TEXT
2
0
REMOVED_BCSETS
Table[initial]
PROFLIST[]
Table IT_44[10683x298]
FUNCTION=SCPR_SCP2_AFTER_IMPORTDATA=BCSETS
Table reference: 27
TABH+ 0(20) = 50C21557FE070000B0C21557FE07000000000000
TABH+ 20(20) = 1B0000002C000000BB2900002A010000FFFFFFFF
TABH+ 40(16) = 04570000080D000010000000C1248001
store = 0x50C21557FE070000
ext1 = 0xB0C21557FE070000
shmId = 0 (0x00000000)
id = 27 (0x1B000000)
label = 44 (0x2C000000)
fill = 10683 (0xBB290000)
leng = 298 (0x2A010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70FA6557FE070000
pgHook = 0x70FD6657FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 33 (0x21000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 10704 (0xD0290000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x60176657FE070000
collHook = 0x0000000000000000
ext2 = 0xB0416257FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0xF0C11557FE070000
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
SY-SUBRC
0
0000
0000
FC_CANCEL
RW
5522
2700
FC_TAKE_NEW
TAKN
5444
41BE
<%_TABLE_SCPRSATTR>
FC_VALUE_HELP
VHLP
5445
68C0
BCSET_RANGE
IEQV1_ISHER_REP_PQUSPIQ_US_NSCH_DEG
4455354544555455555554555554544544422222222222222222222222222222222
95161F93852F250F0153091F53FE338F45700000000000000000000000000000000
FC_DEL_SUBP
DELS
4445
45C3
%_DUMMY$$
2222
0000
%_ITAB_DELETE_LIST
Table[initial]
<WA_PROFLIST>
V1_ISHER_REP_PQUSPIQ_US_NSCH_DEGN00000000000000
5354544555455555554555554544544443333333333333322222222222222222222222222222222222222222222222
61F93852F250F0153091F53FE338F457E0000000000000000000000000000000000000000000000000000000000000
BCSET_RANGES
Table IT_45[10683x67]
FUNCTION=SCPR_DB_ATTR_GET_ADDITIONALDATA=BCSET_RANGES
Table reference: 28
TABH+ 0(20) = 60436257FE070000000000000000000000000000
TABH+ 20(20) = 1C0000002D000000BB29000043000000FFFFFFFF
TABH+ 40(16) = 045900003011000010000000C1248001
store = 0x60436257FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 28 (0x1C000000)
label = 45 (0x2D000000)
fill = 10683 (0xBB290000)
leng = 67 (0x43000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000068
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x40176757FE070000
pgHook = 0x50D89357FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 34 (0x22000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16304 (0xB03F0000)
lineAlloc = 10800 (0x302A0000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
BCSETS_ATTRS
Table[initial]
SYST
000000000000B200000000000000000000000000000000000000000000000000000000000000200000000000000000
000000001000B900000000000000000000000000100020001000000010000000000000000000A10000000000000000
ICON_CLI_CAS
@0V@
43542222222222222222
00600000000000000000
TCATEGORY_CUSY
CUSY
4555
3539
No. 5 Ty. FUNCTION
Name SCPR_SCP2_AFTER_IMPORT
IT_E071
Table IT_42[10683x180]
FUNCTION-POOL=SCTS_EXE_EXPFORM=CALL_IMP_METHODS_IN_CLIENTDATA=LT_E071
Table reference: 26
TABH+ 0(20) = 90EF1457FE07000020444C57FE07000000000000
TABH+ 20(20) = 1A0000002A000000BB290000B4000000FFFFFFFF
TABH+ 40(16) = 044C0000080D000010000000C9248001
store = 0x90EF1457FE070000
ext1 = 0x20444C57FE070000
shmId = 0 (0x00000000)
id = 26 (0x1A000000)
label = 42 (0x2A000000)
fill = 10683 (0xBB290000)
leng = 180 (0xB4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC01B6757FE070000
pgHook = 0x20276757FE070000
idxPtr = 0xD0B58457FE070000
shmTabhSet = 0x0000000000000000
id = 31 (0x1F000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 10736 (0xF0290000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0xD0F75357FE070000
collHook = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_E071K
Table[initial]
IV_IS_UPGRADE
X
5
8
IV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
IT_CLIENT
Table IT_39[1x4]
FUNCTION=TRINT_CALL_AFTER_IMP_METHODDATA=LS_SPEC_PARS-CLIENTS
Table reference: 18
TABH+ 0(20) = A0B91557FE070000000000000000000000000000
TABH+ 20(20) = 12000000270000000100000004000000FFFFFFFF
TABH+ 40(16) = 044C00002813000019000000C1248001
store = 0xA0B91557FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 18 (0x12000000)
label = 39 (0x27000000)
fill = 1 (0x01000000)
leng = 4 (0x04000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000077
occu = 25 (0x19000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x40F75357FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 28 (0x1C000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 25 (0x19000000)
lineAlloc = 25 (0x19000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
<WA_E071>
SAPK700ZEA 010684R3TRSCP2V1_ISHER_REP_PQUSPIQ_US_NSCH_DEG
5454333544222222222233333353555453535454455545555555455555454454442222222222222222222222222222
310B700A5100000000000106842342330261F93852F250F0153091F53FE338F4570000000000000000000000000000
<%_L001>
<%_L001>-PGMID
TTYPE_R3TR
R3TR
5355
2342
SYST-REPID
SAPLSCPRCRITICAL
5454545545454444222222222222222222222222
310C33023294931C000000000000000000000000
<%_L001>-OBJECT
OBJECT_TYPE_SBCSET
SCP2
5453
3302
CONTEXT_CLASSIC
2
0
ACT_STOP_ICON
@3U@
4354
0350
SCPR_AUTHORITY_CHECK
X
5
8
FLD_STATUS_FLD_NM_KEY
FLD_NM_KEY
44454454452222222222
6C4FEDFB590000000000
BCSETS
Table IT_44[10683x298]
BCSET
V1_ISHER_REP_PQUSPIQ_US_NSCH_DEGN00000000000000
5354544555455555554555554544544443333333333333322222222222222222222222222222222222222222222222
61F93852F250F0153091F53FE338F457E0000000000000000000000000000000000000000000000000000000000000
REMOVED_BCSETS
Table[initial]
PCAT_SWITCH
S
5
3
INFO_SEL_REC
4
0000
4000
INFO_NAMESPACE
7
0000
7000
INFO_EQUALIZE
8
0000
8000
INFO_COMMIT
5
0000
5000
INFO_SHOW
6
0000
6000
INFO_SEL_PROFS
9
0000
9000
INFO_COMMIT_SET
10
0000
A000
CFLAG_ANY
VAL
544
61C
T_MESSAGES
Table[initial]
T_MESSAGE
0
3222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SWITCH_BC_SET_ICON
@C1@
4434
0310
LTYPE_FIELD
FLD
4442
6C40
T_MESSAGE-LEVEL
0
3
0
No. 4 Ty. FORM
Name CALL_IMP_METHODS_IN_CLIENT
PS_SPEC_PARS-WITH_ASYNCH_MODE
2
0
SY-XPROG
SAPLSYST
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
PS_METHOD_CALL-METHOD_FB
SCPR_SCP2_AFTER_IMPORT
545555453544545544545522222222
3302F3302F16452F9D0F2400000000
GC_SCP2_AFTER_IMP
SCPR_SCP2_AFTER_IMPORT
545555453544545544545522222222
3302F3302F16452F9D0F2400000000
PS_SPEC_PARS-ASYNCH_MODE
2
0
GC_PARTNRPR_BACK_TO_STNDRD
1A&1B&1H&1I&2I&3R
34234234234234235
11612618619629632
PV_IS_UPGRADE
X
5
8
PS_CLIENT-CLIENT
222
000
GC_GNS_NO_DIFF
/0*/
2322222222
F0AF000000
LT_E071
Table IT_42[10683x180]
GC_GNS_NO_SPECIFIC
2222222222
FAF0000000
LT_E071K
Table[initial]
RELSET
RNO
544
2EF
PS_SPEC_PARS-WITH_CL_RESULTS
X
5
8
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
SYST-REPID
SAPLSCTS_EXE_EXP
5454545554545455222222222222222222222222
310C3343F585F580000000000000000000000000
DEVC_PREFIXNS
N
4
E
PS_SPEC_PARS-CLIENTS
Table IT_39[1x4]
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 3 Ty. FORM
Name CALL_IMP_METHODS
PV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
PV_NO_WORK_FOUND
2
0
GC_XPRA_COMPLETED
C
4
3
PT_CLIENT
Table IT_21[1x4]
PROGRAM=RDDEXECUDATA=GT_CLIENT
Table reference: 16
TABH+ 0(20) = 00AD1557FE070000000000000000000000000000
TABH+ 20(20) = 10000000150000000100000004000000FFFFFFFF
TABH+ 40(16) = 040000003808000019000000C1248001
store = 0x00AD1557FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 16 (0x10000000)
label = 21 (0x15000000)
fill = 1 (0x01000000)
leng = 4 (0x04000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000027
occu = 25 (0x19000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70AC1557FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 19 (0x13000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 25 (0x19000000)
lineAlloc = 25 (0x19000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LS_CLIENT_H
2222
0000
TTRA
T
5
4
SY
000000000000B200000000000000000000000000000000000000000000000000000000000000200000000000000000
000000001000B900000000000000000000000000100020001000000010000000000000000000A10000000000000000
PV_UPDATE_LOCKFLAG
X
5
8
PV_CTC
2
0
PV_STATLOG_FILE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL
AFTER_IMP SCPR_SCP2_AFTER_IMPORT #######È#######É###########ÿÿÿÿ
445455445254555545354454554454552222222220000000C0001000C00010000000FFFF
16452F9D003302F3302F16452F9D0F24000000000000000080007000900060000000FFFF
PV_IS_UPGRADE
X
5
8
PV_TOP_LEVEL
2
3
2
PS_SPEC_PARS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL-CLIDEP
2
0
PS_SPEC_PARS-WITH_CL_RESULTS
X
5
8
%_VIASELSCR
0
4
No. 2 Ty. FUNCTION
Name TRINT_CALL_AFTER_IMP_METHOD
IS_E070
SAPK700ZEA PRSAP SYSTSAPUSER 20080418120004
5454333544222222222255545222222255555455545222223333333333333322222222222222222222
310B700A51000000000002310000000039343105352000002008041812000400000000000000000000
IT_E071
Table IT_15

3.5 Upgrade error

Hello
We are trying to upgrade to 3.5 (from 3.1) & currently facing error in XPRAS_UPG phase
DEtails are as below
*************XPRA ERRORS and RETURN CODE in SAPRIBIFU1.EBD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10120701")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10120701""EBD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPRIBIFUZ.EBD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10120801")
Long text: see above
1AEPU320 See job log"RDDEXECL""10120801""EBD"
1 ETP111 exit code : "12"
has anyone faced the similar problem?
Thx
Praveen

Hello all:
The solution is to implement note 844007 manually. Since the upgrade is in progress, you need to use the commands:
tp unlocksys <SAPSID>
tp unlock_eu <SAPSID>
first before implementing the note.
Please all of you assign 10 points as this is going above and beyond the OSS customer message process.
Best Regards -
Ron
PS - The customer should be advised to upgrade to SAP NetWeaver 2004s instead, as you have a fully working 3.5 system "under the covers" but have huge potential for use of many, many more advanced and next generation features. In other words, you can run 2004s BI like it's a 3.5 system, and can "phase in" the use of new features in 2004s when you are ready without another upgrade!
Best Regards -
Ron Silberstein
SAP

ECC 6.0 EHP4 upgrade to EHP5 fails in MAIN_NEWBAS/XPRAS_AIMMRG

from SAPehpi.log
CURRENTPHASE MAIN_NEWBAS/XPRAS_AIMMRG
...started at 20110825140601
...begin processing at 20110825140601
..times self: 0.080000/0.150000 usr/sys, children 0.560000/0.450000 usr/sys.
..finished at 20110825140820 with status UNRESOLVED REQUESTS IN BUFFER.
Error message set: 'Unresolved requests in buffer UT1
Check logfiles 'XPRASUPG.ELG' and '/usr/sap/putUT1/EHPI/abap/log/SAPehpi.ECO''
...begin dialogue at 20110825140821
from SAPehpi.ECO
EXECUTING /usr/sap/UT1/SYS/exe/run/tp (/usr/sap/UT1/SYS/exe/run/tp) pf=/usr/sap/putUT1/EHPI/abap/bin/XPRASUPG.TPP put
UT1
This is /usr/sap/UT1/SYS/exe/run/tp version 380.03.36 (release 720, unicode enabled)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
Process with ID 4903 terminated with status 12
from XPRASUPG.ELG
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR702XPRA00000005.UT1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14071100")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""14071100""UT1"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
<end of logs>
I have searched for ST22 logs and i got a syntax error on program CL_PROXY_STYLESHEET_RUNTIME.
Upgrade 702 has added a segment in the DELETE_CLASS of the program above:
delete from sproxxsl
 where class = class and method = <sproxxsl>-method and client = <sproxxsl>-client.
before:
delete from sproxxsl
 where class = class and method.
"client" field is not part of table SPROXXSL. Which is causing the error.
Any idea on how to continue???
The choices now are:
01) * Repeat phase MAIN_NEWBAS/XPRAS_AIMMRG to continue at the point it stopped
02) - Initialize phase MAIN_NEWBAS/XPRAS_AIMMRG to restart it from the beginning
03) - Accept non-severe errors and repeat phase MAIN_NEWBAS/XPRAS_AIMMRG
04) - Exit this program
Edited by: Rainier Sison on Aug 29, 2011 2:21 PM
Edited by: Rainier Sison on Aug 29, 2011 2:22 PM
Edited by: Rainier Sison on Aug 29, 2011 2:23 PM

Well, I did have a similar issue with RDDEXECL during the import of SAPKB71007.
The solution at that time was updating the kernel to the latest support level, that was released a few weeks after the error with a special modification to fix 'our' issue.
Do you think it's possible to change the kernel on the shadow instance at this moment of EHPI execution?
Hope this helps
Best Regards
Francisco
Edit: The OSS note was: 1551400 - ABAP: Session abort when compiling a deep constant
Edited by: Francisco José Martínez Carretero on Aug 29, 2011 4:54 PM

1AETR012XProgram terminated (job: "RDDEXECL", no.: "11463401") at XPRAS_UPG

Similar Messages

Maybe you are looking for