71. What are IDOCs? 
Ans. Intermediate document (IDoc) container for exchanging data between R/3, R/2 and non-SAP systems. ALE uses IDocs to exchange data between logical systems. Non-SAP systems can use IDocs as the standard interfacefor data transfer.
IDocs are created when message types and (object) methods are distributed. The message type is the format in which the data for a specific business process is transferred.





72. What are screen painter? menu painter? Gui status? ..etc. 
Ans. Screen painter: Tool for creating the screens of a dialog transaction.
Menu painter: Tool for creating and designing the graphical user interface of an ABAP program.
GUI Status : Main element of the graphical user interface.A GUI status usually consists of a menu bar with menus, a standard toolbar, an application toolbar, and functions with function key settings.
Together with the GUI title, the GUI status defines the actual state of the user interface of an ABAP program. 

73. What is screen flow logic? What are the sections in it? Explain PAI and PBO. 
Ans. Flow logic : Code that processes a particular screen in the R/3 System.Flow logic statements are syntactically similar to ABAP statements, but you cannot use flow logic keywords in ABAP. 
You define flow logic in the flow logic editor of the Screen Painter. Flow logic comprises four modules: 
•	PBO (Process Before Output) 
•	PAI (Process After Input) 
•	POV(Process On value request)
•	POH(Process On Help request)
PBO  : The processing of screen before the screen is displayed is done in this event. (event is triggered before the screen is displayed).
PAI  : This event is responsible for processing of screen after the user enters the data and clicks the pushbutton. 
POV : This is triggered when user clicks F4 function key (for listing all possible values for the field).
POH : This event is triggred when user places the cursor on field and press F1 , by default system displays its own HELP for that particular field one can add his own HELP by writting in POH.

74. Overall how do you write transaction programs in SAP? 
Ans.
•	Create a module program.
•	Goto Screen painter in SE51. create & add all your elements.
•	write flow logic in screen painter 
•	save & activate.
•	attach a transaction code in SE93.

75. Does SAP has a GUI screen painter or not? If yes what operating systems is  it available on? What is the other type of screen painter called? 
Ans. 

76. What are step loops? How do you program pagedown/pageup in step loops? 
Ans. Step Loops:  these are repeated blocks of fields in a screen.

77. Is ABAP a GUI language?
Ans. YES

78. Normally how many and what files get created when a transaction program is  written? what is the XXXXXTOP program? 
Ans. 



79. What are the include programs? 
Ans. Self-contained program that executes a particular task.
An include program has two main functions:
•	It contains code which can be used by several different programs. 
•	It helps you to modularize programs, which consist of many different logically related parts. Each of these parts is stored as a separate include program. 
Include programs improve the readability of programs and make maintenance easier.

80. Can you call a subroutine of one program from another program?
 Ans. yes (using PERFORM)