TM_DYNP_ATTRIB_VALUES

This exit can be used for attribute F4-Help, if the standard dialog for value help does not fit for the customer’s purpose (e.g. complex search help, etc.)

Location for activation

TM Server

Template function Module

/RTC/TM_TMPL_TM_DYNP_ATTRIB

Interface

Import Parameters

Field	TYPE	Description

Field	TYPE	Description
LV_NAME	/RTC/TM_TM_ATT	Attribute Name
LV_VALUE	/RTC/TM_TM_ATTRVALUE	Currently assigned value and if changed during implementation, the new value…

Example

The customer uses an external ticket tool and wants to force developers to assign a valid ticket number before export. If the user calls the F4-Help for the ticket, the valid ticket numbers should be presented based on selection criteria provided by a search help. In order to realize this, it needs an implementation of the BADI_BEFORE_RELEASE exit and TM_DYNP_ATTRIB_VALUES…

Step 1

Copy the function module /RTC/TM_TMPL_TM_DYNP_ATTRIB

to a new function module

Add the following code to the section “Begin of customer implementation”:

  if lv_check ne space.
    if lv_name ne 'GIS_TICKET_ID'.
      raise wrong_parameters.
    endif.
  else.
    if lv_name = 'GIS_TICKET_ID'.

      gv_action = 'CREATE'.
      gv_ticket_id = lv_value.

      if lv_value ne space.
        select single * from /rtc/tm_km_gis_a
          into corresponding fields of /RTC/TM_KM_GIS
          where ticket_id = lv_value.
      else.
        clear /rtc/tm_km_gis.
      endif.

* Individual dialog screen with individual F4-Help
      call screen 100 starting at 10 10
                      ending   at 90 20.

      if sy-ucomm ne 'CANC'.
        lv_value = gv_ticket_id.
      endif.
    endif.
  endif.

REALTECH Connect