XPRA error.

Question

the error has occured during the upgrade and it goes like this....
LIST OF ERRORS AND RETURN CODES  *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700HEC.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700XD3.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZE5.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WE4.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZEA.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WE3.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WE5.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WE6.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WE2.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZE2.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEOL555 Object type '"BUS20370"' could not be generated
  Long text:
    Cause
      The object type could not be activated.
    What to do
      Select the function 'Check' in the object type and correct the error
      found. Then try to activate the object type again.
2EEOL555 Object type '"BUS20350"' could not be generated
  Long text: see above
2EEOL555 Object type '"BUS20310"' could not be generated
  Long text: see above
2EEOL555 Object type '"BUS20300"' could not be generated
  Long text: see above
2EEOL555 Object type '"BUS20310"' could not be generated
  Long text: see above
2EEOL555 Object type '"BUS20360"' could not be generated
  Long text: see above
2EEPU133 Errors occurred during post-handling "SWO_OBJTYPE_AFTER_IMPORT" for "SOBJ" "L"
  Long text:
    Cause
      During the upgrade, import post-processing &V#& was performed for
      object &V#& &V#&. Errors were reported.
    System Response
      The upgrade is interrupted.
    What to do
      You will find the error messages for post-processing &V#& directly
      before this message. First read these error messages and the respective
      long texts. You will find further information there on correcting the
      errors.
      If this information is not sufficient, look for error notes in the
      SAPNet - R/3 Front End. Keywords you can use for the search are
      the name of post-processing &V#& or
      the message numbers of the preceding error messages. The message number
      appears in the header of the long text display.
      If you enter a problem message for the error, enter the following
      information:
      the name of post-processing &V#&
      the message numbers of the preceding error messages
      the components in which the error occurred
2EEPU136 The errors affect the following components:
  Long text:
    Cause
      During the upgrade or import of a transport request, errors occurred
      which affect particular components of the SAP System.
      The following messages list the components in which the errors
      occurred.
    System Response
      The upgrade or import of the transport request is interrupted.
    What to do
      Read the preceding error messages and their long texts for more
      information on correcting the errors.
2EEPU137    "BC-DWB-TOO-BOB" ("Business Object Builder")
  Long text:
    Cause
      During the upgrade or import of a transport request, errors occurred in
      the component
         &V#& (&V#&).
    System Response
      The upgrade or import of the transport request is interrupted.
    What to do
      Read the preceding error messages and their long texts for more
      information on correcting the errors.
1 ETP111 exit code           : "8"
>>> 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 SAPR700ZE7.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZE8.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZE9.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZE1.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WE1.YBA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "01202800")
  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""01202800""YBA"
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 <<<
please help out if someone else has faced this problem earlier.

Answer 1

I got the same error when upgrading from 4.6c to ECC6
In SM37 I found that job RDDEXECL is cancelled. Job log gives that
The following syntax error occurred in program "SAPLSNR3 " in include "LSN
"The type "BADI_NUMBER_GET_NEXT" is unknown."
This can be solved by activating Enhancement Sport: BADI_NUMBER_GET_NEXT in txn SE18. Info can be found in OSS note 980194.