Explore topic-wise InterviewSolutions in .

MARK the Table maintenance allowed FLAG if USERS with the corresponding authorization may change the DATA in the table using the Data Browser (TRANSACTION SE16). If the data in the table should only be maintained with programs or with the table view maintenance transaction (Transaction SM30), you should not set the flag.

Mark the Table maintenance allowed flag if users with the corresponding authorization may change the data in the table using the Data Browser (Transaction SE16). If the data in the table should only be maintained with programs or with the table view maintenance transaction (Transaction SM30), you should not set the flag.

• SE01 - CORRECTION & Transport Organizer
• SE09 - WORKBENCH Organizer
• SE10 - CUSTOMIZING Organizer

By USING two types of FUNCTION MODULES to be called in SAP Script:

1.  HELP_OBJECT_SHOW_FOR_FIELD
2.  HELP_OBJECT_SHOW.

By using two types of function modules to be called in SAP Script:

SELECT-OPTIONS: SPECIFY are DISPLAYED on the SELECTION screen for the user to ENTER values.

Parameters: dname LIKE dept-dname.
Select-options: dname for dept-dname.

SELECT-OPTIONS: specify are displayed on the selection screen for the user to enter values.

Parameters: dname like dept-dname.
Select-options: dname for dept-dname.

YES, we can have more than ONE selection SCREEN.

Selection-screen begin of block honey with frame TITLE text-101.
Select-options : deptno for zrekha_deptt-deptno.
Selection-screen end of block honey.

Selection-screen begin of block honey1 with frame title text-102.
Select-options : dname for zrekha_deptt-dname.
Selection-screen end of block honey1.

Yes, we can have more than one selection screen.

Selection-screen begin of block honey with frame title text-101.
Select-options : deptno for zrekha_deptt-deptno.
Selection-screen end of block honey.

Selection-screen begin of block honey1 with frame title text-102.
Select-options : dname for zrekha_deptt-dname.
Selection-screen end of block honey1.

FREE - You can use FREE to initialize an internal table and release its memory space without first using the REFRESH or CLEAR STATEMENT. Like REFRESH, FREE works on the table body, not on the table work area. After a FREE statement, you can ADDRESS the internal table again. It still occupies the AMOUNT of memory required for its header (currently 256 bytes). When you refill the table, the system has to allocate new memory space to the lines.

Refresh - This always applies to the body of the table. As with the CLEAR statement, the memory USED by the table before you initialized it remains allocated. To release the memory space, use the statement

Free - You can use FREE to initialize an internal table and release its memory space without first using the REFRESH or CLEAR statement. Like REFRESH, FREE works on the table body, not on the table work area. After a FREE statement, you can address the internal table again. It still occupies the amount of memory required for its header (currently 256 bytes). When you refill the table, the system has to allocate new memory space to the lines.

Refresh - This always applies to the body of the table. As with the CLEAR statement, the memory used by the table before you initialized it remains allocated. To release the memory space, use the statement

Select-options specify are displayed on the selection screen for the user to enter values.

DIFFERENT Properties of Select-options:
1) Visible Length
2) Matchcode Object
3) Memory ID
4) Lowercase
5) Obligatory
6) No Display
7) MODIFY ID

Select-options specify are displayed on the selection screen for the user to enter values.

Different Properties of Select-options:
1) Visible Length
2) Matchcode Object
3) Memory ID
4) Lowercase
5) Obligatory
6) No Display
7) Modify ID

GET CURSOR statement transfers the name of the screen element on which the cursor is positioned during a user ACTION into the variable <f>.

GET CURSOR FIELD <f> [OFFSET <off>] [LINE <LIN>] [VALUE <val>] LENGTH <LEN>]. 

GET CURSOR statement transfers the name of the screen element on which the cursor is positioned during a user action into the variable <f>.

GET CURSOR FIELD <f> [OFFSET <off>] [LINE <lin>] [VALUE <val>] LENGTH <len>]. 

AT SELECTION-SCREEN - event is triggered in the PAI of the selection screen once the ABAP runtime ENVIRONMENT has passed all of the input DATA from the selection screen to the ABAP program.

AT SELECTION-SCREEN OUTPUT - This event block allows you to modify the selection screen directly before it is displayed.

AT SELECTION-SCREEN - event is triggered in the PAI of the selection screen once the ABAP runtime environment has passed all of the input data from the selection screen to the ABAP program.

AT SELECTION-SCREEN OUTPUT - This event block allows you to modify the selection screen directly before it is displayed.

ABAP Memory is a memory area in the INTERNAL session (ROLL area) of an ABAP program. Data within this area is RETAINED within a SEQUENCE of program calls, allowing you to pass data between PROGRAMS that call one another. It is also possible to pass data between sessions using SAP Memory.

SAP Memory is a memory area to which all sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session (as with ABAP memory) or to pass data from one session to another.

ABAP Memory is a memory area in the internal session (roll area) of an ABAP program. Data within this area is retained within a sequence of program calls, allowing you to pass data between programs that call one another. It is also possible to pass data between sessions using SAP Memory.

SAP Memory is a memory area to which all sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session (as with ABAP memory) or to pass data from one session to another.

No, there cannot be more than 1 MAIN window in SAP Script because in WRITE_FORM, it ASKS for the PARAMETER Window that will CREATE the problem.

WRITE_FORM

•  Exporting
• ELEMENT
• Window

No, there cannot be more than 1 main window in SAP Script because in WRITE_FORM, it asks for the parameter Window that will create the problem.

WRITE_FORM

READ LINE and READ CURRENT LINE – These statements are used to read data from the LINES of existing list levels. These statements are CLOSELY CONNECTED to the HIDE technique.

READ LINE and READ CURRENT LINE – These statements are used to read data from the lines of existing list levels. These statements are closely connected to the HIDE technique.

1.  SALES Document: Item Data – VBAP
2.  Sales Document: PARTNER – VBPA
3.  Sales Document: Header Data – VBAK
4.  Sales Document Flow – VBFA
5.  Sales Document: DELIVERY Item Data - LIPS
6.  Customer Master – KNA1
7.  Material Data – MARA
8.  Conditions (TRANSACTION Data) - KONV

Sales & Distribution Module

1) Sales Document: Item Data – VBAP
2) Sales Document: Partner – VBPA
3) Sales Document: Header Data – VBAK
4) Sales Document FLOW – VBFA
5) Sales Document: Delivery Item Data - LIPS
6) CUSTOMER Master – KNA1
7) Material Data – MARA
8) Conditions (Transaction Data) - KONV

Sales & Distribution Module

1) Sales Document: Item Data – VBAP
2) Sales Document: Partner – VBPA
3) Sales Document: Header Data – VBAK
4) Sales Document Flow – VBFA
5) Sales Document: Delivery Item Data - LIPS
6) Customer Master – KNA1
7) Material Data – MARA
8) Conditions (Transaction Data) - KONV

There are TWO TYPES of function modules used in F4 HELP:

1.  F4IF_FIELD_VALUE_REQUEST
2.  F4IF_INT_TABLE_VALUE_REQUEST

There are two types of function modules used in F4 help:

Steps for creating the Functions:

FIRST Procedure:
1) /nSE37
2) Goto
3) FUNCTION GROUP (FG)
4) Create Group
5) Name of FG (ZREKHA_FG)
6) Short Text
7) Save
8) Local Object
Second Procedure:
1) Environment
2) Inactive Object
3) Function Group (ZREKHA_FG)
4) Activate
5) Back
Third Procedure:
1) Name of Function Module (ZREKHA_FM)
2) Create
3) Write FG Name (ZREKHA_FG)
4) Short Text
5) Save
Fourth Procedure:
CALL function ‘ZREKHA_FM’.

Steps for creating the Functions:

First Procedure:
1) /nSE37
2) Goto
3) Function Group (FG)
4) Create Group
5) Name of FG (ZREKHA_FG)
6) Short Text
7) Save
8) Local Object
Second Procedure:
1) Environment
2) Inactive Object
3) Function Group (ZREKHA_FG)
4) Activate
5) Back
Third Procedure:
1) Name of Function Module (ZREKHA_FM)
2) Create
3) Write FG Name (ZREKHA_FG)
4) Short Text
5) Save
Fourth Procedure:
Call function ‘ZREKHA_FM’.

WRITE CODE of the FOLLOWING:

1.  Top-of-Page during line-selection
2.  At line-selection

Write code of the following:

Steps for writing BDC
1) /nSE38
2) Declare Tables, Data (for ITAB) and Data (for BDCITAB)
3) Call function ‘Upload’.
4) Write code for the First Screen, Radio Button, Filename, CHANGE Button, Second Screen, Utilities (Create Entries), Third Screen and Save.
5) Call transaction ‘SE11’ using BDCITAB mode ‘A’.
6) Save, Check Errors, Activate and EXECUTE.

Steps for writing BDC
1) /nSE38
2) Declare Tables, Data (for ITAB) and Data (for BDCITAB)
3) Call function ‘Upload’.
4) Write code for the First Screen, Radio Button, Filename, Change Button, Second Screen, Utilities (Create Entries), Third Screen and Save.
5) Call transaction ‘SE11’ using BDCITAB mode ‘A’.
6) Save, Check Errors, Activate and Execute.

Suppressing of entire screens is possible with this COMMAND. This command ALLOWS us to perform screen processing “in the background”. Suppressing screens is useful when we are BRANCHING to list-mode from a TRANSACTION DIALOG step.

Suppressing of entire screens is possible with this command. This command allows us to perform screen processing “in the background”. Suppressing screens is useful when we are branching to list-mode from a transaction dialog step.

No, RECORDS will be DISPLAYED.

No, records will be displayed.

Call Screen: CALLING a single screen is a special case of embedding a screen sequence. If you want to prevent the CALLED screen from covering the current screen completely, you can use the CALL SCREEN statement with the STARTING AT and ENDING AT

• CALL SCREEN 1000.
• CALL SCREEN 1000 STARTING AT 10 10 ENDING AT 20 20.

LEAVE SCREEN: statement ends the current screen and calls the subsequent screen.

• LEAVE SCREEN.
• LEAVE TO SCREEN 2000.

Call Screen: Calling a single screen is a special case of embedding a screen sequence. If you want to prevent the called screen from covering the current screen completely, you can use the CALL SCREEN statement with the STARTING AT and ENDING AT

LEAVE SCREEN: statement ends the current screen and calls the subsequent screen.

RSTXLDMC OR

Steps for making and INSERTING Logo in SAP Script:

First Procedure:
1) Draw the picture
2) Save it
3) /nSE78
4) WRITE NAME & Choose Color
5) CLICK on Import
6) Browse picture
7) Enter
Second Procedure:
1) /nSE71
2) INSERT
3) Graphics
4) Click on stored on document server
5) Execute
6) Choose name of BMAP

RSTXLDMC OR

Steps for making and inserting Logo in SAP Script:

First Procedure:
1) Draw the picture
2) Save it
3) /nSE78
4) Write name & Choose Color
5) Click on Import
6) Browse picture
7) Enter
Second Procedure:
1) /nSE71
2) Insert
3) Graphics
4) Click on stored on document server
5) Execute
6) Choose name of BMAP

• INTERACTIVE SYSTEM FIELDS: SY-LSIND, SY-CPAGE, SY-LILLI, SY-LISEL, SY-LISTI, SY-LSTAT, SY-STACO, SY-STARO.
• LISTS: SY-COLNO, SY-LINCT, SY-LINNO, SY-LINSZ, SY-PAGNO, SY-TVAR0…..SY-TVAR9, SY-WTITL.

eps_get_directory_listing for DIRECTORY.

eps_get_directory_listing for directory.

Two types of LUW are:

1.  DB LUW - A database LUW is the mechanism used by the database to ensure that its data is always consistent. A database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been SUCCESSFULLY executed, the database will be in a consistent state. If an error OCCURS WITHIN a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it had before the transaction started.
2. SAP LUW - A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a series of different WORK processes.

Two types of LUW are:

LOGICAL UNIT of WORK.

Logical Unit of Work.

EXTRACTS are dynamic sequential datasets in which different LINES can have different structures. We can ACCESS the individual records in an extract dataset USING a LOOP.

Extracts are dynamic sequential datasets in which different lines can have different structures. We can access the individual records in an extract dataset using a LOOP.

There are THREE FUNCTIONS USED in SAP SCRIPT:

1.  OPEN_FORM
2.  WRITE_FORM
3.  CLOSE_FORM

There are three functions used in SAP Script:

There are five Standard Layouts in SAP Script:

1.  PAGE
2.  WINDOW
3.  Page Window
4.  Paragraph Format
5.  CHARACTER Format

There are five Standard Layouts in SAP Script:

By USING TWO STATEMENTS:

1.  Top-of-page during line-selection
2.  At line-selection

By using two statements:

There are four TYPES of JOINS:

•  SELF Join
•  INNER Join
•  Outer Join
•  Equi Join

There are four types of Joins:

Answer : START-OF-SELECTION SELECT * FROM DEPTT INTO CORRESPONDING FIELDS OF ITAB WHERE DEPTNO IN DEPTNO. APPEND ITAB. ENDSELECT. LOOP AT ITAB. WRITE : / 10 ITAB-DEPTNO. HIDE : ITAB-DEPTNO. ENDLOOP. END-OF-SELECTION

RDBMS – RELATIONAL DATABASE Management System. It helps to CREATE relationship between two or more table.

RDBMS – Relational Database Management System. It helps to create relationship between two or more table.

There are THREE events of Interactive Reports:

1.  At PF(nn)
2.  At line-selection
3.  At user-command

There are three events of Interactive Reports:

TRANSACTION Method:

1.  It is faster than session method.
2.  While executing, it STARTS from STARTING.

Session Method:

1.  It is slower than transaction method.
2.  While executing, it does not START from starting.

Transaction Method:

Session Method:

There are TWO TYPES of BDC’s:

1.  Transaction METHOD
2.  SESSION Method

There are two types of BDC’s:

In a LOOP STATEMENT.

In a LOOP statement.

It STORES the CLICK VALUE and DISPLAY the related record in the secondary list.

It stores the click value and display the related record in the secondary list.

1.  PBO (Process Before Output) – Before the screen is displayed, the PBO event is processed.
2.  PAI (Process After Input) – When the user INTERACTS with the screen, the PAI event is processed.
3.  POH (Process On Help) - are triggered when the user requests field help (F1). You can program the appropriate coding in the corresponding event blocks. At the end of PROCESSING, the SYSTEM carries on processing the current screen.
4.  POV (Process On VALUE) - are triggered when the user requests POSSIBLE values help (F4). You can program the appropriate coding in the corresponding event blocks. At the end of processing, the system carries on processing the current screen.

Select-options : dname for deptt-dname.

Select-options : dname for deptt-dname.

Primary Key – It can ACCEPTS 0 VALUE and cannot be NULL.

UNIQUE Key – It can be NULL.

Primary Key – It can accepts 0 value and cannot be NULL.

Unique Key – It can be NULL.

SM30.

SM30.

I had worked with the following (30) system fields:
1) SY-DBSYS - Central Database
2) SY-HOST - Server
3) SY-OPSYS - Operating System
4) SY-SAPRL - SAP Release
5) SY-SYSID - System Name
6) SY-LANGU - User Logon Language
7) SY-MANDT - Client
8) SY-UNAME - Logon User Name
9) SY-DATLO - Local DATE
10) SY-DATUM - Server Date
11) SY-TIMLO - Local Time
12) SY-UZEIT - Server Time
13) SY-DYNNR - Screen Number
14) SY-REPID - Current ABAP program
15) SY-TCODE - Transaction Code
16) SY-ULINE - Horizontal Line
17) SY-VLINE - Vertical Line
18) SY-INDEX - Number of current loop Pass
19) SY-TABIX - Current line of internal table
20) SY-DBCNT - Number of table entries processed
21) SY-SUBRC - Return Code
22) SY-UCOMM - Function Code
23) SY-LINCT - Page Length of list
24) SY-LINNO - Current Line
25) SY-PAGNO - Current Page Number
26) SY-LSIND - Index of List
27) SY-MSGID - Message Class
28) SY-MSGNO - Message Number
29) SY-MSGTY - Message Type
30) SY-SPONO - Spool number during printing 

I had worked with the following (30) system fields:
1) SY-DBSYS - Central Database
2) SY-HOST - Server
3) SY-OPSYS - Operating System
4) SY-SAPRL - SAP Release
5) SY-SYSID - System Name
6) SY-LANGU - User Logon Language
7) SY-MANDT - Client
8) SY-UNAME - Logon User Name
9) SY-DATLO - Local Date
10) SY-DATUM - Server Date
11) SY-TIMLO - Local Time
12) SY-UZEIT - Server Time
13) SY-DYNNR - Screen Number
14) SY-REPID - Current ABAP program
15) SY-TCODE - Transaction Code
16) SY-ULINE - Horizontal Line
17) SY-VLINE - Vertical Line
18) SY-INDEX - Number of current loop Pass
19) SY-TABIX - Current line of internal table
20) SY-DBCNT - Number of table entries processed
21) SY-SUBRC - Return Code
22) SY-UCOMM - Function Code
23) SY-LINCT - Page Length of list
24) SY-LINNO - Current Line
25) SY-PAGNO - Current Page Number
26) SY-LSIND - Index of List
27) SY-MSGID - Message Class
28) SY-MSGNO - Message Number
29) SY-MSGTY - Message Type
30) SY-SPONO - Spool number during printing 

Top-of-Page during line-selection.

Top-of-Page during line-selection.

An output LIST which displays just the basic details &AMP; allow USER to interact, so that a NEW list is populated based on user-selection. With interactive list, the user can actively control data retrieval and DISPLAY during the session.

An output list which displays just the basic details & allow user to interact, so that a new list is populated based on user-selection. With interactive list, the user can actively control data retrieval and display during the session.

The Events used in ABAP are:

1. INITIALIZATION
2. AT SELECTION-SCREEN
3. AT SELECTION-SCREEN ON <FIELD>
4. START-OF-SELECTION
5. TOP-OF-PAGE
6. TOP-OF-PAGE DURING LINE SELECTION
7. END-OF-PAGE
8. END-OF-SELECTION
9. AT USER-COMMAND
10. AT LINE-SELECTION
11. AT PF<NN>
12. GET
13. GET LATE.
14. AT User Command

The Events used in ABAP are:

1. INITIALIZATION
2. AT SELECTION-SCREEN
3. AT SELECTION-SCREEN ON <field>
4. START-OF-SELECTION
5. TOP-OF-PAGE
6. TOP-OF-PAGE DURING LINE SELECTION
7. END-OF-PAGE
8. END-OF-SELECTION
9. AT USER-COMMAND
10. AT LINE-SELECTION
11. AT PF<NN>
12. GET
13. GET LATE.
14. AT User Command

There are THREE TYPES:

1.  LINE
2.  KEY
3.  Table

There are three types:

GET - After the logical database has READ an entry from the node table Tag.

GET LATE - After all the nodes of the logical database have been processed that are below &LT;table> in the database hierarchy.

GET - After the logical database has read an entry from the node table Tag.

GET LATE - After all the nodes of the logical database have been processed that are below <table> in the database hierarchy.

There are Two Events:

1. GET - This is the most important event for executable programs that use a logical database. It OCCURS when the logical database has read a line from the node and made it AVAILABLE to the PROGRAM in the work area declared using the statement NODES table Tag. The DEPTH to which the logical database read is determined by the GET statements
2. PUT - The PUT statement directs the program flow according to the STRUCTURE of the logical database.

There are Two Events:

• Logical Databases are special ABAP PROGRAMS that retrieve data and make it available to application programs.
• Use of LDB – is used to read data from database TABLES by linking them to EXECUTABLE ABAP programs