Changing and Hiding Functions

Functions can be hidden on an application-specific basis via customizing. For application definition, undesired functions can be added to the Inactive functions table.
However, if functions are to be hidden or changed dynamically, this must be done using the /PCH/CFW_CTRL_FUNCTION BAdI of the /PCH/CFW_APPLICATION enhancement spot. The BAdI has a filter that can be used to define in which applications the extension should be activated.

The PROVIDE method is called after the function has been fully pronounced by the standard code. The method provides various information:

• IV_FUNCTION, the name of the function

• IO_NODE / IT_NODES, the object (or objects) on which the function is to be applied

• IO_REFERENCE_NODE, depending on the function an indirect reference object

The following information can be changed in the method:

• CV_HIDDEN, visibility of the function

• CV_DISABLED, activation of the function

• CV_TEXT, CV_TEXT_MULTI, text for one or more objects

• CV_MIME_OBJECT_ID, Name of the icon

• CT_SUB_ENTRIES, any submenu that also contains the attributes described above.

Hide vs. disable

The ProFramework follows a clear concept regarding hiding and disabling of functions. It is a strength of the framework that the user is only offered the functions that he can execute at any time. Functions that the user can never execute are always hidden. Functions are only deactivated if the user is allowed to execute these functions in principle, but this is not possible at the current time (e.g. because of a lock by another user).