Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

CALL_FUNCTION_PARM_UNKNOWN when running a Function Module

Former Member
0 Likes
825

I developed a Function Module (SE37) with a number of import parameters. Transported to the TEST system. Works fine, except that we decided that 1 parameter was obsolete.

Back to Development, SE37, change the FM by deleting the obsolete parameter line. Checked and activated, no problem. Transported to TEST again.

When I now test, the FM dumps immediately saying CALL_FUNCTION_PARM_UNKNOWN.

"Es wurde der Funktionsbaustein "Z_AANMAAK" aufgerufen und der Parameter "AFGEKEURD" mitgegeben. Dieser Parameter ist aber dort nicht definiert."

When I check in Development, in the FM, in the list of import parameters, the deleted parameter is not there.

In the TEST system, the deleted parameter IS in the list of import parameters. But when I check the source code, which starts with the list of all parameters and exceptions (in comments), the deleted parameter is NOT showing.

I tried by putting back the deleted parameter and transporting, then deleting again and transporting. That did not help.

I tried by putting back the deleted parameter and renaming it, then transporting. That did not help.

My guess is that there is a bug. The deleted parameter should have been deleted from one of the SAP tables, but it isn't.

Does anyone of you know the solution?

Thanks very much for any help!!

Ger

1 ACCEPTED SOLUTION
Read only

RaymondGiuseppi
Active Contributor
0 Likes
719

You have to transport the whole function group, the symptoms seem to indicate that only the source of the function module was transported. Look into your transport request, is there a function group (R3TR FUGR) or only the sub-object program source (LIMU REPS), this can (and has) generate inconsistencies in the Function Group definition (SAP tables and Program sources)

In SE37 there is an option in one of the menus to correct damaged function groups.

Regards

5 REPLIES 5
Read only

Former Member
0 Likes
719

Hello Ger,

have you checked the import logs of the transport in your Test system? Perhaps an after import method has failed!?

I would try to transport the function module, or better the complete function group again.

Best regards

Stephan

Read only

0 Likes
719

Hi Stephan, the import logs are fine, but transporting the function group is a good plan, I cannot reach these systems now but I will try that later. Thanks. Ger.

Read only

RaymondGiuseppi
Active Contributor
0 Likes
720

You have to transport the whole function group, the symptoms seem to indicate that only the source of the function module was transported. Look into your transport request, is there a function group (R3TR FUGR) or only the sub-object program source (LIMU REPS), this can (and has) generate inconsistencies in the Function Group definition (SAP tables and Program sources)

In SE37 there is an option in one of the menus to correct damaged function groups.

Regards

Read only

0 Likes
719

Hi Raymond, I will try the transport of the function group. And I will look for that option for correction of a damaged function group. Thanks. Ger

Read only

0 Likes
719

Hi Raymond,

I found the repair. It started a repair of the function group. So the transport contained the function group. After transporting to TEST my problem was gone. So thanks again, also for Stephan.

Ger