Mapping the Query Operation

Procedure

To map the Query operation and set range tables, proceed as follows:

1. Create your Data Model. For information, see Selecting the Data Source.

2. Select a GetList operation from the data source and choose Create Mapping. The Map Operation screen displays.

   Note

   The Query method in some cases may not be called, GetList, however, most Query methods use this name.

3. Select Query from the drop-down list in the Operation Type field at the top of the screen.

   Mapping routes (or constant values) are proposed and displayed in the Mapping Route (or Constant Value) column.

4. Select or remove the selections to obtain the table parameters you want and choose Set Range Table. The Map Range Table popup displays.

   For more information, see Ranges Table.

5. Choose Add. The Add Mapping Route popup displays the available Properties from the Data Model view.

6. Select a Property and choose the green check mark to continue.

   The Property displays in the Mapping Route section of the Map Range Table popup. The bottom half of the popup shows any Semantic or Constant Value for each parameter of the range table.

7. Define a meaningful, valid semantic for each attribute by selecting the icon at the end of the Semantic field.

8. Select All buttons are also available for both sections of the popup. When you have finished editing the range table, choose the green check mark to continue.

   The popup screen closes and the range table parameters are greyed out when you return to the mapping screen.

9. Choose the green check mark on the mapping screen to save your mapping for the Query operation.

10. Generate the Data Model.

    For more information, see Generating the PS and DS Models.

To delete a mapping route, select it in the top half of the popup and choose Remove.

Limiting the Number of Items Returned in a Query

You can limit the number of items returned in a Query. Some query BAPIs and RFCs allow you to restrict the number of returned items by means of a maxrows importing parameter.

You can either set a constant value to maxrows and by default limit the returned items, or you can rely on the runtime handling of maxrows.

In both cases, if the returned items are controlled from the consumption channel (respectively with the $top parameter in OData), the runtime component tries to pass the value to the BAPI or RFC but only if there is an importing parameter with one of the following names:

• MAXROWS

• MAX_ROWS

• MAX_HITS

• MAX_LINES

• MAX_CNT

You can use $top and $skip query string attributes to page through table results.

$top can be facilitated by mapping against MAXROWS or similar parameters as listed above.

$skip can be used in your custom code implementation such as, a BADI,/iwfnd/badi_ext_bop_rfc.

If you set a constant value and the $top parameter is also defined, the number in the $top parameter takes precedence. There is no default value.