
In a BSP application, the runtime object (runtime) makes it possible to access runtime-relevant information, for example, current document (method get_document). This also includes the information that must be implemented explicitly for visualization. This can be determined using the service object ddic_utils for the runtime object.
The delivered data can be used directly in the BSP application. In this way the value list can, for example, be visualized from a simple input help from the BSP application side.
Service object ddic_utils provides the following services:
Determine language-dependent texts (from the ABAP Dictionary and the calendar)
Method GET_FIELD_LABEL for assigning the field label.
See also: Field Label
Method GET_QUICKINFO returns a short description for elementary data objects with dictionary reference.
See also: Application Help
Method GET_DAY_COLLECTION returns day names stored in the dictionary.
Method GET_MONTH_COLLECTION returns month names stored in the dictionary.
Determining a Local or Global History ID
Method GET_HISTORY_ID determines a global history ID.
See also: Field History
Method GET_LOCAL_HISTORY_ID determines a local history ID.
See also: Field History
Determining a Value List
Method GET_SIMPLE_HELPVALUES returns a value list from a simple input help.
See also: Value Help
The part of the methods that determines type-specific information from the dictionary has a reference to a data object as an importing parameter. This data object must have a direct or indirect reference to an elementary dictionary type (data element or component of a structure) since the relevant visualization-relevant information (for example, language-dependent texts) is defined by the elementary dictionary type in the dictionary. For example, a reference to a data object with a reference to an elementary component of a dictionary structure ( DATA: var TYPE strucname-compname), or a data object with a direct reference to a data element ( DATA: var TYPE dtelname) can be passed as an active argurment.