Page tree
Skip to end of metadata
Go to start of metadata


Area of the UI that contains a heading and possibly other pieces of information, such as a link or icons.

header area

The part of the standard portal layout that contains the masthead, tool area, and top-level navigation.

header area

Part of the title area. It contains the header branding (company logo and image), a welcome text, and links for the personalization of pages and the portal. It also contains a quick search box.


Line of text serving as a name that can stand on its own or be contained in a header.

HTML Business for Java

Full set of easy-to-use Web controls based on servlets and JSP pages.

HTMLB allows a design-oriented page layout. It is designed to overcome such typical servlet problems as:

  • Visualization is not separate from business logic
  • Content management consumes a lot of qualified manpower. Skills in HTML, CSS, JavaScript, etc. are essential
  • Development has to deal with different Web clients and versions
  • It is difficult to maintain the corporate identity throughout the entire application
  • The namespace conflicts with form elements

HTMLB control

A UI control created by means of HTMLB (HTMLBusiness for Java), an SAP proprietary usage of HTML. A control is a basic graphical user interface (GUI) building block, such as a button or a drop-down list.

hyperrelational navigation protocol

A proprietary set of tags governing the rules for Drag and Relate navigation.

hyperrelational OLEDB provider

A proprietary wrapper for the standard OLEDB provider, which translates Drag and Relate queries into ANSI SQL queries.

hyperrelational track

Appearing in every form of a Database Unifier project, a single link representing a series of Drag and Relate navigation actions.


A programming function available to the Database Unifier for use in the Query Editor, that can contain input arguments of almost any data type. Hyrel.eval supports any valid VBScript and can call functions created by a unifier project developer for specific implementation requirements.

  • No labels