Short-Dump on running t.code FB02 or FB03

[Former Member]

Hi,

We are getting a short dump when running T.codes FB02 or FB03. The Dump is as follows:

-

---

Runtime errors CALL_FUNCTION_PARM_MISSING

Exception CX_SY_DYN_CALL_PARAM_MISSING

Occurred on 24.04.2007 at 15:24:22

Incorrect parameter with CALL FUNCTION.

What happened?

When calling a function module, one of the parmaeters was not

specified.

Error in ABAP application program.

The current ABAP program "SAPLBFFM" had to be terminated because one of the

statements could not be executed.

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

What can you do?

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.

Error analysis

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

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

was neither

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

"(FORM)"

.

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:

When calling the function module "ZZ_SAMPLE_PROCESS_00001130", one of the

parameters

needed according to the interface description was not specified.

This parameter was "T_BKPF".

-

---

Can someone help us with this? Is there a support pack to rectify this problem. Thanks!

[Former Member]

This issue has been resolved now. It seems someone made the wrong entry in table TBE31 for this event and that was the reason it was giving these dumps. I removed the entry from the table and now the transaction code is working fine.

Regards,

Angad

[Former Member]

Hello Angad,

Error is caused while calling function module ZZ_SAMPLE_PROCESS_00001130. Have you made manual changes for FB02,FB03 ?In that case check your ABAP developers-

Regards.

Ruchit.

[Former Member]

Hi Angad,

Sorry ZZ_SAMPLE_PROCESS_00001130 is customer exit. Let me check OSS for this.

Regards.

Ruchit.

[Former Member]

Hello Angad,

Please check function module in SE37.ZZ_SAMPLE_PROCESS_00001130 in SE37.

Under tables tabstrip check if there is any entry for T_BKPF?

Is it like:

T_BKPF LIKE BKPF Belegköpfe

Regards.

Ruchit.

[Former Member]

Hi Ruchit,

Thanks for your replies. Yes there is an entry for T_BKPF. Exactly as you said:

T_BKPF LIKE BKPF Belegköpfe

Regards,

Angad

[Former Member]

Hello Angad,

Have you made any changes to FB02,FB03 recently. Any support package imports ?

Regards.

Ruchit.

[Former Member]

Also in SE37 for function module ZZ_SAMPLE_PROCESS_00001130 go to tab strip source code and let me know if anything is commented out there ?

The code will be:

FUNCTION ZZ_SAMPLE_PROCESS_00001130.

*"----

---

""Lokale Schnittstelle:

*" TABLES

*" T_BKPF STRUCTURE BKPF

*" T_BSEG STRUCTURE BSEG

*" T_BSEC STRUCTURE BSEC

*" T_BKPFSUB STRUCTURE BKPF_SUBST

*" T_BSEGSUB STRUCTURE BSEG_SUBST

*"----

---

ENDFUNCTION.

Lokale Schnittstelle may be commented out. That is fine. What about the rest of the the lines? Any changes in the code?

Regards.

Ruchit.

[Former Member]

Nope, haven made any changes. As for the code, its the same:

FUNCTION ZZ_SAMPLE_PROCESS_00001130.

*"----

---

""Lokale Schnittstelle:

*" TABLES

*" T_BKPF STRUCTURE BKPF

*" T_BSEG STRUCTURE BSEG

*" T_BSEC STRUCTURE BSEC

*" T_BKPFSUB STRUCTURE BKPF_SUBST

*" T_BSEGSUB STRUCTURE BSEG_SUBST

*"----

---

Thanks!

Regards,

Angad

[Former Member]

You mean is everything commented out in this function module?This is nothing be customer exit LBFFMSMPL2U94.

Regards.

Ruchit.

[Former Member]

How do I remove/Rectify it?

[Former Member]

Also, I just noticed, even the code you had sent for the FM ZZ_SAMPLE_PROCESS_00001130 had everything commented out. So is it working at your end?

[Former Member]

Hi Angad,

Yes it is working out fine in my case.. Unless this code is uncommented the customer exit wont be activated. I dont know why is this happening. Best thing is get it debugged in your development system by your developers. That should help in most cases. Else raise a OSS call.

Also if possible please paste the code for the error. You will find it with in the dump itself.

Regards.

Ruchit.

[Former Member]

Here is the source code extract:

Source code extract

001540 INTCA = LAND.

001550 CALL FUNCTION 'BF_FUNCTIONS_FIND'

001560 EXPORTING

001570 I_EVENT = EVENT

001580 I_INTCA = INTCA

001590 I_APPLK = APPLK

001600 TABLES

001610 T_FMRFC = FMTAB

001620 EXCEPTIONS

001630 NOTHING_FOUND = 4

001640 OTHERS = 8.

001650 IF SY-SUBRC = 0.

001660 CLEAR FMTAB.

001670 REFRESH FMTAB.

001680 P_ABEZ = 'X'.

001690 ENDIF.

001700 ENDFORM. " ABEZ

001710 *& *

001720 *& Form CALL_ADD_ONS

001730 *& *

001740 * Call additional components ONLY in the case of CUA-texts

001750 * because only in this case the interfaces are all similar

001760 * *

001770 FORM CALL_ADD_ONS USING EVENT.

001780

001790 * Call external function of SAP-application

001800 LOOP AT FMSAPTAB WHERE EVENT = EVENT.

001810 CHECK NOT FMSAPTAB-FUNCT IS INITIAL.

001820

001830 * Open FI Interface with local destination

> CALL FUNCTION FMSAPTAB-FUNCT

001850 EXPORTING

001860 I_SPRAS = SY-LANGU

001870 IMPORTING

001880 E_FTEXT = FTEXTSTAB-FTEXT.

001890 FTEXTSTAB-IDENT = FMSAPTAB-LAND .

001900 FTEXTSTAB-PRDKT = FMSAPTAB-APPLK.

001910 FTEXTSTAB-KIOFU = 'S'.

001920 FTEXTSTAB-LAND = FMSAPTAB-LAND .

001930 FTEXTSTAB-APPLK = FMSAPTAB-APPLK.

001940 CLEAR FTEXTSTAB-LNUMM.

001950 IF NOT FTEXTSTAB-FTEXT IS INITIAL.

001960 APPEND FTEXTSTAB.

001970 ELSE.

001980 CLEAR FTEXTSTAB.

001990 ENDIF.

-

---

Thanks for all your replies Ruchit. I really appreciate it.

[Former Member]

Hi Angad,

I would suggest OSS call.

In the include LBFFMF01 the error is coming while performing sub routine CALL_ADD_ONS.

I could not find out any code issues. Check if the document you are trying to change has correct data. Even this should not be a issue.

Better raise OSS . Sorry!

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu