Krishna Raut (2068884)-Assignment 2

WEEK 1
Q1. SAP R/3 Architecture.
• R signifies Real-time system
• 3 represents – 3-tier architecture.
• SAP R/3 is a 3-tier architecture consisting of 3 layers.

Q2. Domains And Data Elements.

• Domain describes the technical attributes such as data type and length of a
table field.
• Data Element gives the field labels and documentation for the table field.
• Data Element = Domain + Description/Meaning -> Semantics.

Q3. Views in Dictionary.

• A view acts similar to a virtual table - a table that does not have any
physical existence containing fields from one or more tables.
 Types of views:
i. Projection View:
• If a view is created on a single table, then it is called as Projection View.
• Using this type of view, we can minimize the fields by projecting only
required fields and rest fields will be filtered out.
• This view allows us to read and also maintain the data.
• No Corresponding Object created in DB.
• Can be created on Transparent, pooled, cluster tables.
• No creation in underlying DB

ii. Database View:

• Created on one or more tables by using inner join.
• No maintenance allowed. Only read.
• creation in underlying DB.
• a database view can only contain transparent tables.
• Selection can be done.
iii. Help View:
• The help views are created on two or more tables by using outer join,
specifically for the "Search-helps" object in DDIC.
• No maintenance allowed. Only read.
• a help view can only contain transparent tables.
• Used as selection method for search help.
iv. Maintenance View:
• The maintenance view is created on two or more tables
• the tables must have a foreign key relationship.
 • It allows us to maintain and read the data of the table.
• You cannot directly enter the join conditions as for database view.
• TMG must be created.

Q.4 Structure, APPEND Structure in DDIC

Structure:
• Structures are data objects (comprised of components of any data type)
that are saved in sequence in the memory.
Append Structure:
• APPEND Structure - for Table Enhancement. Adding additional fields to the
standard Table But without changing the standard table’s structure
• Fields from APPEND Str. are added to the End of the table always
• We Don’t need any access key but is required during modifications.
• APPEND Str is Table Specific and normal str is not table specific(re-usable).

Q.5 Currency and Quantity Fields in Table Creation

• Currency (amount fields) use CURR data type
• Quantity fields use QUAN data type
• CURRENCY and QUANT fields are special as they need a UNIT that is for
currency u need currency type like EURO, USD etc., whereas for quantity
you need to know the unit that is KM, HOURS etc. etc.
• SO, whenever you have such fields in your table you need to have a
reference field to assign the UNIT for these fields.

Q.6 Types of Indexes in DDIC

• Indexes are used for fast retrieval of data from database.
 Primary Index:
• Primary index is created automatically on key fields of data when table is
created in SAP.
Secondary Index:
• The secondary index is required when there is retrieval of data on non-key
fields. Secondary index is not created automatically. It is created manually
depends on the requirement.

Q.7 Types of DB Tables in DDIC.

There are three types of database tables:
1. Transparent tables
2. Pooled tables
3. Cluster tables
Transparent tables:
• It has one-to-one relationship with the table in the database i.e., table in
the database has the same name as in the dictionary. The database table
has the same name
• Secondary indexes can be created and buffering can be done on
transparent tables.
Pooled Tables / Table Pool:
• Several pooled tables can be combined to form a table pool.
• It has many-to-one relationship with the table definition in the database
i.e., many pooled tables are stored in a single table in the database called a
table pool.
• Secondary indexes cannot be created on Pooled tables and can be
buffered.
 • Table Pools are used to hold large number of small tables. They need not
have key in common.
Cluster tables / Table Cluster:
• Several cluster tables can be combined to form a table cluster.
• It has many-to-one relationship with the table definition in the database
i.e., many cluster tables are stored in a single table in the database called a
table cluster.
• Table Clusters are used to hold few numbers of large tables that have
common primary key fields.
• Secondary indexes cannot be created on Cluster tables and cannot be
buffered.

Q.8 Purpose and Types of Internal Tables

• An Internal table is a temporary table gets created in the memory of
application server during program execution and gets destroyed once the
program ends.
• It is used to hold data temporarily or manipulate the data.
• Itab is variable for multiple record.

Types of internal tables:

Q.9 System variables and name few
• Variables to store systems current state information.
• These variables always filled by the SAP runtime environment.
e.g., SY-DATUM – System Date
SY-INDEX – Number of Loop passes
SY-TABIX – Current line of Internal Table
Sy-ucomm – contains function code
Sy-lsind – tracks the number of secondary output lists
Sy-user
Q.10. Difference between IF, CASE, DO, while.
IF, CASE: Both are control statements.
• Case statement is good for performance wise because here we declare
cases and according to these cases program will be executed.
• When we use if statement then the cursor goes to in the loop, whenever
the loop is not complete till then the program will not execute.
• Thats by in performance basis the case statement is good
DO, while.
• DO: Unconditional, WHILE: Conditional

Q.11. Explain EXIT, CONTINUE

EXIT:
• completely go out of the LOOP statement
• Can be used in loop as well outside the loop.
CONTINUE:
• skip the current processing of the record and then process the next record
in the LOOP statement.
• Can only be used in loop.

Q12. Explain What is Work Area and Internal Table.

Internal Table: A variable for multiple records.
WA: A variable for single record.
It is single line structure of internal table.
Q.13 Explain Itab Operations
• DESCRIBE TABLE <itab> LINES <v_lines>.
• SORT <itab> BY <field> ASCENDING/DESCENDING.
• APPEND <wa> to <itab>.
• INSERT <wa> INTO <itab> INDEX <index>.
• DELETE <itab> INDEX <index>.
• DELETE <itab> WHERE <condition>.
• DELETE ADJACENT DUPLICATES FROM <itab>
• [COMPARING <f1> .. <fn>|ALL FIEL <fn>}|ALL FIELDS}].

Q.14. Explain the Foreign Key Relation

• Foreign Key Relationship is the link between TWO table Fields i.e. to restrict
the invalid data in One table(Fkey Table) by checking with the valid set of
values from other table (Check Table)
• Both Fkey, Check table field should have referred Domain
• Check Table field must be part of primary Key

Q.15. How to Delete Duplicates from ITAB.

• First sort the ITAB.
• Then use DELETE ADJACENT DUPLICATES.

Q.16. SY-TABIX vs SY-INDEX

 • Sy-tabix is used to find the current line in the internal table; it's a current
line index. Whereas sy-index in used to find the number of current passes
in the loop statement.

Q.17. Role of Application Server.

• These application servers execute ABAP applications and communicate
with the presentation components, the database, and also with each other,
using the message server.
Q.18. Types Of Work Process in Applications
SAP has seven types of work processes;
1 – Dialog Work Process , D: To execute Dialog Steps
SAP Profile Parameter: rdisp/wp_no_dia
2 – Update Work Process, V: For Database Updates
SAP Profile Parameter: rdisp/wp_no_vb
3 – Enqueue Work Process, E: Responsible of Lock Table
SAP Profile Parameter: rdisp/wp_no_enq
4 – Background Work Process, B : Responsible of Background Jobs
SAP Profile Parameter: rdisp/wp_no_btc
5 – Message Server Process, M: Responsible of Routing the Messages between
the Application Servers)
6 – Gateway Work Process, G: Responsible of Message Transfer between SAP
Systems
7 – Spool Work Process, S: Responsible of Spool Requests

Q.19. SAP Application Server architectures

Q.20. Database View vs Help View
• database views restrict it to inner joins, whereas help views also make
outer joins possible.
• A help view is not defined on the database. Whereas DB view defines.
• A help view implements an outer join, which means that the full content of
the primary table of the help view is always displayed. But this Is not in case
of DB view as it implements the inner join.

Q.21. Primary key?

• A primary key is a field or combination of fields that uniquely identify a
record in a table.
• First field in the table must be PKey.

Q.22. Table Maintenance Generator

• SAP Table Maintenance Generator (TMG) is a tool to generate a table
maintenance program i.e., it will generate a program to maintain (Create,
Edit & Delete) entries in a table.
• For multiple entry purpose.

Q.23. Database View vs Help View

• database views restrict it to inner joins, whereas help views also make
outer joins possible.
• A help view is not defined on the database. Whereas DB view defines.
• A help view implements an outer join, which means that the full content of
the primary table of the help view is always displayed. But this Is not in case
of DB view as it implements the inner join.
Q.24. CLEAR, REFRESH, FREE
• Free:
Memory and data both released.
For all variables, itabs.
• Clear:
Make the variable empty that is data released but memory remains as it
is.
For all.
• Refresh:
Used for table to clear all the entries from the internal table body. but sill
memory allocation exist.
For itabs only.

Q.25. Inner Join Vs Outer Join

Table 1. Table 2.

Result of inner Join:

Result of outer join:

Q.26. Search Help.

• Search Help is a data dictionary object which is used to create a popup
window that contains all the data related to your search. It is an input Help
that permits the user to display a list of possible values for a screen field.
• Creating Search Help
• Linking the Search Help at Data Element Level

Q.27. Role of Selection Method in a Search Help.

 • The selection method describes the database object from which the data is
read. A database table or view can be defined as a selection method
• It is source for possible values.

Q.28. Which itab can be used without any restrictions

• Standard internal table.

Q.29. Search time Depends on no.of records in Hasing table

• Hashing Algorithm.

Q.30. Explain Lock Objects and the Function Modules?

• The SAP system synchronizes several users’ simultaneous access to the
same data records with a lock mechanism.
• Lock KUNNR = ‘1000’
• Update KNA1 KUNNR = ‘1000’. SET new values
• After updation
• Unlock/Release KUNNR = ‘1000’
When you activate a lock object in the ABAP Dictionary, the system automatically
creates function modules for setting (ENQUEUE_<lock object name>) and
releasing (DEQUEUE_<lock object name>) locks.

Q.31. Explain Primary Key in a DDIC Table?

• A primary key is a field or combination of fields that uniquely identify a
record in a table.
• First field in the table must be PKey.
Q.32. Standard Itabs with Unique keys?
• A unique index does not permit multiple entries with same values.
Q.33. Chain Operator?
• ABAP programming allows to concatenate consecutive statements with
same keyword in the first part into a chain statement.
Q.34. Explain the Purpose Comments and How to Comment in ABAP?
• Comments are used for documentation purpose
• “Single line comment and can be start from anywhere in line.
• * Single line comment and must be start from first space in line.

Q.35. Work area vs Internal Table?

• Internal Table: A variable for multiple records.
• WA: A variable for single record.
• It is single line structure of internal table.
Data wa_kna1 type kna1.
Data it_kna1 type table of kna1.

Q.36. What is Secondary Index and when to go for it?

• Primary index created automatically on key field.
• Non-key Fields when we access the data frequently on based on non-key
fields.
• Secondary indexes are used to enhancement performance when retrieving
data. For example, say you have a table AFKO where the key to the table is
AUFNR. You can select data from this table using AUFNR, the performance
will be great because you are using the key. Say you need to hit this table
with GLTRP (finish date), it is not part of the key, so the performance would
be poor. If you created a secondary index using this field GLTRP, the
performance would be improved.
Q.37. explain the Foreign Key and the pre-requisites?
• Foreign keys are used to establish the relationship between the different
tables present in the ABAP Dictionary.
• We can create value checks for input fields using the foreign keys. Value
checks are required to validate the values of some fields in a table with the
values of other fields of different tables.
• FK field in one table must be PK field in another table.

Q.38. Explain Control break statements

• Control break processing is used to execute a piece of code whenever a
specific condition in the data is detected during the processing of internal
table loop.
• Control break statements are statements which are used to control the
sequence of execution of statements with in LOOP....ENDLOOP..
• These statements are executed only with in loop...endloop.
• Control break statements are
• AT FIRST - This statement is executed/triggered for the first iteration of
loop (SY-TABIX = 1).
• AT LAST - This statement is executed/triggered for the last iteration of loop.
• AT NEW - This is executed whenever there is a new value on specified field.
• AT END OF - This statement is executed whenever the new value ends on
specific field.

Q.39. Explain Buffering and types of Buffering.

• While accessing the table for the 1st time, if table is buffered, a copy of the
data is maintained in App.server
• While accessing the same table for the Next time onwards, Data from
App.Server is accessed If table is buffered, Else reach DB server
TYPES:
 • Buffering is recommended for the tables whose data is NOT changed
frequently.
BY PASS BUFFERING:
• When a table is buffered but we need to access the data from DB table
instead of application server.

Q.40. What is the Search Help Exit?

• A search help describes the standard input help process. In exceptional
cases it may be necessary to deviate in some points from this standard. You
use a search help exit to implement such a deviation from the standard.
• Individual steps of the input help process can be skipped with a search help
exit.
• A search help exit is a function module that has a predefined interface.

Q.41. Primary Key Vs Foreign Key?

• primary key: to maintain data consistency of a database primary is used for
database tables. in sap for every database table, you should have at least
one primary key and generally all primary ket fields are top most fields of a
table.
 • foreign key: mainly used to provide referential integrities. I.e., to provide
relation between two tables the foreign key is used. foreign of one table is
the primary for that table and becomes foreign for another table which
must have a primary key.

WEEK 2:
Q.1. Classical Report Events.
• The events that are applicable for level 1 list only. That is for basic list only.
Classical report events are:

Addition to this-
AT SELECTION-SCREEN OUTPUT:
 • Triggered before re-display the screen for each Change.
• Used while modifying the selection screen.
END-OF-SELECTION: -
Triggered when last statement of START-OF-SELECTION event is executed

Q.2. GUI Status

• It is collection of all tool bars.
• That is collection of Standard tool bar, menu bar, application bar, title bar.
• Note: We cannot add buttons in title bar only.
• Create GUI Status Using Menu Painter (SE41).
• GUI Status Creation is at program Level and it has to be set explicitly to the
required Output list i.e. via SET PF-STATUS ‘<GUI Status Name in CAPs>’.
Both Line & Button Selection in the same Program
• Line Selection/Double Click is Valid Only when the Choose Button with
Fcode PICK & Func Key F2 presents in App.tool bar and is overwritten when
we set custom GUI Status.
• So that we have add the same explicitly to custom GUI Status along with
Our buttons to make sure that Double click works along with Button Click

Q.3. At Selection-Screen
• Triggers after user input and before leaving the selection screen.
• Validate the input and error messages for invalid data.
Q.4. Initialization
• Triggers before Display the Selection Screen (if exist) else as 1st event.
• Initialize the Selection Screen with Calculated Values as default values.

Q.5. Top-of-Page vs Top-of-Page During Line Selection.

1.TOP-OF-PAGE:
• It is classical report event.
• Triggers At the beginning of each New Page of basic list only.
• And it is used to print same header for all pages of basic list.
2. TOP-OF-PAGE DURING LINE
• It is interactive report event.
• Triggers At the beginning of each New Page of all the Secondary Lists
• To Print same header for all Pages of all the Secondary Lists

Q.6. Explain Interactive Report Events

• User Interaction with Output list can be done in via
1. Line Selection - Event - AT LINE-SELECTION
Sy-LSIND gets the number of output lists generated including the first
output list.
2. Button Selection - Event - AT USER-COMMAND (Gui status)
SY-UCOMM contains the FCode of the button clicked.
Q.7. SY-LSIND , SY-UCOMM
• Sy-LSIND gets the number of output lists generated including the first
output list.
 • SY-UCOMM contains the FCode of the button clicked.

Q.8. Select-Options
• It is range value input.
• DATA <vname> TYPE <dataType>
• SELECT-OPTIONS <name> FOR <vname>

Q.9. What is header line ?

• The header line is a field string with the same structure as a row of the
body, but it can only hold a single row.
• Header line or the work area is used as interface. we can't access data from
an internal table or send data to an internal table without header line.
• If we define internal table with header line , then we don't require to create
explicit work area.
• If an in ternal table created with out work area we have create a work are
of the similar structure of the table.
Q.10. Order of Classical Report Events.
• Load-of-program
• Initialization
• At Selection-Screen output
• At Selection-Screen on field
• At Selection-Screen on value request
• At Selection-Screen on help request
• At Selection-Screen
• Start-of-Selection
• End-of-Selection
• Top-of-Page
• End-of-Page

Q.11. Purpose of Report?

 • Report is the list of records or data.
• Purpose: To analyze the current state and help in decision making.
Q.12. Get Cursor?
• It is AT LINE-SELECTION event only.
• When the 2nd ry list is based on the Selected Column from Output list
• So that we have get the details of the selected column. i.e., name of the
column and value of the column.
• GET CURSOR FIELD <v_fnam> VALUE <v_fval>.
Q.13. Conversion Routine?
• It is at domain level.
• The Internal (DB) format/value and External (Output) format/value differs
for all the fields only if routine name exist at Domain Level.
• During the GET CURSOR, the value comes for Output list i.e external
value/format and the same has to be converted explicitly into Internal/DB
format(value) before using that value for further Selection from DB as DB
has internal format/value.
• FM to Convert from External to Internal
• FM ‘CONVERSION_EXIT_<routineName>_INPUT
• FM to Convert from Internal to External
• FM ‘CONVERSION_EXIT_<routineName>_OUTPUT

Q.14. Initialization
• It is first event in classical report event.
• Triggers before displaying the selection screen (if exist) else 1st event.
• Used to set the calculated values as a default value on selection screen.
Q.15. At Selection-Screen output
• It is classical report event.
• Triggers before redisplaying the screen for each change.
• Can be used to modify selection screen.
Q.16 Break Point vs Watch Point
 • Break point: Signal to interrupt the program execution so that we resume
step by step by see the live result.
Break Point can be -
Session Break point -
External Breakpoint -
• Watch Point: interrupt the program execution by watching the content of a
variable.

Q.17. Session Break Point Vs External Break Point

• Session Break point - active for that login period Only from the same
system execution
• External Breakpoint - active for particular duration for External Execution Ie
from remote Ie. From other SAP, web.
Q.18. F5, F6, F7, F8 - Role of these things in Debugging
• F5 - Single Step / Step by Step Execution
• F8 - Execute up to the next break/watch point if exist else execute the
whole program without any interruption
• F7 - To Return from the definition of the Function, Form, Module…
• F6 - Execute the Calling statement (CALL FUNCTION…PERFORM. as a single
statement.

Q.19. Role of Events in any programs?

• It is used to perform particular operation at particular timing.
• It gives the information for action / timing.

Q.20. Role Of Text Elements?

• It is used to give appropriate information on selection screen.
• Text Elements for which we can maintain Language translations
 • It has three elements:
1.selection text: input level
2.text symbol: input level
3. headings: output level

Q.21. Push Buttons on Application Toolbar? Fcodes?

• Function keys are used to give push buttons on application tool bar.
• Maximum 5 buttons are allowed from FUNCTION KEY 1 to FUNCTON KEY 5.
• FCodes: FC01 to FC05.

Q.22. Buffering? Types?

• While accessing the table for the 1st time, if table is buffered, a copy of the
data is maintained in App.server
• While accessing the same table for the Next time onwards, Data from
App.Server is accessed If table is buffered, Else reach DB server

• Buffering is recommended for the tables whose data is NOT changed

frequently.
BY PASS BUFFERING:
• When a table is buffered but we need to access the data from DB table
instead of application server.
Q.23. Full Buffering vs Single record vs Generic

Q.24. Size Category as part of Technical Settings.

• It is used to assigned initial memory in the DB for creating table entries.
• If initial reserved memory is full then implicit memory is allocated according
chosen size category.

Q.25. Data Class?

• It is Physical space in DB used to stored tables in DB.

Q.26. Any 5 transaction codes and purpose ? Any 5 Standard Tables ?

• SE11: DDIC
• SE21: Creating Package
• SE37: Function Builder
• SE38: ABAP Editor
• SE41: Menu painter
• SE51: Screen Painter
• SE80: Object Navigator
• SE91: Message Maintenance
• SE93: Maintain Transaction
 • OAER: Logo Creation
• KKBL: Button in ALV
STD Tables:
• KNA1: Customer general data
• LFA1: Vendor general data
• VBAK: Sales Document header data
• VBAP: sales document item data
• MARA--Material Master-General

Q.27. Subroutines Vs Function Modules.

• Subroutines are within program only while FM can be used globally.
• Subroutines are fast as compared to FM.

Q.28. Passs By Reference and Pass by Value?

• Pass by ref:
Changes in formal reflects in actual immediately.
Using/changing.
• Pass by value:
Changes in formal do not reflects in actual at all.
Using value().

Q.29. Pass By value and Result

• Pass by value and result:
Changes in formal reflects in actual only the after complete execution of
subroutines.
 Changing value().

Q.30. Define, Raise and Handle Exceptions of a Function Modules?

• Define exception in exception tab of the function module.
• And then Raise the exception in source code tap of the function model.
• Then handle the exception in our code or in ABAP editor by using SY-Subrc.

Q.31. BDC Programming?

• BDC: Batch Data Communication.
• BDC is an automated procedure for transferring large volumes of external
or legacy data into the SAP system using batch input programming.
• All the standard transactions can create only one record at a time. So, a
custom BDC program is needed to call that transaction repeatedly to create
bulk of records

Q.32. BDC Call Transaction Steps?

• First create a file with all data that we have to enter for the particular
transaction.
• Then create internal table with the same structure as of the file.
• Then Calle the FM ‘GUI_UPLOAD’. It transfers data from file to internal
table.
• Then declare it_bdcdata type table of bdcdata. Bdcdata is the table with
the fields of screen fields of the particular transaction.
• Then loop at our internal table and append itab values to it_bdcdata.
• Then CALL TRANSACTION USING it_bdcdata
• And refresh the it_bdcdata before the next iteration.
Q.33. BDC Session Method Steps.
• Session Method and Call Transaction Method both works on same Principle
i-e; Via Screens & Screens Fields Repeatedly.
• Session is like Folder in which we collect data from file then execute/
upload it to SAP data base via Batch Input Method using t-Code SM35.
• There are three steps to upload data through BDC Session Method, those
are,
1. Create Session – calling Function Module ‘BDC_OPEN_GROUP’ you
open session.
2. Insert Data – in Session from IT_BDCDATA using Function Module
‘BDC_INSERT to insert Screens, Fields and Values.
3.Close Session – using Function Module ‘BDC_CLOSE_GROUP’.
• At Last, you execute the SESSION from t-code SM35, as discussed before all
the error log are saved by the session, no need to write code.

Q.34. FMs used in Session Method and purpose?

• BDC_OPEN_GROUP: To open the session
• BDC_INSERT: To insert data from IT_BDCDATA to Session.
• BDC_CLOSE_GROUP: To close the session.
Q.35. Role of BDC programming?
• BDC is an automated procedure for transferring large volumes of external
or legacy data into the SAP system using batch input programming.
• All the standard transactions can create only one record at a time. So, a
custom BDC program is needed to call that transaction repeatedly to create
bulk of records

Q.36. types of FMs?

 • BDC_OPEN_GROUP: To open the session
• BDC_INSERT: To insert data from IT_BDCDATA to Session.
• BDC_CLOSE_GROUP: To close the session.

Q.37. Role of Transaction Recorder in BDC Program?

• To collect the screen and screen field information.
• And then we use this info to enter data from our itab to IT_BDCDATA.
• Tcode for transaction recorder SHDB.

Q.38. Different Modes of Display during Call Transaction?

• Mode A (default) - Display all the messages.
• Mode N – Nothing to display.
• Mode E – Shows error pages only.

Q.39. Control Break Events/Statements?

• Control break processing is used to execute a piece of code whenever a
specific condition in the data is detected during the processing of internal
table loop.
• Control break statements are statements which are used to control the
sequence of execution of statements with in LOOP....ENDLOOP.
• These statements are executed only with in loop...endloop.
• Control break statements are
• AT FIRST - This statement is executed/triggered for the first iteration of
loop (SY-TABIX = 1).
• AT LAST - This statement is executed/triggered for the last iteration of loop.
• AT NEW - This is executed whenever there is a new value on specified field.
 • AT END OF - This statement is executed whenever the new value ends on
specific field.

Q.40. Clear, Refresh, FREE.

DATA : Variable(1) type c.
Variable = 'X'.
• 1. FREE Variable.
• The memory allocated is refreshed and freed. Means after this statement
the memory to the variable is no more. It is freed from the program and
can be used for some other programs are purpose.
• 2. REFRESH Itab.
• Used for table to clear all the entries from the internal table body. but sill
memory allocation exists and you can use some other with in the program.
• 3. CLEAR variable.
• it clears the memory of the variable i.e., variable will be empty.

Q.41. How Session Method differs from Call Trans?

• First is error handling done explicitly in call transaction while implicitly in
Session method.
• Call transaction does the Data consistency check with the help of screen
logic. The Call Transaction processes the data quicker than with batch input
sessions.
• 'CALL TRANSACTION USING ' does not automatically support interactive
correction or logging functions. Sessions Method support stopping, going
back and correcting sessions that contain errors, and provides log details.
• With 'CALL TRANSACTION USING 'you can go for update the database both
Synchronously and Asynchronously but Sessions method does Synchronous
Database updates.
• The system executes a database commit immediately before and after the
'CALL TRANSACTION USING' statement whereas for the sessions method it
goes for Asynchronous processing. During processing, no transaction is
started until the previous transaction has been written to the database.
• Sessions Cannot be generated in Parallel. The batch input program must
not open a session until the preceding session is closed.