SAP ABAP Quiz - 1

The AT LINE-SELECTION event is triggered when a user double-clicks a line or presses F2 on a basic list, which is the standard way to trigger the display of a secondary list.

In ABAP/programming event reporting, standard events include initialization, line-selection, end-of-page, and load of program. 'Exit' is not typically categorized as an event keyword in reports - it's a program termination statement. The other three (A, B, D) are standard event keywords triggered during report execution.

To answer the question, let's first understand the concept of client-independent tables. In SAP systems, client-independent tables are those that store data that is shared across all clients in the system, rather than being specific to a single client. These tables typically contain configuration data or other system-wide information.

Now, let's go through each option:

A. Yes: This option is incorrect. Client-independent tables do not have a MANDT field because they store data that is shared across all clients, so there is no need for a field to distinguish the client.

B. No: This option is correct. Client-independent tables do not have a MANDT field because they are not associated with a specific client.

C. Both: This option is incorrect. Client-independent tables do not have a MANDT field, so they cannot have both a MANDT field and be client-independent.

D. None of the above: This option is incorrect. Option B, "No," is the correct answer because client-independent tables do not have a MANDT field.

So, the correct answer is: B. No.

In ABAP, you can create one basic list and up to 20 secondary lists (levels 1 to 20) to provide detailed information when a user interacts with the basic list.

To answer this question, the user needs to have basic knowledge of ABAP programming language and its event-driven programming model.

The correct answer is B. Start-of-selection is the default event in ABAP. This event is triggered when the program is executed and is responsible for fetching data from the database tables and displaying it on the screen.

Now, let's go through each option to explain why it is right or wrong:

A. Initialization: This is not the default event in ABAP. The initialization event is used for initializing variables and internal tables before the start-of-selection event is triggered.

B. Start-of-selection: This is the correct answer. This event is triggered by default when the program is executed.

C. At Selection-screen: This event is triggered when the user interacts with the selection screen of the ABAP program. It is not the default event.

D. Top-of-page: This event is responsible for displaying headers and footers on each page of the ABAP program. It is not the default event.

Therefore, the correct answer is:

The Answer is: B. Start-of-selection

SAP ABAP defines three Standard Internal Table types: Standard Table (default, unsorted), Sorted Table (automatically sorted by key), and Hashed Table (accessed by hash algorithm). 'Index Table' is not a separate table type - it's a category that includes Standard and Sorted tables which can be accessed by index. The question asks what is NOT a type.

BDC (Batch Data Communication) in SAP supports three techniques: Call Transaction (direct, synchronous processing), Session Method (creates sessions to be processed later), and Direct Input Method (for bulk data transfer via special interface). Since all three are valid techniques, 'All of the Above' is the correct answer.

BDC function modules are: BDC_OPEN_GROUP (opens a batch input session), BDC_INSERT (adds transactions to the session), and BDC_CLOSE_GROUP (closes the session; the answer has a typo 'CLOSED' but this is the intended module). BDC_DELETE_GROUP is not a standard BDC function module.

In the ABAP Data Dictionary, the core objects are Tables (store data), Domains (define field technical properties like type and length), and Structures (define complex types without storage). Function Modules are code objects stored in the Function Builder, not dictionary objects used for data definitions.

Transparent tables can be buffered (single or full record), Pooled tables use table buffers, and Internal tables are in-memory structures. Cluster tables cannot be buffered - they store complex data structures across multiple rows and are always read directly from the database. Buffering would be ineffective due to their clustered nature.