Additional Button CUST1 for Customized Functions

BUTTON_CUST1

// From Allevo version 2.9.24 (extended in version 3.3)

Customized functions, such as creating master data or subsequent processing of already existing planning data may be included in the Allevo planning view.  For this purpose, a suitable function module is required in the customer system (by default, in the customer naming environment). According to the import and export parameter, it has the following structure.

§ Import: /KERN/IPP_S_CUST_BUT_TO_FM
with information on the layout and the current planning object / list of all objects in the MultiPage mode (from Allevo 3.3 also desktop integration object and header data).
The corresponding layout object informs if the call was performed via Allevo Inplace or the Allevo Business Client (ABC); in the latter case, no PopUp functions may be called (only return of notes via the BAPI return table).

§ Export: /KERN/IPP_S_CUST_BUT_FROM_FM
contains the table for messages of the format BAPIRET2.
The subordinate parameter COMMAND serves as return value for Allevo commands that shall be automatically called after (successful) execution of a customized button (e.g. during automatic adoption of planning data).

§ Export: EV_SHOW_BUTTON
controls the display of the button depending on, for example, the object state or specifically depending on the user.  
This function is only available if the function module is entered in Value to without further Allevo commands.

A sample function module is available under /KERN/IPP_BUT_CUST_TEMPL. It contains the relevant interfaces but has no other function except for the output of a PopUp window. The function module may be used for first tests.

An entry in column Value from defines the label of button |Cust.Button1|. Without any label, the button will not be displayed.

Enter the name of the function module in Value to. The button will then be visible in the Allevo planning view (e.g. the sample module mentioned above). If the entered function module does not exist in the system, an error message will be displayed when clicking on the CUST1 button.

Analogously, there is another constant BUTTON_CUST2 of the same functionality. Two customized functions may therefore be defined and called in the planning view.

Call in the ABC: The availability of the named functions is limited when calling via the ABC; for example, the called function modules may not contain any ABAP dialogs/PopUps (please check restrictions in the Allevo introductory project). Optionally, a customized function may decide itself if the call was performed using the ABC; in that way, execution may be also performed depending on the respective mode (e.g. skip PopUp in the ABC mode).

Examples of application:

Example 1: Update satellite data in one step

Entry “PLANEN,ZDE_FB_TEST,EXIT2“ triggers the automatic execution of the following functions:

§ Allevo function for “Adopt planning data”

§ Execute function module ZDE_FB_TEST

§ Allevo function for “Reread satellite data“

A list of available Allevo commands may be provided by the Kern Support.

It is further possible to define language-dependent texts; the belonging name scheme is <BUT_xx_CUST1> with xx being the desired language.

Example 2: multilingual application

Constant BUT_EN_CUST1 defines the text in English. BUTTON_CUST1 still determines the name of the called function module.

Example 3: Compensation for Allevo line item display

The import parameters /KERN/IPP_S_CUST_BUT_TO_FM are also used to transfer Allevo internal objects for header data and desktop integration (DOI): this allows to react to the processing status in Excel (e.g. to go to a customized evaluation as in line item display). This function is not available when calling via ABC.

Example 4: Call posting via Allevo Actuals and Architect

The function module /KERN/IPP_EMBED_INTERFACE, used as entry for the customer button, is delivered to call the posting functions of Allevo Actual. The required controlling parameters are stored in the constant EMBEDDED_INTERFACE (see also manual “Allevo Actual” for further details).

New from Allevo version 3.0

Availability: the constant is now available in all Allevo planning transactions (before only in MultiObject).

New from Allevo version 3.2.11

Depending on the application case, you may hide the button via the export parameter EV_SHOW_BUTTON.

Info in the layout object for the call via Allevo Inplace or ABC

New from Allevo version 3.3

Store multiple function modules: multiple function modules and Allevo commands may be entered in Value to (separated by comma). The stored functions are then executed in the defined sequence.