2368372 - Upgrade phase of type XPRA* fails with short dump PERFORM_NOT_FOUND with exception CX_SY_DYN_CALL_ILLEGAL_FORM | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2368372 - Upgrade phase of type XPRA* fails with short dump PERFORM_NOT_FOUND with exception CX_SY_DYN_CALL_ILLEGAL_FORM

Symptom

Upgrade fails in phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE or MAIN_NEWBAS/XPRAS_UPG fails with following error in XPRA*.ELG file:

1AETR012XProgram canceled (job "RDDEXECL", number "<nnnnnn>")
1AEPU320 See job log"RDDEXECL""<nnnnnn>""<SID>"
1 ETP111 exit code           : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

 

Job log overview for job:    RDDEXECL

          Internal session terminated with a runtime error PERFORM_NOT_FOUND (see ST22)
          Job canceled

 

When you check corresponding short dump, you can see following dump:

 

Category               ABAP programming error
Runtime Errors         PERFORM_NOT_FOUND
Except.                CX_SY_DYN_CALL_ILLEGAL_FORM
ABAP Program           SAPLSDTA
Application Component  BC-DWB-DIC-AC
Date and Time         


 Short Text
     Call (PERFORM) to a non-existent external routine.


 What happened?
     There are several possibilities:
     Error in the ABAP application program.

     The current ABAP program "SAPLSDTA" had to be terminated because it found a
     statement that could not be executed.
     Either
     Error in the SAP kernel

     The current ABAP program "SAPLSDTA" had to be terminated because the ABAP
     processor detected a system error.

Error analysis
    An exception has occurred which is explained in more detail below. The
    exception is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM' and was not
     caught in procedure
    "DD_TABL_INNER_ACT" "(FUNCTION)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated this
    exception, the current program was terminated.
    The reason for the exception is:
    Program "SAPLSDTA" is trying to execute an external PERFORM: routine
     "TBFD_CHK_FEATURES_INDEPENDENT" of
    program "RADTBCHK".
    This routine does not exist however.

    Possible reasons for this error occurring might be:

    1.) Program "SAPLSDTA" or "RADTBCHK" is currently being worked on in the
     system. Name
    "TBFD_CHK_FEATURES_INDEPENDENT" of the called routine might be incorrect (the
     name must be written
    in uppercase), or routine "TBFD_CHK_FEATURES_INDEPENDENT" might not have been
     implemented yet in
    program "RADTBCHK".

    2.) If program SAPMSSY1 is involved in the runtime error, one of the
    function modules called via RFC is flagged as not being remote-enabled.
    (SE37  -> Administration -> Activate RFC Flag)

    3.) There is an inconsistency in the system. The versions of programs
    "SAPLSDTA" and "RADTBCHK" do not match.

 

Note: This dump can come up in other phases of the upgrade as well and if the cause is same, resolution mentioned in this KBA can be followed.


Read more...

Environment

  • Upgrade using Software Update Manager (SUM)
  • ABAP or Dual stack system

Keywords

SAPup, XPRA_EXECUTION, SPAM, SAINT, change request, ADJUSTPRP, umodauto.lst , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-DWB-DIC-AC , Activation Prog., Conversion Prog., DB-Utility, MC, SPDD , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.