Data Segments in the Context (SAP Library

Data Segments in the Context

For performance reasons, you can determine whether only a specific section of data should be kept in the context so that system performance is not affected. For example, you may want to display data from rows 10 to 20 only in a table.

To do this, you create a subnode in the context, which is filled using the supply method. You can find an example in the system in component DEMO_TABLE.

Example of the Supply Method

method S_DATA_NODE .
*
  data:
    flight type sflight,
    parent_data type CL_WD_FLIGHT_MODEL=>T_SFLIGHT_KEY.
*
  parent_element->get_static_attributes( importing static_attributes = parent_data ).

  flight = CL_WD_FLIGHT_MODEL=>get_sflight_by_key( parent_data ).
** bind a single element
  Node->Bind_Structure( New_Item = flight ).
*
endmethod.

Context Paging

Caution

Context paging is deprecated. This involves the following properties and events:

● Table:

○ firstActualRow (FIRST_ACTUAL_ROW) property

○ rowCount (ROW_COUNT) property

○ onScroll (ON_SCROLL) event

● MultiPane:

○ firstActualPane (FIRST_ACTUAL_PANE) property

○ paneCount (PANE_COUNT) property

○ onScroll (ON_SCROLL) event

Context paging is available for MultiPane and Table.

With the property firstActualxx you specify the cell (row) counting from 0 that is to be the first element in the context, and with xxCount you specify the number of cells (rows) that are to be displayed in the UI element.

With the onScroll event you can find out which data is to be displayed.

Note

Note that with context paging not all the data in the context is available. This could cause problems, for instance with selection. For this reason you should only use context paging with very high data volumes.