some abap questions
1 What are the problems in processing batch input sessions? How is batch input process different from processing on line?
2 . What does an EXEC SQL stmt do in ABAP? What is the disadvantage of using it?
3 What are the exceptions in function module? what is the use of exceptions
4 . How are the date and time field values stored in SAP?
5 . What transactions do you use for data analysis?
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.
I) 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.
ii) If session processing fails data will not be transferred to SAP database table.
... PERFORMING form
Executes the Native SQL statements enclosed between EXEC SQL and ENDEXEC statements. Unlike Open SQL, the addressed database tables must not be declared in the ABAP Dictionary.
You cannot perform reliable authorization checks using EXEC SQL. You should implement them at program level instead.
EXCEPTIONS lists the exceptions to be handled by the calling program itself. If one of the exceptions occurs, SY-SUBRC is set to the corresponding value and control returns back to the calling program.
This helps as a communication interface between the function module and the calling program. If you are building your own function module, and want to use exceptions then it can be done with the statements RAISE and MESSAGE ... RAISING. If exception is not to be handled by the calling program itself, then RAISE terminates the program with a runtime error; whereas MESSAGE ... RAISING outputs the message.
<b>YYYYMMDD AND HHMMSS</b>