The table can have a standard key and user-defined key standard key user-defined key.
What is correct to say about Header lines: (There are two correct answers) Are the old way of defining internal tables and are still valid The header line for an internal table is the same name as the internal table After SAP NetWeaver 7.40 SP02, the internal tables with header line definitions are totally supported in OO ABAP programming An internal table with a header line can have both flat structures or nested structures as a line type.
There are three types of internal tables: Standard Sorted Hasched Binary Tree Object.
What is correct to say about standard tables: (There are four correct answers) Row numbering (index) is maintained internally, and tables can be accessed using the key or an index This type of table cannot have a unique key and can therefore have duplicate entries The response time of a standard table is better if accessed with an index Key access for the standard table is optimized The table indexing is managed internally. When a record is deleted or inserted, the indexing is reorganized You cannot add a new record to a standard table by using the APPEND statement.
What is correct to say about sorted tables: (There are four correct answers) Defined using the SORTED TABLE addition. Table records are stored in sorted order according to the table keys.The table is sorted in ascending order by default You fill a sorted table using the APPEND statement. The table entries are inserted according to the defined sort sequence The index of the sorted internal table is maintained internally Do not support non-unique keys, generate a runtime error during the INSERT statement Can be accessed with the table key or index. Both sorted and standard tables are also called index tables because they can be accessed using an index The system always uses the binary search algorithm for the sorted table when you access it using the table key (or part of
the key from left to right).
What is correct to say about Hashed tables: (There are three correct answers) They have key and indexes, hence they can be accessed using an index or the key A hashed table must have a unique key because it can only be accessed using the key The sequence of the entries is managed by hash algorithm Hashed internal tables are ideal for storing large numbers of entries, where you need to read those entries using the key, because the response time is dependent upon the number of entries, like Sorted Tables Key access with the standard table is a linear search; for the sorted table, key access is a binary search, and for the hashed table, the key access uses the hash algorithm.
What is correct to say about Defining ABAP Internal Tables: (There are four correct answers) You can define internal tables locally or define them in the ABAP Dictionary as table types As of release 7.0 EHP 2, a secondary key can be defined for the internal table with TYPES and DATA, as well as in the ABAP Dictionary.The table key has now become the primary table key; its predefined name is primary_key. The primary_key can be replaced with an alias in the enhanced definition of the primary table key in release 7.0 EHP 2 An internal table can have up to 5 optional secondary table keys with different names Standard tables are automatically assigned a standard key if an explicit primary key is not defined Hash keys and sorted keys can be declared as secondary table keys. A secondary table index is created for each sorted secondary key of an internal table.
As of SAP NetWeaver 7.40 SP02, it is now possible to define an empty table key for a standard table by using the EMPTY KEY statement for TYPES and DATA declaration. What is correct to say about it? (There are three correct answers) Without the EMPTY KEY addition, the empty table key occurs only if the standard key of the standard table does not contain any component suitable to be a key, such as if the row type does not contain any non-numeric elementry components A standard table with an empty primary key cannot have a nonempty secondary key An explicit declaration of an empty table key using EMPTY KEY is independent of row type Sorting a standard table with an empty table key will not have any effect, unless you specify the table key on which you would like to sort the standard table It is also possible to declare a sorted or hashed internal table with an empty key.
Talking about access type, select the correct definition: Index Table Not Specified.
The key category Not specified defines a generic table type. A generic table type does not define all of the attributes of the table type in the ABAP Dictionary; it leaves some of the attributes undefined. True False.
Talking about internal tables, what is correct to say: (There are three correct answers) An ABAP Dictionary structure is included in the type definition by using the INCLUDE statement An internal table line type can be a flat structure, deep structure, or nested structure, but you must define a separate work area to work with the internal table The STANDARD addition is required for the declaration of the standard table For a standard table, if you do not specify a key, the system automatically adopts a default key as the table key. The default key for a standard table consists of all of the non-numeric fields, in the sequence in which they appear in the line type.
What is correct to say about internal table with header line: (There are four correct anwers) You could declare an internal table with a header line using the DATA statement with the addition of OCCURS followed by the declaration of a flat structure Object-oriented programming also support internal tables with header lines You can use the LIKE statement or TYPE statement to define the individual component of the structure The OCCURS addition defines the expected number of lines for an internal table and reserves the memory for the internal table If you do not specify the OCCURS addition, then
the data object definition is STANDARD TABLE You can simply specify OCCURS 0 and let the system manage the memory for an internal table.
What is correct to say about the APPEND statement: (There are three correct answers) You can use APPEND only with the sorted and standard tables Can be used to append either one or several table lines to standard internal tables Appends the line as the last line in the internal table If the addition FROM <idx1> TO <idx2> is specified in the APPEND statement, then only the rows from <idx1> to <idx2> will be transferred from itab1 to itab2.
What is correct to say about the statement INSERT: (There are five correct answers) Is also used to insert lines into an internal table and is generally used to fill sorted and hashed tables INSERT can be used only for Sorted or Hasched tables because they use a KEY access For sorted internal tables, the new line is inserted according to the sort sequence as specified by the table key definition of the internal table Duplicate lines are inserted above the existing line with the same key Duplicated records cannot be inserted for sorted internal tables with both types non-unique and unique key With a hashed internal table, the lines are inserted in the hash management table according to its table key By INSERT LINES the rules of inserting the single table are maintained.
What is correct to say about MOVE-CORRESPONDING: (There are three correct answers) With SAP NetWeaver 7.40 SP05, the operand of the MOVE-CORRESPONDING statement can be an internal table; this has been enabled by the new variant of the MOVE-CORRESPONDING statement that assigns the identically named components of the internal table row by row With the addition of KEEPING TARGET LINES the original content of the table itab2 will be preserved With the addition of EXPANDING NESTED TABLES the components of the row type are resolved at every hierarchy level Can be used only in STANDARD tables It works only with internal tables that have a flat structure and is used to sum or add up the numeric table fields.
What is correct to say about COLLECT: (There are three correct answers) Can also be used to insert lines into an internal table It works only with internal tables that have a flat structure and is used to sum or add up the numeric table fields For a internal table, the COLLECT statement sums the numeric field values if a line with the key values already exists; otherwise, it appends/inserts the line to the end of the internal table The system field sy-index contains the index of the line inserted or modified in the collect statement.
What is correct to say about READ TABLE: (There are three correct answers) Read a table and append the results in an internal table To use the read statement, you have to provide either a key or an index The result of the READ TABLE statement is transferred to the work area or field symbol only if the READ TABLE statement successfully finds a line With the TRANSPORTING NO FIELDS addition, you can select the components or fields that you want to be transferred to the work area If you specify the ASSIGNING <fs> addition, then the table line with the index idx is assigned to the field symbol <fs>.This addition is helpful if you want to modify the selected line, otherwise, you have to use the MODIFY statement to modify the table line.
What is correct to say about READ TABLE: (There are five correct answers) You can read the internal table record based on any field in the table record with the WITH KEY addition You can use only the key felds of the table line to search the table In the first READ statement provides you with only one record even if more than one record matches the search key With the addition BINARY SEARCH, the search is binary instead of sequential, which considerably improves search performance at runtime. For binary search, the standard internal table must be sorted by the search key in ascending order For sorted internal tables, the search is always binary, and the addition BINARY SEARCH has no effect and is not permitted for hashed internal tables In the second Read the search is performed based on the content of the work area wa In the last Read (WITH TABLE KEY) you can specify the full table key or partially.
What is correct to say about LOOP: (There are three correct answers) You can specify the condition to select the lines using the additional WHERE, it reads via index the wanted lines Specifying the FROM idx1 or TO idx2 you can limit number of table lines to be processed As of SAP NetWeaver 7.0 EHP 2, the WHERE condition can be specified dynamically. The processing sequence for the LOOP statement can be controlled using a secondary key. You can also use the WHERE addition with the AT ... condition.
What is correct to say about Modify the internal table: (There are four correct answers) You cannot use the statement modify direct with a field-symbol, a work area is required With the addition TRANSPORTING, only the fields specified after the TRANSPORTING statement are preserved The statement "MODIFY TABLE itab FROM wa" outside a loop, searches for the internal table line whose key components match the key values of the work area and then modifies the selected internal table line With the WHERE addition all the table lines that satisfy the condition will be updated The statement "MODIFY itab FROM wa INDEX idx" find and update the record via Index The statement "MODIFY TABLE itab FROM wa" inside a loop, modifies just the current line based on wa.
What is correct to say about DELETE internal table: (There are two correct answers) You can delete a line with the index, but only inside a loop You can delete multiple lines with FROM idx1 TO idx2 or with the addition WHERE The DELETE ADJACENT deletes multiple lines from an internal table, there is no pre-conditions to use it The TABLE KEY addition delete based on the table key.
What is correct to say about SORT: (There are two correct answers) You can sort only a standard table using the SORT statement The first three statements sort the internal table by its key. By default DESCENDING AS TEXT addition sorts the character type components according to the current text environment setting specified in the user master record. Without the AS TEXT addition, the internal table is sorted according to the encoding specified by the hardware platform As of SAP NetWeaver 7.40 SP2, it is possible to specify the sort key dynamically.Each row of the internal table tab defines a component of the sort key, and the priority of the sort is based on the order of rows in the stab.The table is not sorted if the internal table stab is initial. The internal table stab is declared as table of type ABAP_SORTORDER_TAB.
What is correct to say about Emptying the Internal Table: (There are three correct answers) The FREE statement works like the REFRESH statement, but in addition, it releases the memory area of the internal table. The memory area reserved for the internal table is released You can clear an internal table with a header line with CLEAR itab[] or REFRESH itab. This statement clears also the header line To clear the header line and the body of the internal table CLEAR: itab,itab[] or CLEAR: itab. REFRESH itab. You can use the CLEAR statement to delete or initialize the body lines of the internal table without a header line.
Table expression is a new feature introduced in SAP NetWeaver 7.40 SP02, what is correct to say about it? (There are four correct answers) allows a read to be perform at the operand position The expression could be based on the index read, read using a free key, or read using a table key If the table line is not found, the SY-SUBRC returns with 4. The predefined function LINE_INDEX for internal tables can be used to identify the index of the row in an internal table. The function will not raise an exception if the row is not found; instead, it will return value 0 The predefined function LINE_EXISTS can be used to check for the existence of a table row specified by table expression.
How many kinds of internal tables are supported in the ABAP language? 2 3 1.
Which of the following statements are true? Select all that apply (There are two correct answers) Standard tables can be accessed by indexhttp://www.daypo.net/images/diskette.png Standard tables cannot be accessed by index A sorted table is always accessed by a unique key Hashed tables are always accessed by index Hashed tables are accessed by a unique key.
The OCCURS statement is required to define an internal table with a header line? True False.
You can use the APPEND statement to fill a sorted internal table: True False.
You cannot use the INSERT statement to insert lines into a standard internal table: True False.
You can use a table with a header line for object-oriented programming: True False.
An internal table line type with a deep or nested structure can be defined for internal tables with a header line: True False.
Internal tables cannot have a deep or nested structure in their line type: True False.
The READ statement with the addition BINARY SEARCH for a sorted internal table is better for performance True False.
The READ statement with the BINARY SEARCH addition cannot be used for a sorted internal table True False.
The BINARY SEARCH addition cannot be used with the READ statement for the HASHED table: True False.
Which of the following is a true statement? Select all that apply. (There are two correct answers) A sorted table can have a unique or a non-unique key A standard table should always have a unique key A hashed table should always have a unique table key.
You can empty the body of the internal table itab with a header line using the CLEAR itab statement: True False.
You can modify an internal table by using the UPDATE statement: True False.
Internal tables can also be modified after executing the READ statement with the addition ASSIGNING True False.
You cannot use a SORT statement for a sorted internal table: True False.
An internal table can have primary keys as well as secondary keys: True False.
An internal table can have at most 15 secondary keys. True False.
An internal table is an ABAP program variable: True False.
An internal table can be defined using the DATA statement: True False.
|
