Skip to Content
0
Former Member
Feb 29, 2008 at 11:35 AM

Problem with BADI implementation LE_SHP_DELIVERY_PR

225 Views

Hi,

I implemented the BADI LE_SHP_DELIVERY_PR, It worked ok and I was transported OK to the test Integration machine .

But now, one month after, in the Development Machine instead of process the class implemented (ZCL_IM_LE_SHP_DELIVERY_PRO====CP), the class processed is the standar example CL_IM_LE_SHP_DELIVERY_PRO====CP.

And inside this class exemple there is a call function for a nonexistent function (ZZ_DELETE_ITEM_CUSTOMER_DATA) that isn´t called in my implementation.

Nevertheless, this implementation in test integration machine continues to work correctly.

¿Does anybody know what It has happened?

thanks,

Laura

  • The DUMP's log is:

Errores tiempo ejec. CALL_FUNCTION_NOT_FOUND

Excepción CX_SY_DYN_CALL_ILLEGAL_FUNC Pág. 1

ocurrido el 28.02.2008 a 10:17:00

-

-


Function module "ZZ_DELETE_ITEM_CUSTOMER_DATA" not found.

-

-


¿Qué ha sucedido?

-

-


The function module "ZZ_DELETE_ITEM_CUSTOMER_DATA" was called, but cannot be

found in the Function Library.

Error in ABAP application program.

The current ABAP program "ZCL_IM_LE_SHP_DELIVERY_PRO====CP" had to be

terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

-

-


¿Qué puede hacer?

-

-


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.

-

-


Anál.errores

-

-


An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',

was neither

caught nor passed along using a RAISING clause, in the procedure

"IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETION" "(METHOD)"

.

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:

The program "ZCL_IM_LE_SHP_DELIVERY_PRO====CP" contains a CALL FUNCTION

statement. The name

of the function module to be called is "ZZ_DELETE_ITEM_CUSTOMER_DATA".

No function module exists with the name "ZZ_DELETE_ITEM_CUSTOMER_DATA".

All function modules are stored in the Function Library (SE37).

Possible reasons:

a) Wrong name specified. Particular attention should be paid

to upper/lower case and underscores ("_")

b) Transport error

Errores tiempo ejec. CALL_FUNCTION_NOT_FOUND

Excepción CX_SY_DYN_CALL_ILLEGAL_FUNC Pág. 2

ocurrido el 28.02.2008 a 10:17:00

-

-


c) If an enqueue/dequeue module has been used, the lock object

may not have been activated (ABAP Dictionary)

may not have been activated (ABAP Dictionary).

-

-


Notas para corregir errores

-

-


The exception must either be prevented, caught within the procedure

"IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETION"

"(METHOD)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Check the last transports to the R/3 System.

Is the program "ZCL_IM_LE_SHP_DELIVERY_PRO====CP" currently being changed?

If an enqueue/dequeue module is involved, is the activation

of the lock object missing in the ABAP/4 Dictionary?

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:

-

-


"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC

"ZCL_IM_LE_SHP_DELIVERY_PRO====CP" or "ZCL_IM_LE_SHP_DELIVERY_PRO====CM006"

"IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETION"

-

-


Function modules with names similar to "ZZ_DELETE_ITEM_CUSTOMER_DATA":

ZZ_INITIALIZE_CUSTOMER_DATA

ZZ_READ_CUSTOMER_DATA

ZWT_CUSTOMER_UPDATE

ZBAPI_CUSTOMER_CREATEFROMDATA1

ZBAPI_CUSTOMER_CREATEFROMDATA2

ZCT_MF_DELETE_COMENTARIO

Z_DATOS_CLTE_POSVENTA

Z_PKM_GET_START_DATE_AND_TIME

Z_CRC_DATOS_ALTA

Z_SD_SALES_ORDER_STATUS

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.

Errores tiempo ejec. CALL_FUNCTION_NOT_FOUND

Excepción CX_SY_DYN_CALL_ILLEGAL_FUNC Pág. 3

ocurrido el 28.02.2008 a 10:17:00

-

-


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

or which actions and input led to the error.

-

-


Entorno sistema

-

-


SAP Release.............. "620"

Application server....... "tormes"

Network address.......... "10.75.16.25"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00CF214F4C00"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 3

Short dump setting....... "full"

Database server.......... "tormes"

Database type............ "ORACLE"

Database name............ "SIL"

Database owner........... "SAPR3"

Character set............ "es_ES.ISO8859-1"

SAP kernel............... "640"

Created on............... "Mar 22 2007 20:48:46"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "175"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"

Errores tiempo ejec. CALL_FUNCTION_NOT_FOUND

Excepción CX_SY_DYN_CALL_ILLEGAL_FUNC Pág. 4

ocurrido el 28.02.2008 a 10:17:00

-

-


-

-


Usuario, transacción....

-

-


Client.............. 101

User................ "UN19887"

Language key........ "S"

Transaction......... "VL01N "

Program............. "ZCL_IM_LE_SHP_DELIVERY_PRO====CP"

Screen.............. "SAPMV50A 1102"

Screen line......... 218

-

-


Info posición de cancelación

-

-


The termination occurred in the ABAP program "ZCL_IM_LE_SHP_DELIVERY_PRO====CP"

in "IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETION".

The main program was "SAPMV50A ".

The termination occurred in line 5 of the source code of the (Include)

program "ZCL_IM_LE_SHP_DELIVERY_PRO====CM006"

of the source code of program "ZCL_IM_LE_SHP_DELIVERY_PRO====CM006" (when

calling the editor 50).

Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"

occurred in the

procedure "IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETION" "(METHOD)" but was not

handled locally, not declared in the

RAISING clause of the procedure.

The procedure is in the program "ZCL_IM_LE_SHP_DELIVERY_PRO====CP ". Its source

code starts in line 1

of the (Include) program "ZCL_IM_LE_SHP_DELIVERY_PRO====CM006 ".

-

-


Detalle código fuente

-

-


000010 method IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETION .

000020

000030 * Example: Delete item dependend data from the global memory of an own

000040 * function group

-

-


call function 'ZZ_DELETE_ITEM_CUSTOMER_DATA'

000060 exporting

000070 if_vbeln = is_xlips-vbeln

000080 if_posnr = is_xlips-posnr.

000090

000100 endmethod. "IF_EX_LE_SHP_DELIVERY_PROC~ITEM_DELETIO

Errores tiempo ejec. CALL_FUNCTION_NOT_FOUND

Excepción CX_SY_DYN_CALL_ILLEGAL_FUNC Pág. 5

ocurrido el 28.02.2008 a 10:17:00

-

-