TAW12 2-3

(1)

TAW12 - Week 2

1 of 133

_{format Check}

_{Obligatory Field Check} _{Fixed Values}

_{Foreign Key Check} _{Parameter Id Validation}

2 of 133

OK_CODE is a system reserved variable and cannot be accessed directly

Because the OK_CODE gets reset at the beginning of each execution of PAI processing

To prevent accidental setting of the OK_CODE in a different screen

So the OK_CODE is freed up for subscreens

3 of 133

(More than one answer is correct)

To improve user response time

your updates need to run together as a logical unit Immediate updates to the Database are required your program need the updates completed in order

(2)

4 of 133 NUMBER_GET_INFO NUMBER_RANGE_INTERVAL_LIST NUMBER_CHECK . NUMBER_RANGE_EXTERNAL_CHECK NUMBER_GET_NEXT 5 of 133 0 2 Unlimited 1 6 of 133

Update table.. ..

PERFORM.. .. ON COMMIT and WAIT

COMMIT WORK AND WAIT

CALL FUNCTION in Update Task 7 of 133

SAP memory

ABAP/4 memory

(3)

8 of 133 V2 Local V1 Transactional 9 of 133

an update-task function module triggered with COMMIT WORK AND WAIT

an update-task function module triggered with COMMIT WORK

Batch Input Programs

PERFORM.. .. ON COMMIT 10 of 133

After these events are processed the screen is redisplayed but the PBO is not processed

After these events are processed the PAI is processed then the PBO and then the screen is displayed

After these events are processed the PBO module is processed and the screen is redisplayed

None of the answers are correct

11 of 133

Ensure the prefix name of the radio buttons is the same

Encompass them in a Radio Button Group

Define a Group box

Make sure each one has the same Screen Group

(4)

TAW12 - Week 2

12 of 133

10 PROCESS BEFORE OUTPUT. 20 MODULE SET_STATUS_0100. 30 Set Titlebar 'ABC'.

40 CALL SUBSCREEN SUB INCLUDING 'SAPMZABC' '110'. 50 LOOP.

60 MODULE CHECK_LOOP. 70 ENDLOOP.

80 PROCESS AFTER INPUT.

90 MODULE USER_COMMAND_0100.

100 FIELD FLIGHT MODULE CHECK_FLIGHT ON-REQUIRED.

₃₀ ₁₀₀ ₂₀ ₄₀ ₅₀ TAW12 - Week 2 13 of 133

_{ROLLBACK WORK}

_{CALL Transaction}

_{MESSAGE S101}

(5)

14 of 133

To where the transaction was called To the initial screen of the transaction To the previous screen

To the Cancel area

TAW12 - Week 2

15 of 133

_{I type MESSAGE statement} _{A type MESSAGE statement} _{E type MESSAGE statement} _{W type MESSAGE statement} _{S type MESSAGE statement} 16 of 133

LEAVE TO BASIC LIST

LEAVE TO LIST-PROCESSING

CALL REPORT report_name

GENERATE list

17 of 133

An error in one V2 function module cause all other V2 functions to be rolled back

Each V2 function module for a given COMMIT WORK always runs in its own (separate) DB LUW

(6)

V2 errors cause V1 updates to be rolled back They are usually time critical updates

TAW12 - Week 2

18 of 133

_{Set Screen}

_{Use the Next Screen Option on the Screen Attributes}

_{Loop at Screen}

_{Submit Screen}

19 of 133

The function module forms its own Database LUW The remote function will continue to execute even if

the caller is no longer active

All parameters must have a dictionary reference They are executed on another R/3 database server

TAW12 - Week 2

20 of 133

_{The flow logic is contained in Modules}

Dialog Programs do not require a transaction to execute the module pool

(7)

_{Screens are optional in a dialog program.} Transactions are a vehicle to execute dialog

programs

_{update and enqueue techniques are important.}

TAW12 - Week 2

21 of 133

_{contains screen field values} _{contains function codes}

_{determines successful user action}

TAW12 - Week 2

22 of 133

_{Multiple subscreens are possible in a single screen.} You can also specify the subscreens dynamically at

runtime.

_{Can set their own titlebar} _{Can set their own GUI status} _{have their own OK_CODE}

TAW12 - Week 2

23 of 133

(8)

Duplicate numbers will never be encountered in the system

_{perceived improved performance can be achieved} a programmer can choose to ignore buffering on

request

_{The numbering sequence is contiguous}

TAW12 - Week 2 24 of 133 _{Case OK_CODE} _PAI _{Module User_command} _PBO TAW12 - Week 2 25 of 133

_{Leave to transaction} _{Call Transaction} _{Submit.. .. and Return}

_Submit

TAW12 - Week 2

(9)

_{On the same screen} _{On the next screen}

_{After the AT-EXIT Module} _{In the System Log}

TAW12 - Week 2

27 of 133

process after input. 10 module exit at exit-command. module back. 20 field a module check_field_a. 30 field b module check_field_b. 40 chain. field: a, b, c. module check_field_abc. endchain. 50 chain. field: c, d.

module check_field_cd. <== ERROR endchain. _c _{a, b, c} _{c, d} _{b, d} TAW12 - Week 2 28 of 133

(10)

_{CALL report AND RETURN}

_{SUBMIT report}

_{LEAVE TO LIST-PROCESSING}

_{SUBMIT ZPGMA and Return}

_{SUBMIT ZPGMA with selection-set.. ..}

TAW12 - Week 2 29 of 133 _{At Line-Selection} _{Start-of-Selection} _Top-of-Page _{At Selection-Screen} TAW12 - Week 2 30 of 133 ₃ ₂ ₀ ₁ TAW12 - Week 2 31 of 133

(11)

In the PAI when Process on Value-Request dialog event is triggered

In the PBO when Process on Value-Request dialog event is triggered

In the PAI when Process on Help-Request dialog event is tgriggered TAW12 - Week 2 32 of 133 _SNR3 _SNR1 _SNR2 _SNR4 TAW12 - Week 2 33 of 133 _{There is no difference}

Call Screen is used only for external screens. Set screen is only for screens in the same module pool Call screen executes and returns to the point of call.

Set Screen does not

Set screen executes and returns to the point of call. Call Screen does not

(12)

TAW12 - Week 2

34 of 133

_{DYNP_VALUES_UPDATE} _{DYNP_VALUES_READ} _DYNPREAD _{F4IF_FIELD_VALUE_REQUEST} TAW12 - Week 2 35 of 133

_{ENQUEUE_EZMARA} _{DEQUEUE_EZMARA} _{ENQUEUE_EZ_MARA} _{DEQUEUE_EZ_MARA} TAW12 - Week 2 36 of 133

(13)

_P _T _Blank _F _E TAW12 - Week 2 37 of 133

A subordinate output field in a table control inherits the context menu of the table control

_{They are a special GUI Status}

A subordinate input field in a subscreen causes the subscreen to inherit the context menu of the

subordinate field

_{Context Menus are assigned to input fields}

TAW12 - Week 2

38 of 133

PROCESS BEFORE OUTPUT. * MODULE SET_STATUS_0100. PROCESS AFTER INPUT

MODULE USER_COMMAND_0100.

(14)

_MZABCTOP _{USER_COMMAND_0100} _MZABCO01 _MZABCI01 TAW12 - Week 2 39 of 133

A loop .. endloop statement for the table control only in the PAI

A loop .. endloop statement for the table control in both the PBO and the PAI

A loop .. endloop statement for the table control only in the USER_COMMAND module

A loop .. endloop statement for the table control only in the PBO TAW12 - Week 2 40 of 133 _Field _Module _Check _Case

(15)

TAW12 - Week 2

41 of 133

The screen will be displayed with the report that was built, but the gui-status will be the one from the previous screen

The report will be displayed on the screen only after the user presses the enter key

The previous screen (calling screen) will be redisplayed

_{The screen will be displayed, and will be empty}

TAW12 - Week 2

42 of 133

_{Call Subscreen in the PAI and PBO}

_{The Call Subscreen statement is not required} _{Call Subscreen in the PAI only}

_{Call Subscreen in the PBO only}

TAW12 - Week 2

43 of 133

(16)

_{Through a Function Call}

_{Create it as an object in the dictionary}

TAW12 - Week 2

44 of 133

_{A Commit Work is executed}

System passes a Database commit to the database system

_{The application gathers data for update processing} _{The SAP LUW is concluded}

TAW12 - Week 2

45 of 133

_{Using the SET GROUP statement} _{Do you really care}

_{In the Dynpro}

_{In the screen painter}

TAW12 - Week 2

46 of 133

_{Parameter passing is allowed}

(17)

the FORM

_{Commit Work is allowed in the form} _{RollBack Work is allowed in the FORM}

TAW12 - Week 2

47 of 133

Call Function Enqueue_ESMYLOCK Exporting

Field1 = … Field2 = … Field3 = …

_{It is not possible in this case}

_{Field1 = Generic, Field2 = Generic, Field3 = Space} _{Field 1 = ’AA’, FIELD2 = ’111’, Field3 = Initial} _{Field 1 = ’AA’, FIELD2 = ’111’, Field3 = Space}

TAW12 - Week 2 48 of 133 _Batch _Asynchronous _Synchronous _Direct

(18)

TAW12 - Week 2 49 of 133 ₄ ₁ ₃ _Unlimited ₂ TAW12 - Week 2 50 of 133 _{TOP_LINE} _w/selcolumn _{LINE_SEL_MODE} _{Function code} TAW12 - Week 2 51 of 133

_{An RFC Function Call that terminates normally} _{A program that issues a MESSAGE type 'A'.} _{A user cancels the transaction}

(19)

TAW12 - Week 2

52 of 133

_{read data,lock data, update database, release locks} _{lock data, read data, release locks, update database} _{lock data, read data, update database, release locks}

TAW12 - Week 2 53 of 133 _R _D ₁ _M TAW12 - Week 2 54 of 133

_{Until the Next screen change}

_{Until the next Set TitleBar statement} _{Until the next DB Luw}

(20)

TAW12 - Week 2

55 of 133

_{Screen fields followed by table control fields} All fields regardless of table control definition are

transported at the beginning of PBO

Table control fields followed by the remaining screen fields

_{Dictonary Fields followed by Program Fields}

TAW12 - Week 2 56 of 133 _SM13 _CCMS _SM12 _SE80 TAW12 - Week 2 57 of 133 _{_mytext} _!mytext _?mytext TAW12 - Week 2

(21)

58 of 133 _tstc _txncodes _tstct _txn TAW12 - Week 2 59 of 133

_{SAP LUW is concluded} _{User is notified of updates} _{Update requests are processed} _{Database commit is triggered}

TAW12 - Week 2

60 of 133

When Users need the ability to navigate freely between components

When Navigation between components is pre-determined in a fixed manner

When several components of an application need to be displayed on one screen

(22)

TAW12 - Week 2 61 of 133 _{Asynchronous RFC} _{Synchronous RFC} _{Transactional RFC} TAW12 - Week 2 62 of 133 _{03 - Already_Locked} _{08 - General_Failure} _{01 - Foreign_Lock} _{02 - System Failure} TAW12 - Week 2 63 of 133

(23)

Update task functions are logged in the SM12 log tables

_{Requests are not passed directly to the DB}

You can combine update requests from consecutive dialog steps

_{COMMIT concludes the SAP LUW} _{All updates are performed or none at all}

TAW12 - Week 2

64 of 133

_{You must release the locks programatically}

Locks generated in the dialog program are passed on to the update program

_{An update termination error holds the locks} The locks are automatically released when the

updates complete

TAW12 - Week 2

65 of 133

_{In a PBO module}

_{In a PAI Module}

(24)

_{PBO screen event in Flow logic} TAW12 - Week 2 66 of 133 _{Screen Pushbuttons} _{menu functions} _Container _{tool-bar pushbuttons} TAW12 - Week 2 67 of 133

_{End the Transaction}

_{Reset Command}

_{CALL FUNCTION DEQUEUE_ALL}

_{Commit Work}

(25)

TAW12 - Week 2

68 of 133

a)The corresponding check table will be referenced and displayed

b)Process on Value-Request is executed

c)A search help is referenced and displayed d)The corresponding domain values will be displayed _{b, c, a, d} _{a, b, c, d} _{b, d, a, c} _{d, a, c, b} TAW12 - Week 2 69 of 133 _Subscreen _Sy-Table _Screen _{Screen_ITAB}

(26)

TAW12 - Week 2 70 of 133 _Program _{Transaction Text} _{Screen Number} _{Authorization Object} TAW12 - Week 2 71 of 133

_{Before PBO Processing Begins}

After the User has pressed enter and before the PAI modules are processed

_{After PAI Processing is complete}

After the User has pressed enter and before the PBO modules are processed

TAW12 - Week 2

72 of 133

All fields except table control and field statements, Table control fields, Field statement fields

Field statement fields, Table control fields, remaining fields

Dictionary Fields followed by Program Fields Table control fields, Field statement fields, All

(27)

TAW12 - Week 2

73 of 133

_1.

Dialog-task FORM routines logged with PERFORM…. ON COMMIT. 2. High-priority (V1) update-task function modules. 3. Low-priority (V2) update-task function modules.

_{1, 2, 3} _{3, 2, 1} _{2, 3, 1} TAW12 - Week 2 74 of 133

To the next screen defined in the screen attributes of screen 100

There is no return if the statement LEAVE TO LIST-PROCESSING is used

_{To the beginning of the transaction}

If LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN xxx is used, return will go to screen xxx To the next screen defined in the screen attributes of

(28)

TAW12 - Week 2 75 of 133 _CXTAB _TableView _TableControl _Table TAW12 - Week 2 76 of 133

_{All PBO and PAI modules in the Module pool} _{One sequence of a PBO followed by a PAI} _{One sequence of a PAI followed by a PBO} _{All ABAP Modules of a screen}

TAW12 - Week 2

77 of 133

The system will display the documentation of the field to which a screen field refers

The system will display the documentation of the data element to which a screen field refers

The system will display the documentation of the domain to which a screen field refers

(29)

The system will display the technical information of the field to which a screen field refers

TAW12 - Week 2 78 of 133 _{Function Type} _Application _{Processing type} _{Function Group} TAW12 - Week 2 79 of 133

_{The database breaks}

The update task removes them at the end of the SAP LUW

The update task removes them at the beginning of the SAP LUW

_{Commit Work statement is issued}

(30)

80 of 133

_{Update requests do not use the VBLOG table} Cluster tables are used to processing the update

request

_{Update requests use shared memory}

A new dialog work process is used for the update process TAW12 - Week 2 81 of 133 Titles/Headers Parameter Texts Selection Texts Text Symbols TAW12 - Week 2 82 of 133 _{NUMBER_GET_INFO} _{NUMBER_GET_NEXT} _{NUMBER_RANGE_INTERVAL_LIST} _{NUMBER_RANGE_EXTERNAL_CHECK}

(31)

TAW12 - Week 2

83 of 133

_{CALL SUBSCREEN}

_{At User-Command}

_{Message I001.}

_{Exit the Transaction}

_{CALL TRANSACTION}

TAW12 - Week 2

84 of 133

CLEAR MEMORY ID 'MYID'

FREE MEMORY ID 'MYID'

IMPORT ABC TO MEMORY ID 'MYID' EXPORT ABC TO MEMORY ID 'MYID'

85 of 133

(32)

Set the screen painter attribute GET Parameter and fill in the Parameter ID field with CAR Use the GET Parameter in the PBO of the

DYNPRO

Use the SET Parameter in the PBO of the DYNPRO

Use the GET Parameter in the PAI of the DYNPRO

TAW12 - Week 2

86 of 133

_{subroutines called using on commit have no interface} subroutines called using on commit pass parameters

by reference only

subroutines called using on commit pass parameters by value only

subroutines called using on commit use global data only

TAW12 - Week 2

87 of 133

_{Tab Title}

_{Function Keys}

_{Tabstrip Menu Bar}

(33)

_{Subscreen Area} TAW12 - Week 2 88 of 133 _{Module Pool} _{Flow logic} _{Screen attributes} _{Element List} _{Screen layout} TAW12 - Week 2 89 of 133

F1, Technical Info on the screen field Check users default

Check table TPARA

Check the Value statement in the Top Include

TAW12 - Week 2

90 of 133

(34)

OK_CODE Checking is performed in the Screen Flow Logic

The last field of the element list of the screen has the name OK_CODE

_{OK_CODE is Defined in the TOP Include} _{Define a GUI Status}

TAW12 - Week 2 91 of 133 _F2 _F3 _F1 _F4 TAW12 - Week 2 92 of 133

Prevents a single user with read-write access from attaining further locks to the same set of table rows. This is useful when you are using recursive routines to make updates.

Gives a single user read and write access to the specified table rows. No other users may access the rows.

allows multiple users to access the specified table rows, but with read-access only. No write-accesses are allowed at any time.

(35)

TAW12 - Week 2 93 of 133 _Event _{Program Type} _Module _Transaction TAW12 - Week 2 94 of 133

Field MYTAB-RESERVATION Module Validate_Reservation.

The field is ready for input again PBO is reprocessed

The system places the cursor in the error field Screen is Redisplayed

The Message is displayed

TAW12 - Week 2

(36)

Export the screen fields to memory

The mandatory fields must be filled in with "Get Parameter" statement or default values in Transaction ZABC

The mandatory fields must be filled in with "Set Parameter" statement or default values in Transaction ZABC

The first screen in transaction ZABC can indicate that mandatory fields do not need to be filled in if called by another transaction

TAW12 - Week 2

96 of 133

_{SUBMIT TRANSACTION tcod}

_{LEAVE PROGRAM}

_{LEAVE TO TRANSACTION tcod}

_{CALL TRANSACTION tcod}

TAW12 - Week 2

97 of 133

SUBMIT RSPGM101 WITH BOOKING =

T_BOOKING.

SET PARAMETER ID ‘BOK’ FIELD T_BOOKING. SUBMIT RSPGM101.

IMPORT T_BOOKING TO MEMORY ID ‘MYID’. SUBMIT RSPGM101.

EXPORT T_BOOKING TO MEMORY ID ‘MYID’. SUBMIT RSPGM101.

(37)

TAW12 - Week 2 98 of 133 _{TC_FLIGHT-LINES} _SY-DYNNR _SY-STEPL _{TC_FLIGHT-TOTAL_LINES} TAW12 - Week 2 99 of 133

A number range can be character only The range consists only of numerics

A number range can be defined as both internal and external.

A number range is used only for transactional documents

TAW12 - Week 2

100 of 133

_{SUBMIT ABC WITH CARRID = W_CARRID}

_{CALL ABC WITH CARRID = W_CARRID}

_{SUBMIT ABC AND SKIP FIRST SCREEN.}

(38)

TAW12 - Week 2

101 of 133

_{Leave Program}

_{Leave to Screen 0}

_{Set Screen 0}

_{Set Screen 0. Leave Screen}

TAW12 - Week 2

102 of 133

_{LOOP AT BOOKING_TC.ENDLOOP. "In the PBO.} controls: booking_tc type tableview using screen 200.

"IN THE TOP INCLUDE

LOOP AT BOOKING_TAB WITH CONTROL

BOOKING_TC CURSOR BOOKING_TC-CURRENT-LINE. ENDLOOP. "IN THE PAI

controls: booking_tc using screen 200. " IN THE TOP INCLUDE

TAW12 - Week 2

103 of 133

CHAIN.

Field: Flight, Carrid.

Module Validate on Chain-Input ENDCHAIN.

The Module Validate is processed if both FLIGHT and CARRID are other than the initial value

(39)

The Module Validate is processed if at least one of the fields FLIGHT or CARRID are other than the initial value

The Module Validate is processed only if both FLIGHT and CARRID are initial values

_{The Module Validate is never processed}

TAW12 - Week 2

104 of 133

You should declare a corresponding one character variable in your TOP include You should declare a corresponding one

character variable in the Screen Flow

_{Ensure the radio button is selected in the screen} _{Nothing else is required}

TAW12 - Week 2

105 of 133

_{The Column heading}

_{The width of a column ,}

_{The horizontal grid can be set off/on} _{The order of the columns}

(40)

TAW12 - Week 2

106 of 133

_{At the end of the transaction}

Only when the program encounters more code to modify the field attributes

_{At PAI execution}

_{At PBO execution}

TAW12 - Week 2

107 of 133

_{Enables execution of interactive reporting events} Data available in the dialog program must be passed

to the list

_{Enables processing of ok_code functions} _{The CALL SCREEN xxx statement is possible} The invoking module pool still retains control of

execution TAW12 - Week 2 108 of 133 _{Leave to Transaction} _{Leave Screen} _{Call Screen 100} _{Set Screen 100}

(41)

TAW12 - Week 2

109 of 133

_{ABAP memory is local to each external session} _{Each external session has its own ABAP memory} SAP Memory can be accessed by all external

sessions

_{ABAP memory can be accessed by SAP memory} ABAP memory is used to pass data between the

external sessions of an internal session

TAW12 - Week 2

110 of 133

_{Shortcuts for frequently used functions}

Functions that are relevant for the current Screen Group

_{Context Sensitive Pushbuttons} _{A special menu for subscreens}

TAW12 - Week 2

(42)

_{Issue a COMMIT WORK statement}

Issue a ROLLBACK WORK statement in the program

_{End the dialog program}

_{Issue a termination message (type A)}

TAW12 - Week 2 112 of 133 _{Extended memory} _{SAP memory} _{ABAP/4 memory} TAW12 - Week 2 113 of 133 _{Function Modules}

_{Generic Lock Keys}

_{A Dictionary Table}

TAW12 - Week 2

114 of 133

_UPDATE

_{CALL FUNCTION .. .. IN UPDATE TASK}

(43)

_{PERFORM .. .. ON COMMIT}

TAW12 - Week 2

115 of 133

Place a tabstrip object on your screen using Screen Painter

_{Define Pushbuttons on the subscreen area} _{Name your tabstrip object}

Declare a Tabstrip control in your global top include

TAW12 - Week 2

116 of 133

_{Any Primary Key Fields}

Any Primary Key Fields and Any Secondary Key Fields

_{The Primary Key Fields}

_{The Foreign Key Dependancies}

TAW12 - Week 2

(44)

process after input. 10 module exit at exit-command. module back. 20 field a module check_field_a. 30 field b module check_field_b. 40 chain. field: a, b, c. module check_field_abc. endchain. 50 chain. field: c, d.

module check_field_cd. <== ERROR endchain. ₃₀ ₂₀ ₄₀ ₁₀ ₅₀ 118 of 133

_{Dictionary Objects} _{Txn Code} _{Function Modules} _GUI _{User Dialogs} _{ABAP Program}

(45)

119 of 133

_{Assign Function Type = Space} _{Assign Function Code = P} _{Assign Function Code = Space} _{Assign Function Type = P}

TAW12 - Week 2 120 of 133 _{Leave to Transaction} _Exit. _{Leave Program} _{Stop Program} TAW12 - Week 2 121 of 133

_{Number of table control lines}

_{Loop Counter}

_{Number of filled lines}

TAW12 - Week 2

(46)

Do 5 times.

x = sy-tabix.

perform calculate_sales on commit. enddo. COMMIT WORK. _Infinitely ₁ _{Not at all} ₅ TAW12 - Week 2 123 of 133

_{A screen can be called from within a function module} _{Screens should be called from PBO modules}

_{Screens can be called from PAI modules} _{A screen can be called from a report program.}

TAW12 - Week 2

124 of 133

Process After Input

Module Exit at exit-command Field ABC Module Validate_ABC. 10 All fields not defined in FIELD statements

(47)

20 System performs Auto Field Checking 30 Fields in FIELD Statements

_{20, 30, 10} _{10, 20, 30} _{20, 10, 30} TAW12 - Week 2 125 of 133 _Application _Screens _{Top Include} _{Logical Database} TAW12 - Week 2 126 of 133

_{Message A101}

_{ROLLBACK WORK}

_UPDATE

(48)

TAW12 - Week 2

127 of 133

_{Define a change document object}

Mark the change document flag on the domain of the field where logging is required

Call the generated change doc function (i.e. obj_write_document) in an ABAP program Create a function to update tables CDHDR and

CDPOS TAW12 - Week 2 128 of 133 _{cl_context_clas} _{cl_ctmenu} _{cl_menu} _{menu_class} TAW12 - Week 2 129 of 133 _{Tab strip} _ACTIVETAB _{Function Code}

(49)

_{OK_Code} TAW12 - Week 2 130 of 133 _COMMIT _MODIFY _SET _ACTIVATE TAW12 - Week 2 131 of 133

_{After all V1's are complete} _{After each related V1} _{Before V1's are started} _{Parallel to relative V1's}

TAW12 - Week 2

132 of 133

_{Run Time Error}

_{Status 'BASE' is displayed} _{Standard List Status}

(50)

_{Screen 200 is displayed without a status.}

TAW12 - Week 2

133 of 133

Page scrolling using the standard toolbar is automatic and can be controlled by the user Column sizing is adjustable and can be controlled

by the user

The sort option is automatic and can be controlled by the user