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

[Former Member]

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.

[Former Member]

Thanks a lot, I'm going to restart the upgrade.

[Former Member]

Jorge,

I am curious to know if adding of the matching SPs solved your problem. Because i am facing similar problem. But on one system sandbox i could complete without adding any SPs matching the target level. However, on our developmement system i am not able to.

Regards

Vivek

[Former Member]

Hello Shaji,

It means that I don't have choice, just stop the upgrade and then start it again??

could you tell me which is Support Package (700) equivalent to

Support Package 63 (620)???

Regards,

Jorge Ramírez Carrasco.

[Former Member]

You can include upto SP'15, which is the latest. Also check the dependencies of each SP's and make sure its copied to the ...\EPS\in directory

[Former Member]

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,

[Former Member]

If your Source SP=63, you need to include the Support Package equivalent to that in the Target version, or else you will end up losing data also.