topic Re: what is a transaction in Application Development and Automation Discussions

what is a transaction

Former Member — Thu, 11 Oct 2007 11:24:09 GMT

hi gurus

can anybody inform me

what is a transaction

how to define it

thank you

kals.

Re: what is a transaction

former_member189629 — Thu, 11 Oct 2007 11:25:34 GMT

Kalyan,

Transaction, in R/3 system is an operation that lets the user make necessary changes to the database. The entire R/3 system is nothing but set of business transaction. The data transfer from old system to SAP R/3 database, or modifying data, or deleting data, which is not required, is done through transaction.

For SAP system, Transaction is nothing but sequence of steps called as dialog steps and for user it is sequence of screens that appears one after the other depending upon the option he selects. The special transaction monitor called the SAP dispatcher handles the sequence of steps that takes place in any transaction. The main task of transaction is to update database table. The database table is not updated until a transaction is completed. All changes can be rolled back if the transaction has not finished.

You can create transactions from SE93 or directly from SE*).

Reward if helpful,

Re: what is a transaction

Former Member — Thu, 11 Oct 2007 11:27:56 GMT

hi Kalyan,

look these sites:

/people/horst.keller/blog/2004/10/21/abap-geek-3--about-transactions

http://help.sap.com/saphelp_nw04s/helpdata/en/cb/4da13c77e91409e10000000a114084/frameset.htm

Regards

Allan Cristian

Re: what is a transaction

Former Member — Thu, 11 Oct 2007 11:50:27 GMT

<b>Transaction</b>

To emulate a business transaction, a program may need to perform several steps. A financial program, for example, might transfer funds from a checking account to a savings account with the steps listed in the following pseudocode:

begin transaction

debit checking account

credit savings account

update history log

commit transaction

Either all three of these steps must complete, or none of them at all. Otherwise, data integrity is lost. Because the steps within a transaction are a unified whole, a transaction is often defined as an indivisible unit of work.

A transaction can end in two ways: with a commit or a rollback. When a transaction commits, the data modifications made by its statements are saved. If a statement within a transaction fails, the transaction rolls back, undoing the effects of all statements in the transaction. In the pseudocode, for example, if a disk drive crashed during the credit step, the transaction would roll back and undo the data modifications made by the debit statement. Although the transaction failed, data integrity would be intact because the accounts still balance.

In the preceding pseudocode, the begin and commit statements mark the boundaries of the transaction. When designing an enterprise bean, you determine how the boundaries are set by specifying either container-managed or bean-managed transactions.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d329d190-0201-0010-e7a1-96a9f893b40b

REward if useful