> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-ewm/configuration-guide/customising-the-screen-layout/detailed-screen-fields-customisation/maintaining-table-types-for-step-loop-table-functionality.md). # Maintaining table types for step-loop table functionality To improve the usability of step-loop tables within PreBilt, table types are used to control how the table is presented within the UI. The table type functionality addresses the challenge of displaying multiple fields within a single row, particularly on mobile devices with limited screen space. The table type displayed in PreBilt can be controlled either through configuration in transaction */TCTM/EWM\_CUST*, which manages table types at the display profile level, or in transaction */TCTM/EWM\_CFG*, where it can be maintained at logical step/field level. This configuration allows for flexible control data presentation based on the specific requirements.

Maintaining table type for Display Profile

Maintaining table type for Logical Transaction Ste

{% hint style="info" %} **Note** Maintaining table type at screen field level will take priority over anything set at display profile level. {% endhint %} ### Step-Loop (SL) table The step-loop table supports Popin functionality, which adjusts the display based on available screen space. If the screen is resized or has limited space, fields will dynamically grow "downwards" into a vertical stack, ensuring no truncation occurs.

In addition to the Step-Loop (SL) table, there are two other table types available for displaying data, each with unique characteristics: ### Full table view This displays all rows at once, removing the need for navigation buttons like "PAGE UP" or "PAGE DOWN." Fields in this view are read-only, so users cannot edit data. {% hint style="info" %} **Example** Table type "TA" (full table) is set for transaction *INSTBI*, step INSTSB. {% endhint %}

### Object list view This displays data in a simplified, vertically growing list format without column headers. Like the full table view, the object list is non-editable, for scenarios where only viewing is required. {% hint style="info" %} **Example** Table type "OL" (object list) is set for transaction *INSTBI*, step INSTSB. {% endhint %}