Labelling the Button for Activity-Type-Dependent Planning Rules Display

BUTTON_ LSVAR

The SAP tables which contain the set of rules for the activity-type-dependent planning can be displayed during the Allevo planning process via this function.

The button for starting the function from the Allevo planning screen appears only if the activity-type-dependent planning has been made through the constant LSVAR_VARIATOR with regard to the SAP set of rules. This constant can then be used to change the title of the button by a corresponding entry in the column Value from.

If X is entered in column Value to, the button is hidden when the Excel planning screen is opened.

New for Allevo 2.8 and later: Language-specific text

In Allevo 2.8 and later, an additional feature to maintain language specific texts is available; the relevant name scheme is <BUT_xx_LSVAR> with xx standing for the selected language.

EXAMPLE: BUT_EN_LSVAR defines a button label in English.

New for Allevo 3.0.10 and later: Visibility

Alternatively, SAP user names can be entered in the column Value to (separated by comma); in this case the button on the Excel planning screen will only be visible to these.

Customized functions, such as creation of master data, can be integrated in the Allevo-planning screen. For that an appropriate function module has to be available in the customer system. By default this module can be found in the customer namespace and consists of an import and an export parameter in accordance with the following structure:

· Import: /KERN/IPP_S_CUST_BUT_TO_FM
with information about the layout and the current planning object, or the list of all the objects in the multi-page mode respectively

· Export: /KERN/IPP_S_CUST_BUT_FROM_FM
with the message table in the format of BAPIRET2 as well as the return table for Allevo-Commands that are to be called automatically after (successful) realization of a Customer-button (e.g. automatic acquisition of plan data).

If necessary, additional detailed information will be provided by KERN AG.

The name of the function module - if available - has to be entered in the Value to column of the value parameter BUTTON_CUST1. Thereby it will be visible in the Allevo-planning screen. If the name of the function module that is being entered does not exist in the system, an error message will appear when clicking on the Cust1-Button.

The entry in the Value from column defines the label of the button | Cust.Button1 | .

The title of the button | Cust.Button1 | is defined by the entry in the Value from column.

Note:

An additional feature of maintaining language specific texts is available; the relevant name scheme is <BUT_xx_CUST1> with xx standing for the selected language. Example: BUT_EN_CUST1 defines a different text in English. The name of the function module is always defined through the BUTTON_CUST1 value parameter. In the earlier version 2.9 the value parameter BUTTON_CUST1 is only available in conjunction with MultiObject.

Analogous to this, another value parameter BUTTON_CUST2 with the same functionality is available. Thus two customized functions can be defined and called in the planning screen.