After a system copy we do have dumps about CALL_FUNCTION_NOT_ACTIVE
on the target new Test system
The function module "ENQUEUE_E_BGRFC_CONF_TAB" is called, but
cannot be found in its function group.
Dump / Runtime Error: CALL_FUNCTION_NOT_ACTIVE u2013 Exception: CX_SY_DYN_CALL_ILLEGAL_FUNC
What happened?
The function module "ENQUEUE_E_BGRFC_CONF_TAB" is called, but
cannot be found in its function group. -
Short text
The function module is not active or contains no code.
The name of the function module to be called is "ENQUEUE_E_BGRFC_CONF_TAB".
but "ENQUEUE_E_BGRFC_CONF_TAB" cannot be found in its function group.
Possible reasons:
a) The function module "ENQUEUE_E_BGRFC_CONF_TAB" has not been activated.
Therefore,
it cannot be found at runtime.
b) The Function Library contains an incorrect entry for
"ENQUEUE_E_BGRFC_CONF_TAB".
c) The function module contains no code, even FUNCTION ... ENDFUNCTION
is missing.
An attempt to solve this via transaction SE37 did fail:
The function group /1BCDWBEN/SEN0015 contains inconsistencies.
Function module ENQUEUE_E_BGRFC_CONF_TAB is not activated (and/or not accessible via SE37)
Procedure
Use the Function Builder repair tool to remove the inconsistencies from the function group. You can then change the function module as planned.
To open the repair tool, on the initial screen of the Function Builder, choose Utilities -> Repair func. group.
Remark: on our development system the same seems to be included in different Function Group named /1BCDWBEN/SEN0018
Instead of /1BCDWBEN/SEN0015
Now comparing /1BCDWBEN/SEN0018 on both DEV and new TEST we see that in TEST there is one object missing
Which is DEQUEUE_E_BGRFC_CONF_TAB, while in both systems for the same function group
we do Have DEQUEUE_E_BGRFC_DB_CONS
While /1BCDWBEN/SEN0018 look similar in DEV and new TEST, we can see that /1BCDWBEN/SEN0015 is quite different in DEV and TEST
We suspected that this could be a problem with table TFDIR but that table was active in SE14
and database as well as runtime object for that table seems to be OK
Remark: SGEN did run without issue