Explore topic-wise InterviewSolutions in .

No, it is not MUST to use LDB. Apart from it, we have other OPTIONS:

•  Table join by Basis Table
•  DIRECT READ of table
•  Data RETRIEVAL by Program

No, it is not must to use LDB. Apart from it, we have other options:

• Functional Areas - By creating functional areas, we can initially select this data. This ensures that the data is presented to the ABAP Query user in a meaningful way to accomplish the task, and that only the data that the user may use is presented.
• User Groups - A user group is a collection of users that work with about the same data and carry out similar tasks. The members of a user group can use all programs (queries) created by any user of the group. Changes to such a program are at once visible to all users. This ensures that all members of a user group use the same evaluation programs.
• ABAP Query - It consists of three components – queries, functional areas and user groups. The functional areas PROVIDE the user with an initial SET of data in accordance with the task to be accomplished. All users must be members of at least one user group. All members of one user group can ACCESS the same data as well as the same program (queries) to create lists.

• ADVANTAGES: No programming knowledge is required.
• Disadvantages: DEPENDING on the COMPLEXITY of the database tables, it MAY not be easy for the USER to select the necessary data correctly.

• AT LINE-SELECTION
• AT USER-COMMAND
• AT PF.

• SAP supplied BDC PROGRAMS
• RM06BBI0 (Purchase Requisitions)
• RMDATIND (MATERIAL MASTER)
• RFBIKR00 (Vendor Masters)
• RFBIDE00 (Customer Master)
• RVINVB00 (Sales ORDER)

• CONVERSION: LEGACY SYSTEM to flat FILE.
• INTERFACE: Flat file to SAP system.

Open SQL has 2 SYSTEM fields with return CODES:

1.  SY-SUBRC
2.  SY-DBCNT

Using FUNCTION modules

Open SQL has 2 system fields with return codes:

Using function modules

The SEQUENTIAL files (ON APPLICATION SERVER) are called datasets. They are used for file HANDLING in SAP.

The sequential files (ON APPLICATION SERVER) are called datasets. They are used for file handling in SAP.

Performance of ABAP programs can be improved by minimizing the AMOUNT of data to be transferred. The data set must be transferred through the network to the applications, so reducing the amount of TIME and also reduces the network traffic.

Some measures that can be taken are:

•  Use views defined in the ABAP/4 DDIC (also has the advantage of better reusability).
•  Use field LIST (SELECT clause) rather than SELECT *.
•  Range tables should be avoided (IN operator)
•  AVOID nested SELECTS.

Performance of ABAP programs can be improved by minimizing the amount of data to be transferred. The data set must be transferred through the network to the applications, so reducing the amount of time and also reduces the network traffic.

Some measures that can be taken are:

1.  It is a standard data TYPE object, which exists only during the RUNTIME of the program. They are used to perform table calculations on subsets of DATABASE tables and for re-organizing the CONTENTS of database tables according to users need.
2.  Using SY-DBCNT.
3. The number of memory ALLOCATIONS the system need to allocate for the next record population.

SY-SUBRC, SY-DBCNT, SY-LILLI, SY-DATUM, SY-UZEIT, SY-UCOMM, SY-TABIX..

SY-SUBRC, SY-DBCNT, SY-LILLI, SY-DATUM, SY-UZEIT, SY-UCOMM, SY-TABIX..

Yes, group of USERS can ACCESS these PROGRAMS with a CLIENT number.

Yes, group of users can access these programs with a client number.

In COMMERCIAL, organizational and TECHNICAL terms, the client is a self-contained unit in the R3 system, with separate SET of Master data and its own set of TABLES. When a CHANGE is made in one client all other clients are affected in the system - this type of objects are called Client independent objects.

In commercial, organizational and technical terms, the client is a self-contained unit in the R3 system, with separate set of Master data and its own set of Tables. When a change is made in one client all other clients are affected in the system - this type of objects are called Client independent objects.

• CTS stands for Correction and Transport System. The CTS provides a range of functions that help you to choose a transport STRATEGY optimally suited to your requirements. We recommend that you follow the transport strategy while you plan and set up your system landscape.
• Correction and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP WORKBENCH and in CUSTOMIZING, and then transport the changes between the SAP Systems and clients in your system landscape. This documentation provides you with an overview of how to manage changes with the CTS and essential information on setting up your system and client landscape and deciding on a transport strategy. Read and follow this documentation when planning your development project. For practical information on working with the Correction and Transport System, SEE Correction and Transport Organizer and Transport Management System.

• Main function of ranges to pass data to the actual selection tables without displaying the selection screen.
• Min, Max values provided in selection screens.
• It is often necessary to directly access individual RECORDS in a data structure. This is done using UNIQUE keys. Number ranges are USED to ASSIGN numbers to individual database records for a commercial object, to complete the key. Such numbers are e.g. order numbers or material master numbers.

It is SIMILAR to table INDEX that gives list of possible VALUES for EITHER primary KEYS or non-primary keys.

It is similar to table index that gives list of possible values for either primary keys or non-primary keys.

When the table is activated, a physical table DEFINITION is created in the database for the table definition STORED in the ABAP DICTIONARY. The table definition is translated from the ABAP dictionary of the particular database.
It is available for any insertion, MODIFICATION and updation of records by any user.

When the table is activated, a physical table definition is created in the database for the table definition stored in the ABAP dictionary. The table definition is translated from the ABAP dictionary of the particular database.
It is available for any insertion, modification and updation of records by any user.

Different types of DATA DICTIONARY objects:

1.  TABLES
2.  Views
3.  Data elements
4.  STRUCTURE
5.  MATCHCODE
6.  Domains
7.  Search Helps
8.  Local Objects

Different types of data dictionary objects:

DD.MM.YYYY. HH:MM:SS.

DD.MM.YYYY. HH:MM:SS.

Exceptions: Our FUNCTION MODULE needs an exception that it can trigger if there are no ENTRIES in table SPFLI that meet the SELECTION criterion. The exception NOT_FOUND serves this function.
COMMUNICATION_FAILURE & SYSTEM_FAILURE

Exceptions: Our function module needs an exception that it can trigger if there are no entries in table SPFLI that meet the selection criterion. The exception NOT_FOUND serves this function.
COMMUNICATION_FAILURE & SYSTEM_FAILURE

1.  Called PROGRAM - SE37 - Creating function group, function module by assigning attributes, importing, exporting, tables, and exceptions.
2.  Calling program - SE38 - In program, CLICK pattern and write function NAME- provide export, IMPORT, tables, exception VALUES.

It’s an Interactive REPORT where in the user can get more RELEVANT DATA by selecting EXPLICITLY.

It’s an Interactive report where in the user can get more relevant data by selecting explicitly.

An Interactive report is a dynamic drill down report that produces the list on USERS choice.
Difference: -

•  The list produced by CLASSICAL report doesn't allow USER to interact with the system where as the list produced by interactive report allows the user to interact with the system.
• Once a classical report, executed user LOOSES control where as Interactive, user has control.
• In classical report, drilling is not possible where as in interactive, drilling is possible.

An Interactive report is a dynamic drill down report that produces the list on users choice.
Difference: -

The events are as FOLLOWS:

1.  Initialization
2.  At selection-screen
3.  Start-of-selection
4.  END-of-selection
5.  Top-of-page
6.  End-of-page
7.  At line-selection
8.  At user-command
9.  At PF
10.  Get
11.  At New
12.  At LAST
13.  AT END
14.  AT FIRST

The events are as follows:

ABAP Editor: Tool in the ABAP Workbench in which you enter the SOURCE code of ABAP PROGRAMS and check their syntax. You can ALSO navigate from the ABAP Editor to the other tools in the ABAP Workbench.

ABAP Editor: Tool in the ABAP Workbench in which you enter the source code of ABAP programs and check their syntax. You can also navigate from the ABAP Editor to the other tools in the ABAP Workbench.

To use a Native SQL statement, you must PRECEDE it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:

EXEC SQL [PERFORMING <form>].
<Native SQL statement>
ENDEXEC.

There is no period after Native SQL statements. Furthermore, USING inverted commas (") or an asterisk (*) at the beginning of a line in a native SQL statement does not introduce a COMMENT as it would in normal ABAP syntax. You need to know whether table and FIELD names are case-sensitive in your chosen database. 

To use a Native SQL statement, you must precede it with the EXEC SQL statement, and follow it with the ENDEXEC statement as follows:

EXEC SQL [PERFORMING <form>].
<Native SQL statement>
ENDEXEC.

There is no period after Native SQL statements. Furthermore, using inverted commas (") or an asterisk (*) at the beginning of a line in a native SQL statement does not introduce a comment as it would in normal ABAP syntax. You need to know whether table and field names are case-sensitive in your chosen database. 

Open SQL – These STATEMENTS are a SUBSET of standard SQL. It consists of DML command (Select, Insert, Update, Delete). It can simplify and SPEED up database access. Buffering is partly stored in the WORKING memory and shared memory. Data in buffer is not always up-to-date.

Native SQL – They are loosely integrated into ABAP. It allows access to all functions containing programming interface. They are not checked and converted. They are sent DIRECTLY to the database system. Programs that use Native SQL are specific to the database system for which they were written. For e.g. to create or change table definition in the ABAP.

Open SQL – These statements are a subset of standard SQL. It consists of DML command (Select, Insert, Update, Delete). It can simplify and speed up database access. Buffering is partly stored in the working memory and shared memory. Data in buffer is not always up-to-date.

Native SQL – They are loosely integrated into ABAP. It allows access to all functions containing programming interface. They are not checked and converted. They are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. For e.g. to create or change table definition in the ABAP.

• Collect: If an ENTRY with the same KEY already EXISTS, the COLLECT statement does not append a new line, but adds the CONTENTS of the numeric fields in the work area to the contents of the numeric fields in the existing entry.
• Append : DUPLICATE entries occurs

In PAI, DEFINE FUNCTION CODE and WRITE code for the same.

In PAI, define function code and write code for the same.

No, Transparent table do exist with the same STRUCTURE both in the DICTIONARY as well as in the database, exactly with the same DATA and FIELDS.

No, Transparent table do exist with the same structure both in the dictionary as well as in the database, exactly with the same data and fields.

STEPS to create a table:

• Step 1: creating DOMAINS (data type, field length, Range).
• Step 2: creating data ELEMENTS (PROPERTIES and type for a table field).
• Step 3: creating TABLES (SE11).

Steps to create a table:

4 Types of Tables:

1.  Transparent tables - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields. Both Open SQL and Native SQL can be used.
2.  Pool tables - Pooled tables in the dictionary has a many-to-ONE relation with the table in database. Table in the database has the different name as in the dictionary. Pooled table are stored in table pool at the database level.
3.  Cluster tables - These are logical tables that are arranged as records of transparent tables. One cannot use Native SQL on these tables (only Open SQL). They are not manageable DIRECTLY using database system tools.
4.  Internal tables - Internal table is a temporary table stored in the RAM of the application server. It gets CREATED during the program execution and gets DELETED once the program ends.

4 Types of Tables:

Synchronous.

Synchronous.

Two Problems: -

1.  If the USER forgets to opt for KEEP session then the session will be automatically removed from the session queue (LOG remains). However, if session is PROCESSED we may DELETE it manually.
2.  If session processing fails, data will not be transferred to SAP database table.

Two Problems: -

Pool Table :

1.  Many to One Relationship.
2.  Table in the DICTIONARY has the different NAME, different number of fields, and the fields have the different name as in the R3 Table DEFINITION.
3.  It can hold only POOLED tables.

TRANSPARENT Table :

1.  One to One relationship.
2.  Table in the Dictionary has the same name, same number of fields, and the fields have the same name as in the R3 Table definition.
3.  It can hold Application data.

Pool Table :

Transparent Table :

Go to SM36 and create background JOB by giving job NAME, job class and job STEPS (JOB SCHEDULING).

Go to SM36 and create background job by giving job name, job class and job steps (JOB SCHEDULING).

CALL TRANSACTION METHOD &AMP; Call DIALOG.

Call Transaction Method & Call Dialog.

BATCH INPUT SESSION is an intermediate step between internal table and database table. Data ALONG with the action is stored in session i.e. data for screen fields, to which screen it is passed, program name behind it, and how NEXT screen is processed.

• CREATE session – BDC_OPEN_GROUP
• INSERT batch input – BDC_INSERT
• Close session – BDC_CLOSE_GROUP

BATCH INPUT SESSION is an intermediate step between internal table and database table. Data along with the action is stored in session i.e. data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.

Field Symbols – They are placeholder or symbolic NAMES for the other fields. They do not physically reserve SPACE for a field, but point to its contents. It can point to any data objects.
Field-symbols <fs>

Field Groups – Field groups does not reserve STORAGE space but contains pointers to existing fields.
An EXTRACT dataset consists of a sequence of records. These records may have different structures. All records with the same structure form a record TYPE. You must define each record type of an extract dataset as a field group, using the FIELD-GROUPS statement.
Field-groups <fg>

Field Symbols – They are placeholder or symbolic names for the other fields. They do not physically reserve space for a field, but point to its contents. It can point to any data objects.
Field-symbols <fs>

Field Groups – Field groups does not reserve storage space but contains pointers to existing fields.
An extract dataset consists of a sequence of records. These records may have different structures. All records with the same structure form a record type. You must define each record type of an extract dataset as a field group, using the FIELD-GROUPS statement.
Field-groups <fg>

HEADER, BODY, FOOTER.

HEADER, BODY, FOOTER.

Sum: You can only use this statement within a LOOP. If you use SUM in an AT - ENDAT block, the system calculates totals for the numeric fields of all lines in the current line group and writes them to the corresponding fields in the work area. If you use the SUM statement outside an AT - ENDAT block (single entry processing), the system calculates totals for the numeric fields of all lines of the internal table in each loop pass and writes them to the corresponding fields of the work area. It therefore only makes sense to use the SUM statement in AT...ENDAT blocks. If the table contains a nested table, you cannot use the SUM statement. Neither can you use it if you are using a field SYMBOL instead of a work area in the LOOP statement.

COLLECT : It 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 wa.

Sum: You can only use this statement within a LOOP. If you use SUM in an AT - ENDAT block, the system calculates totals for the numeric fields of all lines in the current line group and writes them to the corresponding fields in the work area. If you use the SUM statement outside an AT - ENDAT block (single entry processing), the system calculates totals for the numeric fields of all lines of the internal table in each loop pass and writes them to the corresponding fields of the work area. It therefore only makes sense to use the SUM statement in AT...ENDAT blocks. If the table contains a nested table, you cannot use the SUM statement. Neither can you use it if you are using a field symbol instead of a work area in the LOOP statement.

COLLECT : It 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 wa.

SYSTEM variables have been predefined by SAP. We can use these variables in formulas or, for example, to pass on CERTAIN PIECES of information to a function module. How the function called by the function module behaves depends on the type of information passed on.

System variables have been predefined by SAP. We can use these variables in formulas or, for example, to pass on certain pieces of information to a function module. How the function called by the function module behaves depends on the type of information passed on.

There are MAXIMUM 6 SESSIONS OPEN in SAPGUI.

There are maximum 6 sessions open in SAPgui.

GO to SE71, give layout SET name, go to UTILITIES select debugger mode on.

Go to SE71, give layout set name, go to utilities select debugger mode on.

PAGE Window: In this window, we define the margins for left, WIDTH, upper and height for the layout of Header, Logo, Main, & FOOTER.

Page Window: In this window, we define the margins for left, width, upper and height for the layout of Header, Logo, Main, & Footer.

• OPEN_FORM – This MODULE OPENS layout set printing. This function must be called up before we can work with other layout set function LIKE WRITE_FORM.
  WRITE_FORM – Output text element in form window. The specified element of the layout set window ENTERED is output. The element must be defined in the layout set.
• CLOSE_FORM – End layout set printing. Form printing started with OPEN_FORM is completed. Possible closing operations on the form last opened are carried out. Form printing must be completed by this function module. If this is not carried out, NOTHING is printed or displayed on the screen.

Reason for Setting LOCK: Suppose a travel agent want to BOOK a flight. The customer wants to fly to a particular city with a certain airline on a certain day. The booking must only be possible if there are still free PLACES on the flight. To AVOID the possibility of overbooking, the database entry CORRESPONDING to the flight must be locked against access from other transactions. This ensures that one user can find out the number of free places, make the booking, and change the number of free places without the data being changed in the meantime by another transaction.

Reason for Setting Lock: Suppose a travel agent want to book a flight. The customer wants to fly to a particular city with a certain airline on a certain day. The booking must only be possible if there are still free places on the flight. To avoid the possibility of overbooking, the database entry corresponding to the flight must be locked against access from other transactions. This ensures that one user can find out the number of free places, make the booking, and change the number of free places without the data being changed in the meantime by another transaction.

TABLES:

1.  Data is permanently stored in tables in the database.
2.  Database tables are GENERATED from them.

Structure:

1.  It CONTAINS data temporarily during program run-time.
2. No Database tables are generated from it.

Tables:

Structure:

• Check Table: The ABAP Dictionary allows you to define relationships between tables using foreign keys. A dependent table is called a foreign key table, and the referenced table is called the check table. Each key field of the check table corresponds to a field in the foreign key table. These fields are called foreign key fields. ONE of the foreign key fields is designated as the check field for checking the validity of values. The key fields of the check table can serve as input help for the check field.
• Value Table: PRIOR to Release 4.0, it was possible to use the value table of a domain to provide input help. This is no longer possible, PRIMARILY because unexpected results could occur if the value table had more than one key field. It was not possible to restrict the other key fields, which meant that the environment of the field was not considered, as is normal with check tables.In cases where this KIND of value help was appropriate, you can reconstruct it by CREATING a search help for the data elements that use the domain in question, and using the value table as the selection method.Check table will be at field level checking.Value table will be at domain level checking ex: scarr table is check table for carrid.

PARAMETERS, Select-options &AMP; Selection-Screen.

Parameters, Select-options & Selection-Screen.