Explore topic-wise InterviewSolutions in .

The start and the finish of the main PROCESSING LOGIC, which is default for every ABAP/4 application; the statements from START-OF-SELECTION to END-OF-SELECTION are executed automatically, there is no requirement for having END-OF-SELECTION. Every procedural STATEMENT in ABAP APPLICATIONS are DEPENDENT by default on the START-OF-SELECTION.

The start and the finish of the main processing logic, which is default for every ABAP/4 application; the statements from START-OF-SELECTION to END-OF-SELECTION are executed automatically, there is no requirement for having END-OF-SELECTION. Every procedural statement in ABAP applications are dependent by default on the START-OF-SELECTION.

The COMMAND GET CURSOR will be UTILIZED when the hidden information is not enough for tracing the selected line.

The command GET CURSOR will be utilized when the hidden information is not enough for tracing the selected line.

The secondary list is ALSO CALLED the stacked list and it will be shown on the entire screen if we don’t WRITE its COORDINATES of the command window.

The secondary list is also called the stacked list and it will be shown on the entire screen if we don’t write its coordinates of the command window.

There are TWO WAYS to CREATE table

1. Top-down APPROACH
2. Bottom-up approach

There are two ways to create table

COLLECT allows you to create unique or summarized datasets. The system first tries to find a table entry corresponding to the table key. The key values are taken either from the HEADER line of the INTERNAL table itab, or from the explicitly-specified work area.

If the system finds an entry, the NUMERIC FIELDS that are not part of the table key (see ABAP NUMBER types) are added to the sum total of the existing entries. If it does not find an entry, the system creates a new entry instead.

COLLECT allows you to create unique or summarized datasets. The system first tries to find a table entry corresponding to the table key. The key values are taken either from the header line of the internal table itab, or from the explicitly-specified work area.

If the system finds an entry, the numeric fields that are not part of the table key (see ABAP number types) are added to the sum total of the existing entries. If it does not find an entry, the system creates a new entry instead.

'Refresh' is the KEYWORD which CLEARS the CONTENTS of an INTERNAL table BODY.

'Refresh' is the keyword which clears the contents of an internal table body.

STANDARD TABLE: The key is, by DEFAULT, SET to NON-UNIQUE. You may not use the UNIQUE addition.

SORTED TABLE: Unlike standard tables, sorted table have no default setting for the uniqueness ATTRIBUTE. If you do not specify either UNIQUE or NON-UNIQUE, the system defines a generic table TYPE, where uniqueness is irrelevant. You can use generic types to specify the type of generic subroutine parameters.

HASHED TABLE: Hashed tables have no default setting. You must use the UNIQUE addition with hashed tables. You may not use NON-UNIQUE.

STANDARD TABLE: The key is, by default, set to NON-UNIQUE. You may not use the UNIQUE addition.

SORTED TABLE: Unlike standard tables, sorted table have no default setting for the uniqueness attribute. If you do not specify either UNIQUE or NON-UNIQUE, the system defines a generic table type, where uniqueness is irrelevant. You can use generic types to specify the type of generic subroutine parameters.

HASHED TABLE: Hashed tables have no default setting. You must use the UNIQUE addition with hashed tables. You may not use NON-UNIQUE.

• Check table WORKS at table LEVEL and value table works at domain level.
• Check table is nothing but master table that u will create with VALID set of VALUES.
• Value table it PROVIDES the list of values and it will automatically proposed as a check table while creating foreign key relationship.

TEXT elements MAKES PROGRAM easier to maintain program texts in different languages. These are used for maintaining list headers, selection texts in PROGRAMS.

Text elements makes program easier to maintain program texts in different languages. These are used for maintaining list headers, selection texts in programs.

SM31 is a new version of the t-code SM30.

SM30 - Call VIEW MAINTENANCE & views for SAP TABLES.

SM31 - used for maintenance for SAP tables.

SM31 is a new version of the t-code SM30.

SM30 - Call view maintenance & views for SAP tables.

SM31 - used for maintenance for SAP tables.

Report dont need any EVENT to execute the output.It we we put START-of-selection there is no compulsory to use end-of-selection. End-of-selection is used when we want to execute some output even when some exception occurs to SKIP start-of-selection.

There is no MANDATORY event in the report program. however, if we don't explicitly write any event, system implicitly starts with start of selection event.In CASE of database selection, it is a good practice of use end-of-selection event.

Report dont need any event to execute the output.It we we put start-of-selection there is no compulsory to use end-of-selection. End-of-selection is used when we want to execute some output even when some exception occurs to skip start-of-selection.

There is no mandatory event in the report program. however, if we don't explicitly write any event, system implicitly starts with start of selection event.In case of database selection, it is a good practice of use end-of-selection event.

• ot line SIZE .. INCREASE line-count
• line-size means width of line
• line-count means no. of lines per PAGE.

Load of program is the first triggering EVENT in the classical REPORTS, where as ABAPER point of view INITIALIZATION is the first triggering event.

LOAD-OF-PROGRAM which gets triggered INTERNALLY in the SAP system, then the event INITIALIZATION gets trigger.

Load of program is the first triggering event in the classical reports, where as abaper point of view initialization is the first triggering event.

LOAD-OF-PROGRAM which gets triggered internally in the SAP system, then the event INITIALIZATION gets trigger.

Internal table with header LINE is nothing but work area NAME as WELL as internal table name is same, whereas internal table without header line is nothing but work area name as well as internal table name is different.

FOR INTERNAL TABLE WITH HEADER we need not CREATE work area. But not advisable because the user may get confused what is work area and what is internal table SINCE they both will be having same names.

Internal table with header line is nothing but work area name as well as internal table name is same, whereas internal table without header line is nothing but work area name as well as internal table name is different.

FOR INTERNAL TABLE WITH HEADER we need not create work area. But not advisable because the user may get confused what is work area and what is internal table since they both will be having same names.

Data element is the collection of domain with short DESCRIPTION, whereas domain is collection of datatype and length.

Domain contains only technical attributes (data TYPE , SIZE) where as Data Element contains Technical attribute as WELL as Semantic attributes(Field description).

Data element is the collection of domain with short description, whereas domain is collection of datatype and length.

Domain contains only technical attributes (data type , size) where as Data Element contains Technical attribute as well as Semantic attributes(Field description).

At SELECTION-SCREEN is an event, which is used to VALIDATE the selection screen input fields, if you want to validate the particular input FIELD we use at selection-screen on event.

AT SELECTION-SCREEN ON event is used to validate input.

At selection-screen is an event, which is used to validate the selection screen input fields, if you want to validate the particular input field we use at selection-screen on event.

AT SELECTION-SCREEN ON event is used to validate input.

MOVE itab1 to itab2

We can use APPEND for copying data from ONE ITAB to ANOTHER ITAB by keeping in a loop. But it is not EFFICIENT. Instead we can use as follows:

ITAB1[]=ITAB2[].

Move itab1 to itab2

We can use APPEND for copying data from one ITAB to another ITAB by keeping in a loop. But it is not efficient. Instead we can use as follows:

ITAB1[]=ITAB2[].

SAP provides support in the form of NOTES also and this is CALLED OSS. Can check the link Sree provided.

Just for an example if you FACE any error in your system. Then there is error number associated with the error. Then you can search for the OSS not for the error number, and the note will GIVE you possible solution to your problem.

SAP provides support in the form of Notes also and this is called OSS. Can check the link Sree provided.

Just for an example if you face any error in your system. Then there is error number associated with the error. Then you can search for the OSS not for the error number, and the note will give you possible solution to your problem.

YES. USE TOP-OF-PAGE DURING LINE-SELECTION EVENT.

Yes. Use TOP-OF-PAGE DURING LINE-SELECTION event.

SKIP GENERATES a blank LINE, while the NEW-LINE causes the CONTROL to move to NEXT line.

SKIP generates a blank line, while the NEW-LINE causes the control to move to next line.

SKIP PROVIDES EMPTY space between lines, while RESERVE executes a page break on the CURRENT page if the number of lines between current line and the page footer is less than the number SPECIFIED in RESERVE statement.

SKIP provides empty space between lines, while RESERVE executes a page break on the current page if the number of lines between current line and the page footer is less than the number specified in RESERVE statement.

TOP-OF-PAGE event will be triggered when the FIRST ULINE, WRITE or SKIP statement OCCURS in a PROGRAM.

TOP-OF-PAGE event will be triggered when the first ULINE, WRITE or SKIP statement occurs in a program.

ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements.

SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to PASS DATA from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA PARAMETERS (also known as SET/GET parameters).

ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements.

SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters).

You can MODIFY a RECORD USING MODIFY STATEMENT or UPDATE Statement.

You can modify a record using MODIFY statement or UPDATE Statement.

Using SE11, ENTER the table name and CLICK on Change.

Click on Indexes and select fields and create a SECONDARY index. Note: Always TRY to include MANDT as the first FIELD unless you have a reason..

Using SE11, Enter the table name and click on Change.

Click on Indexes and select fields and create a secondary index. Note: Always try to include MANDT as the first field unless you have a reason..

There is an INDEX created by default for the PRIMARY KEY of the table and that is called Primary Index. If you create, any other index that is called Secondary Index for that table. Secondary INDEXES are created to improve the PERFORMANCE of SELECT statements.

There is an Index created by default for the Primary Key of the table and that is called Primary Index. If you create, any other index that is called Secondary Index for that table. Secondary Indexes are created to improve the performance of SELECT statements.

SELECT SINGLE can be USED if you know the FULL key to select a record. If you do not have the full Key to select and you are interested in one single row, you COULD use SELECT UPTO 1 ROWS. If you use a SELECT SINGLE WITHOUT a full key, you would GET a warning message in Extended Program checks.

If you have the full Key use SELECT SINGLE

If you do not have the full Key to select and you are interested in one single row, you could use SELECT UPTO 1 ROWS..

SELECT SINGLE can be used if you know the full key to select a record. If you do not have the full Key to select and you are interested in one single row, you could use SELECT UPTO 1 ROWS. If you use a SELECT SINGLE without a full key, you would get a warning message in Extended Program checks.

If you have the full Key use SELECT SINGLE

If you do not have the full Key to select and you are interested in one single row, you could use SELECT UPTO 1 ROWS..

In Interactive REPORTS, HIDE statement stores the value of that field for that LINE. If the user places the cursor on a line and click on something those values are AUTOMATICALLY populated to that HIDDEN fields.

In Interactive reports, HIDE statement stores the value of that field for that line. If the user places the cursor on a line and click on something those values are automatically populated to that hidden fields.

Using this function module, you can get the FIELD CATALOG for a given Internal table or DD Structure. Once you get the Field catalog, you COULD change the properties of each field.

Using this function module, you can get the Field catalog for a given Internal table or DD Structure. Once you get the Field catalog, you could change the properties of each field.

In the FIELD Catalog table, you set the HOTSPOT PROPERTY of the field to X.

In the Field Catalog table, you set the HOTSPOT property of the field to X.

• Create all the Domains and Data ELEMENTS as needed using Txn SE11.
• START creating the table using Tcode SE11.
• Maintain Delivery Class (A-Application Table, C-Customizing, etc)
• Enter all the fields (MANDT MUST be the first field) and appropriate data elements or Built in Types for each field.
• Make SURE you select the Primary Key for this table.
• Maintain the Technical Settings (Data class, Size, Buffering info)
• Create Secondary indexes as needed
• ACTIVATE the Table

CREATE a VARIANT in the ALV Report with whatever COLUMNS you would like to see and set sort criteria and column widths and save as a default variant.

You COULD get the default variant by CALLING FM REUSE_ALV_VARIANT_DEFAULT_GET

Create a variant in the ALV Report with whatever columns you would like to see and set sort criteria and column widths and save as a default variant.

You could get the default variant by calling FM REUSE_ALV_VARIANT_DEFAULT_GET

CLEAR: It clears any FIELD, structure or Header LINE of INTERNAL table.

REFRESH: DELETES all entries of internal table.

CLEAR: It clears any field, structure or Header line of internal table.

REFRESH: Deletes all entries of internal table.

AT SELECTION-SCREEN OUTPUT is like Process Before Output Event. This WOULD get triggered before screen is DISPLAYED. This can be used to make fields invisible/visible based on selection.

AT SELECTION-SCREEN: This would be triggered if you hit anything (Enter, Drop-Down, Help, EXECUTE) after the selection screen is displayed.

AT SELECTION-SCREEN OUTPUT is like Process Before Output Event. This would get triggered before screen is displayed. This can be used to make fields invisible/visible based on selection.

AT SELECTION-SCREEN: This would be triggered if you hit anything (Enter, Drop-Down, Help, Execute) after the selection screen is displayed.

If you have MANDT as the FIRST field that is Client DEPENDANT table otherwise it is not. Usually most of the TABLES are client dependent. Only few like RFC Connections table (RFCDES), BATCH Jobs (TBTCO and TBTCP) are not client dependant.

If you have MANDT as the first field that is Client Dependant table otherwise it is not. Usually most of the tables are client dependent. Only few like RFC Connections table (RFCDES), Batch Jobs (TBTCO and TBTCP) are not client dependant.

To ALLOW USERS to MAINTAIN table USING SM30 transaction you use Table Maintenance GENERATOR.

To allow users to maintain table using SM30 transaction you use Table Maintenance generator.

Pricing Tables STARTS with A* LIKE A001, A002, A900 like that.

• KONH – CONDITION Header
• KONP – Condition DETAIL

Pricing Tables starts with A* like A001, A002, A900 like that.

• TRANSPARENT table
• CLUSTER Cluster table
• POOL POOLED table

The user can Interact with the report. We can have a drill down into the report data.

We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).

Events associated with Interactive Reports are:

• AT LINE-SELECTION
• AT USER-COMMAND
• AT PF<key&GT;
• TOP-OF-PAGE DURING LINE-SELECTION.

HIDE statement holds the data to be displayed in the secondary list.

sy-lisel : CONTAINS data of the selected line.

sy-lsind : contains the level of report (from 0 to 21)

Interactive Report Events:

AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sub list is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sub list.

AT PFn: For PREDEFINED function keys...

AT USER-COMMAND : It provides user FUNCTIONS keys.

TOP-OF-PAGE DURING LINE-SELECTION : Top of page event for secondary list.

The user can Interact with the report. We can have a drill down into the report data.

We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).

Events associated with Interactive Reports are:

HIDE statement holds the data to be displayed in the secondary list.

sy-lisel : contains data of the selected line.

sy-lsind : contains the level of report (from 0 to 21)

Interactive Report Events:

AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sub list is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sub list.

AT PFn: For predefined function keys...

AT USER-COMMAND : It provides user functions keys.

TOP-OF-PAGE DURING LINE-SELECTION : Top of page event for secondary list.

These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a LOOP.

Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT.

Events In Classical Reports:

INTIALIZATION: This event triggers before selection screen DISPLAY.

AT-SELECTION-SCREEN: This event triggers after PROCESSING USER input still selection screen is in active mode.

START OF SELECTION: Start of selection screen triggers after processing selection screen.

END-OF-SELECTION: It is for Logical Database Reporting.

These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a loop.

Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT.

Events In Classical Reports:

INTIALIZATION: This event triggers before selection screen display.

AT-SELECTION-SCREEN: This event triggers after processing user input still selection screen is in active mode.

START OF SELECTION: Start of selection screen triggers after processing selection screen.

END-OF-SELECTION: It is for Logical Database Reporting.

E_EXIT_CAUSED_BY_CALLER: DELETE list in CALLBACK_USER_COMMAND

ES_EXIT_CAUSED_BY_USER: How the USER left the list Tables

T_OUTTAB: Table with DATA to be displayed ---MANDATORY

E_EXIT_CAUSED_BY_CALLER: Delete list in CALLBACK_USER_COMMAND

ES_EXIT_CAUSED_BY_USER: How the user left the list Tables

T_OUTTAB: Table with data to be displayed ---mandatory

REUSE_ALV_GRID_DISPLAY

REUSE_ALV_GRID_DISPLAY

This internal table has the following fields:

SOPS: Sort sequence.

Fieldname: Internal output table field name.

Tab name : Only relevant for hierarchical-sequential LISTS. Name of the internal output table.

Up: 'X' = sort in ascending order.

Down: 'X' = sort in descending order.

Sub tot : 'X' = subtotal at GROUP value change.

Group: '* ' = NEW page at group value change ,'UL' = UNDERLINE at group value change.

This internal table has the following fields:

Sops: Sort sequence.

Fieldname: Internal output table field name.

Tab name : Only relevant for hierarchical-sequential lists. Name of the internal output table.

Up: 'X' = sort in ascending order.

Down: 'X' = sort in descending order.

Sub tot : 'X' = subtotal at group value change.

Group: '* ' = new page at group value change ,'UL' = underline at group value change.

Display OPTIONS:

• EXCEPTIONS
• TOTALS
• Interaction
• Detail SCREEN
• Display variants (only for hierarchical-sequential lists)
• Color
• Other

Display options:

A LIST of possible events is POPULATED into an event table (I_EVENTS) when this table is passed from the FUNCTION module REUSE_ALV_EVENT_NAMES_GET. The RETURN table from this function module CONTAINS all the possible events.

A list of possible events is populated into an event table (I_EVENTS) when this table is passed from the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.

he user can PROGRAMMATICALLY SET the initial (DEFAULT) variant for list display.

The default variant can be found USING the function MODULE 'REUSE_ALV_VARIANT_DEFAULT_GET'.

he user can programmatically set the initial (default) variant for list display.

The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.

SLIS is the TYPE LIBRARY for ALV grid.

If you'll use the ALV you have to ADD TYPE-POOLS : SLIS. command at the BEGINNING of your code. 

•  SLIS_LAYOUT_ALV,
• SLIS_T_FIELDCAT_ALV
• SLIS_T_LISTHEADER,
• SLIS_T_EVENT,
• SLIS_SELFIELD.

SLIS is the type library for ALV grid.

If you'll use the ALV you have to add TYPE-POOLS : SLIS. command at the beginning of your code. 

• We have the following three ways to build a field catalog.
• AUTOMATICALLY through a DATA Dictionary structure. 
• Manually in ABAP PROGRAM. 
• Semi-automatically by combining the above two PROCEDURES.
• Declare an internal table of type SLIS_T_FIELDCAT_ALV.
• Call function MODULE REUSE_ALV_FIELDCATALOG_MERGE.

• Sorting of RECORDS
• Filtering of records
• Totals and Sub-totals
• Download the report output to Excel/HTML
• Changing the ORDER of the COLUMNS in the report
• Hide the unwanted columns from the report

ALV stands for ABAP List Viewer. ALV gives US a STANDARD List FORMAT and USER interface to all our ABAP reports. ALV is CREATED by a set of standard function modules provided by SAP.

ALV stands for ABAP List Viewer. ALV gives us a standard List format and user interface to all our ABAP reports. ALV is created by a set of standard function modules provided by SAP.