We are upgrading our SRM system from SRM 2.0 ( EBP 3.5 ) to SRM 5.0 SR2 on windows 32 bit platform with Oracle database. We have included SRM SPS 13 in the BIND_PATCH phase of the prepare.
The error is coming in XPRA_UPG phase of upgrade. I am attaching the error logs below :
Contents of XPRASUPG.ELG
**************************************************
**************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620XD1.BBS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "13324900")
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""13324900""BBS"
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 <<<
ST22 Dump
Error in the ABAP Application Program
The current ABAP program "CL_IM_BBP_OM_BUPA_UPDATE======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_HR_ALEOX_BADI_NEWMOD=======CP " in include
"CL_HR_ALEOX_CUSTOMIZING=======CU " in
line 48:
"Type "HRALX_BP_EEWA" is unknown"
" "
" "
" "
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_IM_BBP_OM_BUPA_UPDATE======CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Termination occurred in the ABAP program "CL_IM_BBP_OM_BUPA_UPDATE======CP" -
in "OBJECT".
The main program was "BBP_ATTR_XPRA350 ".
In the source code you have the termination point in line 15
of the (Include) program "CL_EXIT_MASTER================CM002".
The program "CL_IM_BBP_OM_BUPA_UPDATE======CP" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 09303700
I havn't found any OSS Note or any similar proble in sdn. Any help or suggestion will be appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.