on 08-19-2009 12:21 PM
Hello,
Within the SAP system, three conceptually different types of transactions.
1) Database transaction 2) update transaction 3) SAP transaction(ABAP transaction)
could you please explain me the use and difference between them in simple words.
Regards
Shridhar Gowda
Hi Sridhar,
Dialog transaction : These are the most common kind of transactions. The transaction code of a dialog transaction is linked to a Dynpro of an ABAP program. When the transaction is called, the respective program is loaded and the Dynpro is called. Therefore, a dialog transaction calls a Dynpro sequence rather than a program. Only during the execution of the Dynpro flow logic are the dialog modules of the ABAP program itself are called. The program flow can differ from execution to execution. You can even assign different dialog transaction codes to one program
Parameter transaction
In the definition of a parameter transaction code, a dialog transaction is linked with parameters. When you call a parameter transaction, the input fields of the initial Dynpro screen of the dialog transaction are filled with parameters. The display of the initial screen can be inhibited by specifying all mandatory input fields as parameters of the transaction.
Variant transaction
In the definition of a variant transaction code, a dialog transaction is linked with a transaction variant. When a variant transaction is accessed, the dialog transaction is called and executed with the transaction variant. In transaction variants, you can assign default values to the input fields on several Dynpro screens in a transaction, change the attributes of screen elements, and hide entire screens. Transaction variants are maintained in transaction SHD0.
Report transaction
A report transaction is the transaction code wrapping for starting the reporting process. The transaction code of a report transaction must be linked with the selection screen of an executable program. When you execute a report transaction, the runtime environment internally executes the ABAP statement SUBMITu2014more to come on that.
OO transaction
A new kind of transaction as of release 6.10. The transaction code of an OO transaction is linked with a method of a local or global class. When the transaction is called, the corresponding program is loaded, for instance methods an object of the class is generated and the method is executed.
Shitika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A database transaction, known as LUW or database LUW, is the period of time in
which the operations requested must be performed as a unit. This is known in the
database world as an all or nothing operation. At the end of the LUW, cither the
database changes are committed (performed) or they are rolled back (thrown
away).
u2022 An update transaction or SAP LUW is the equivalent to the database concept for
the SAP systems. It means that as a logical unit, these SAP LUWs are either
executed completely or not at all. Generally, a SAP LUW can have several
database LUWs. The special OpenSQL command, COMMIT WORK, marks the
end of a SAP LUW and the beginning of a new one.
u2022 A SAP transaction or ABAP transaction is made up of a set of related tasks
combined under one transaction code. This concept is related more to the
programming environment, in which an ABAP or SAP transaction functions like
a complex object containing screens, menus, programming logic, transaction
code, and so forth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sid,
Annindya is correct and all are ABAP transaction code. Transaction is shortcut to run a ABAP Program code and whenever we execute a Tcode the associated ABAP program executed.
The Tcode type will be decided on the nature of ABAP program and its purpose like Dialog, Report, Updation.
Thanks
Lokendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Technically Transation are of 5 types.
1.Dilog transactions
2.Report transactions
3.OO Transactions
4. Variant transactions
5.Parameter Transactions
But if you divide the transation in the below category
1) Database transaction 2) update transaction 3) SAP transaction(ABAP transaction)
then 1) will include all those transactions which display.maintain,administer anything related to database. Like Db02, Db16, Db17, ST04 etc..
2) will include those transations which actually update records ( a functional guy can give you better explanation)
3) Any transation with which you administer /use SAP system--Like SM21,ST22, SM04, SM50, SM51, SM66 ,scc4,se06 etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.