Function module is not active

[Sandra_Rossi]

I cannot run VIEW_KUAGV FM, because it throws the error Function module VIEW_KUAGV is not active

however, I see that the module is active and moreover it is executed by system when creating sales order in VA01 for partner determination.

How that could be? Why it cannot be ran manually?

[Sandra_Rossi]

A function module is part of a function group. Could you check the version management of the function module (utilities > version), do you have the last version inactive? Is there something in the function group that is not activated? Could you check if some people have done some modifications to the function group? (maybe applying a SAP note)

[Astashonok]

sandra.rossi here is the version overview screenshot. The last version is active and released by SAP on 05.10.2011, exactly like in the FM properties

[Sandra_Rossi]

Can you activate the function group V05E? (via SE80 for instance)

[Astashonok]

activated FG, it returned Active version generated, also re-activated the FM and still no changes. Still the same error. Do you observe the same behavior in your system?

[Sandra_Rossi]

Could you "repair" the function group (note 2101855 - Function module cannot be tested after repair of a function group)?

If it doesn't work, see if there are some other SAP notes or eventually contact SAP Support.

[Astashonok]

and the approach described in this note did not work, this is what I see after activation via FUNC_OBJECT_ACTIVATE

the module parameters are missing, so regeneration got corrupted.

[Astashonok]

or maybe test environment is corrupted

[RemiKaimal]

Try setting a break-point at the function module : RS_FUNCTION_ACTIVE_CHECK, and check what you get.
If you look at the attributes of the function module it says it’s “Not released”.

[FredericGirod]

Not active is an attribute of hte code, meaning the last updated code has not been compiled (even if in abap there is no compiler).

Not released is a functional attribute of hte FM, meaning, if you are not SAP developper, you should not use it

[Astashonok]

PRICING module is also marked as Not released, but it is perfectly runnable programmatically as well as from SE37, so it's not the case.