41⟩ Explain What are Extracts?
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.
“SAP ABAP Interview Questions and Answers will guide you that ABAP is a very high level programming language created by the German software company SAP. It is currently positioned, alongside the more recently introduced Java, so learn more about the SAP ABAP with the help of this SAP ABAP Interview Questions with Answers guide”
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.
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.
Logical Unit of Work
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
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
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.
No, records will be displayed.
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.
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.
Write code of the following:
1) Top-of-Page during line-selection
2) At line-selection
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 Step:
Call function ‘ZREKHA_FM’.
There are two types of function modules used in F4 help:
1) F4IF_FIELD_VALUE_REQUEST
2) F4IF_INT_TABLE_VALUE_REQUEST
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
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
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.
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
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.
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.
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>].