Ansicht
Dokumentation

MDG_CONFIG_DRILLDOWN - Define Drill-Down Search Configuration

Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

MDG Drill-Down Search enables you to explore search result data in a flexible manner. It also enables you to define and drill down into hierarchical data. In this Customizing activity, you define the attributes to be a part of the drill-down search for MDG on HANA.

This application searches data from the HANA system. The data is transferred between this application and the HANA database using the SAP Gateway system.

You must have the software component MDG_APPL installed for this activity to function. The drill-down search explores the data from an attribute view in the HANA system. An attribute view with the required information is therefore required for this customizing activity.

Post Activity

A gateway model must be defined and generated as a next step to enable the interaction between the drill down search application and the HANA system.

This customizing activity enables you to define the structure for the drill-down search. It is a two-step activity:

1. Define HANA View Name

Define the header and associate the HANA attribute view on which the search needs to be performed.

The Technical Name is the name for which the search is performed, for example, Customer or Material.

The HANA View Name is the HANA attribute view name, for example, tmp.mdg.customer/AT_CUSTOMER_DATA.

2. Define Attributes for Drill-Down Search

For the selected technical name, define the structure of the master data. The field names defined here should be the same names as in the attribute view defined in step 1. The following options exist:

• Drill-down Attribute: An attribute from the attribute view which is to be a part of the drill down search.

• Child Attribute: An attribute from the attribute view which is to be a part of the drill down search but as a part of the hierarchy and not as a direct root attribute. Example: If a hierarchy has to be defined as Country/Region -> Region -> City, Country/Region being the parent, Region the child of Country/Region, and City the child of Region then it should be defined as follows:

Drill-Down Attribute	Child Attribute
Country/Region	Region
Region	City
City

,,

The above table indicates that Country/Region is the parent whose child is Region and Region is also a parent whose child is City whereas City is a child attribute which does not have a child.

• Root Flag: This flag indicates if an attribute is required as a part of the root attribute or not.

• Result Flag: This flag indicates if an attribute is required as a part of result list or not. It is expected that there is at least one attribute defined as a result.

A root attribute can be a result attribute and vice-versa. The following combinations are possible:

Drill-Down Att.	Child Attribute	Root Flag	Result Flag
Country/Region	Region	X	X
Region	City		X
City		X
Name		X

The above table indicates that Country/Region is a parent attribute with Region as its child and Country/Region is defined as a root attribute on which a search can be made. Country/Region is also a part of the result lists.

Region is an attribute defined as a child of Country/Region and parent of City. Also it is not defined as a Root Attribute because Region shall not be searched directly, but only as a part of hierarchy of Country/Region. Region is still defined as a part of the Result.City is defined as a child of Region and is an attribute. City is not defined as a root attribute but only as a result. Name is an independent attribute which is not part of a root (cannot be searched) it only appears as a part of the result list.

You can add calculated attributes to your drill down search. The following data types are supported for the calculated attributes:

• ALPHANUM

• VARCHAR

• CHAR

• DOUBLE

• FLOAT

• INTEGER

• VARBINARY

• REAL

• TINYINT

• SMALLINT

• NVARCHAR

• BIGINT

• BINARY

Customizing for Gateway Service Enablement under SAP NetWeaver > Gateway Service Enablement > Backend OData Channel > Service Development for Backend OData Channel > Maintain Models

Customizing for Gateway Service Enablement under SAP NetWeaver > Gateway Service Enablement > Backend OData Channel > Service Development for Backend OData Channel > Maintain Services

Addresses (Business Address Services)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 6445 Date: 20240523 Time: 192646     sap01-206 ( 95 ms )