topic Re: Difference between Update KNA1 and with commit work in Application Development and Automation Discussions

Difference between Update KNA1 and with commit work

Former Member — Wed, 27 Sep 2006 11:39:46 GMT

Hi Friends,

Can any one tell me What is the diffrence between

1. UPDATE KNA1 and

2. UPDATE KNA1.

COMMIT WORK.

Thanks & Regards,

Naren.

Re: Difference between Update KNA1 and with commit work

Former Member — Wed, 27 Sep 2006 11:42:55 GMT

Hi Naren,

COMMIT WORK will immediately proceed to update the database.

If you don't commint it will be done automatically by the end of the session.

Aubin

Re: Difference between Update KNA1 and with commit work

Former Member — Wed, 27 Sep 2006 11:43:56 GMT

i guess, its not required to use COMMIT WORK with UPDATE.

UPDATE statement will take care of storing the database changes permanently.

Regards

Srikanth

Message was edited by: Srikanth Kidambi

Re: Difference between Update KNA1 and with commit work

Former Member — Wed, 27 Sep 2006 11:46:41 GMT

Hi,

Commit Work : Executes a database commit and thus closes a Logical Unit of Work ( LUW).

i.e.

All database updates are made irrevocable and cannot be reversed with ROLLBACK WORK.

All database locks are released.

Where as, UPDATE: Updates values in a database table (see Relational Databases ). You can specify the name of the database table either directly in the form dbtabor at runtime as contents of the field dbtabname. In both cases, the table must be known to the ABAP Dictionary.

Changes to lines made with the UPDATE command only become final after a database commit (see Logical Unit of Work (LUW)). Prior to this, any database update can be canceled by a database rollback.

P.S. Mark all helpful answers for points.

JLN

Re: Difference between Update KNA1 and with commit work

Former Member — Wed, 27 Sep 2006 12:28:25 GMT

Hi,

Commit work marks the end of the LUW and starts a new LUW ,all the changes made to the database cannot be rolled back.

Regards

Re: Difference between Update KNA1 and with commit work

anversha_s — Wed, 27 Sep 2006 12:38:06 GMT

hi,

commit work will update the database at that instant itself.

while with out that at the end of the session only the data base update wil happen.

rgds

anver

pls mark hlpful answers

Re: Difference between Update KNA1 and with commit work

Former Member — Wed, 27 Sep 2006 12:43:19 GMT

Hi Naren,

To apply the changes made to the runtime objects of persistent classes to the actual persistent objects in the database, execute the COMMIT WORK statement. (Alternatively, use COMMIT WORK AND WAIT or SET UPDATE TASK LOCAL). Unless you are executing an object-oriented transaction from within the Transaction Service, you must include the COMMIT WORK statement explicitly in the program. Otherwise, it is encapsulated in the Transaction Service. (If you explicitly include the COMMIT WORK statement as described here, the t op-level transaction runs in compatibility mode).

The function of the COMMIT WORK statement is extended when you use it in conjunction with Object Services. Before COMMIT WORK closes the SAP LUW and triggers an update, it calls internal methods of the Persistence Service. These methods bundle the changes made to managed objects of the Persistence Service and pass them to a special update function module using CALL FUNCTION ... IN UPDATE TASK. Thus the Persistence Service works with traditional update methods. The update module is usually registered after any update modules that have already been registered. The update is then triggered and the update task executes the update module in the order in which they were registered.

After the system executes the COMMIT WORK statement, it sets the attributes of each persistent object in the ABAP program to initial. (That is, it calls the IF_OS_STATE~INVALIDATE method).

Local Update

If you want to change managed objects directly, rather than using the update module, you must change the update mode of the implicitly used Transaction Service. That is, the following statements must be executed before the COMMIT WORK statement:

DATA TM type ref to IF_OS_TRANSACTION_MANAGER.

DATA T type ref to IF_OS_TRANSACTION.

...

TM = CL_OS_SYSTEM=>GET_TRANSACTION_MANAGER( ).

T = TM->GET_CURRENT_TRANSACTION( ).

T->SET_MODE_UPDATE( OSCON_DMODE_DIRECT ).

COMMIT WORK.

To ensure database consistency, the local update is activated internally using SET UPDATE TASK LOCAL. In such cases, the system raises an exception if there are already update modules registered in the update task. You can only register additional classical update modules after setting the mode. They will then also be updated locally.

Regards,

Laxmi.