Regarding LUW

can anybody tell me What is LUW and use of it?

Hi:
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
o Each time you start a transaction
o When the database changes of the previous LUW have been confirmed (database commit) or
o When the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
o When the database changes have been confirmed (database commit) or
o When the database changes have been canceled (database rollback)
Regards,
Sookshma

Similar Messages

Logical unit of work

Hi all,
Can help me regarding LUW(logical unit of work) and its importance in r/3 ?
Thanks and Regards
Ravi

Hai Ravi Charan
There are 3 types of LUW's available in SAP
1)Database Transaction or DBLUW
2)SAP      Transaction or SAPLUW
2)ABAP     Transaction or ABAPLUW
1) DBLUW : when it is called it locks the rows , Update the rows & commit the rows issued by auto Commit
2) SAPLUW : collection of Business reports is called SAPLUW and Issuing the Commit
here UPDATE,INSERT,MODIFY statements are valid
Commit work is given by Developer Side.
3) ABAPLUW : What ever Transaction Code we are creating is called ABAPLUW it is belongs upon Developers
here 3 types of updates available
1) Bundled Updates
2) Un-Bundled Updates
1) Bundled Updates :
    in Bundled Updates all your updates in a single unit of work present in a PERFORM 'XYZ'
PERFORM 'XYZ' on Commit.
here PERFORM-kept in Buffer 'XYZ' this form having all your update statements
Priarities of execution.
Perform xy on comit it will execute first
perform ab on comit it will execute second
I want to change this execution Order
Perform xy on comit Level 2 it will execute second
perform ab on comit Level 1 it will execute First
because it will depends on Level command
Using in Function Modules
Call Function XYZ in Update Task.
Commit work.
In this case it stores in a buffer once encounters the commit statement this will executes from the buffer
so it is an asynchronos method
2) Un Bundled Updates
these are two types
1) Inline Updates
2) Buffered Inline Updates
1) Inline Updates : INSERT,UPDATE
when update statement found in a program then it is called inline update and you should give the 'commit work'after a update statement
inthe inline update if you not issue a commit work the system will automatically issues the commit work.
2) Buffered Inline Updates:
you will buffer all your inline updates and executes after Encounter the 'COMMIT WORK'
100
   XYZ --> we can not roll back here
200
   ABC---> if here is using commit
Thanks & Regards
Sreenivasulu P

Issue in CIF - Execute LUW again

Hi ,
   I created an integration model for stock transfer and when i try to activate it , it gives error. In SMQ1 (outbound queue from ECC to SCM) an entry is shown with status "RETRY" and it says "Command to tRFC/qRFC Execute LUW again" . In the queue manager in SCM (cq) it shows the same error ie., "Execute LUW again".
     I tried looking at the application log but it says "no application log available" .
     When i try to execute the LUW from SMQ1 it keeps giving me the same error again and again. I tried deleting the LUW from SCM using "queue manager /n/sapapo/cq". But it is not allowing me to delete the LUW.
      Since the queue is blocked it does not allow me to execute any other integration model. Kindly suggest a solution.

Hi
Should you not try deleting the blocked queue from TA SMQ1 itself and try to activate the integration model again if you are not able to debug the problem. I do not know the effects of doing this in your scenario but usually we delete the blocked queues from smq1. This method works for us most of the times.
To do this select the queue ( identified by a part of your document no. ) line and press delete button in std application tool bar.
What error are you getting when trying to delete the queue from /sapapo/cq?
regards
Mohan Chunchu
Edited by: Mohan V R Chunchu on Jan 29, 2008 10:58 PM

How can i check all the data in LUW's of RSA7

Hi All,
Iam trying to see the contents of LUW's for my data source in RSA7, but it keeps on giving me only data from data packet 7, even if i changed different numbers in
in option " choose" and different options in " extraction parameters"
its only displaying data when i select update mode as " repetition" no records when i select "delta"
i can imagine thats bcoz my last delta was failed. is that right??
How can i select data from different packagaes( as it shows in BW)???
any help pls.
Regards
Robyn.

Thanks guys
Actually i was trying to figure out the error data coming from my datasource failing my data load. the error is
" Value '60306XZED ' from field ANZVERTR is not convertible into the DDIC
data type DEC in data record 1 . The field content could not be
transferred into the typed transfer structure." 
that field ANZVERTR has type DEC & length 6 is assigned to infoobject 0UCCNTRCNT of data element /BI0/OIUCCNTRCNT ( DEC & length 17)that has type Number, data type DEC (Counter or Amount field with comma and sign.
I guess this assignement is correct but i cudnt able to understand how this valus "60306XZED" is coming to this field. at the first place ANZVERTR has length only 6 then how come it bring this value from R/3.
I cudnt able to figure out is this error from R/3 or BW.
Pls anybody help.
Regards
Robyn.

Error while executing LUW in SM58 - Mess.No.SY359

hi,
error while executing LUW in SM58
Error. Mess.No.SY359
"Function module does not exist or EXCEPTION raised-sy359"
trfc has been configured and try to push the Idoc through SM58 need help on this.
Regards
Leo

Hi,
This error is related to RFC settings and also the logon group in RZ12
Kindly generate the appropriated logon groups and confirm if the idocs are flowing
Thanks

RFC in background task LUW

Hello,
I've two RFC in user-exit. Both, using IN BACKGROUND TASK DESTINATION XI
When i execute the transaction, the user-exit is raising and i can see the follow error in SM58:
maximum size of requests for one LUW has been reached(1).
I've changing in the CC the parameter Maximum Conecction, however the error continue.
If i comment the second call function in the user-exit, the first call function is executed OK, the interface is right,
¿how can i do to execute two functions in the same LUW?
thanks

Hi,
>>¿how can i do to execute two functions in the same LUW?
you cannot - you need to do "commit work." after each RFC call
Regards,
Michal Krawczyk

Multiple RFC calls in one LUW

Hi Guys,
Is it possible to do multiple RFC(receiver) calls in a single LUW(Logical Unit ofWork) in PI 7.0??
If yes, can any1 pls tell me from which SP level has this been enabled??Also what settings do i need to do to create the scenario??
Thanks
Varun

hi
i think its possible.please refers to the link hope it will help u.
1.https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
2.http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
3.http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
regards
kasturika

Starting new SAP LUW inside ABAP method

I am calling a ABAP method and in that I want to start a new SAP LUW and do commit when leaving the method.
The requirement is that all update function modules called inside the method should only be committed and no other prior update FMu2019s(before calling the method) should not be committed.
Any idea if itu2019s possible to do that in ABAP OO and how do we do it.
Thanks & Regards,
Anand.

HI ,
Thanks for the quick replies. I tried using SET UPDATE TASK LOCAL but it was also committing all the prior update FM's before calling this method.
I also tried using the RFM - CALL FUNCTION 'ABC' IN BACKGROUND TASK DESTINATION 'NONE' . and then
COMMIT WORK AND WAIT.
Now when i do commit work it commits all the previous update tasks also.
And if i do not call COMMIT WORK right after the call to RFM, then the object that i am trying to create inside the RFM will not be committed.And then if i proceede some validations will fail as the objects were not created.
Is there a way to commit immediately when the RFM is called without commiting the calling transaction from where this RFM is called.
Any examples would be highly appreciated ..
Regards,
Anand.
Edited by: Anand Ajitsaria on Feb 4, 2011 9:54 AM

LUW data for smq2--Error During Delivery: Ibound processing locked

Hi all,
There are lot of messages(more than 7000) stucked in d Inbound queues, as viewed by SMQ2, and are in the retry mode for long.
In the LUW data the status of the queue is showing error during delivery and the error text is Inbound Processing Locked for example Deadline Processing 
can anyone please suggest what this problem is about and suggstions for removing this problem will be really appreciated.
This is urgent as the problem is in production.
Regards,
Rookie.

Hi Prateek,
The BPM involved is a dicesion making BPM which is creting large Idocs.
We have checked in SM12 and the messages are locked there. Can you please advice how can we unlock the messages from SM12.

Regarding function module in update task

Hi,
I have a function module(Zxxx) which is update type. i have called the fun.module in my program (Zyyy) using the syntax CALL FUNCTION ZXXX IN UPDATE TASK. As I suppose to debug the function module, I activated the update debugging in the debugging screen. But the controll still not goen into the function module. Please let me know solution.
Thanks & regards,
Suresh

>
sureshkumar vaniyasekar wrote:
> I activated the update debugging in the debugging screen. But the controll still not goen into the function module.
Hello Suresh,
What do you mean by not going?
If you are trying to do an F5 at the function call, the debugger is not "enter" into the FM. This is because at this point the function call is registered but the FM is not executed.
Update FM calls registered in a particular LUW are executed(in a special "UPD" workprocess) when there is a COMMIT encountered(may be explicit or implicit).
Did you read the online help on [Update Debugging|http://help.sap.com/saphelp_NW70EHP1core/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm] & [Breakpoint behaviour during Update Debugging|http://help.sap.com/saphelp_NW70EHP1core/helpdata/en/c6/617cbee68c11d2b2ab080009b43351/content.htm]?
BR,
Suhas

Questions regarding update function module

Hello experts,
I am on customer site to help them investigate one issue: they have a background job which runs periodically.
In the report database table A is changed firstly ( new entries are inserted ), then a update function module is called via keyword CALL FUNCTION ... IN UPDATE TASK.
Inside the function module database table B is updated. ( existing entries are updated )
Customer issue:
sometimes they find A is updated as expected, however B remains unchanged at the same time.
customer could not find exact steps to reproduce the issue. However the issue does exist there and occur from time to time.
the issue could only be reproduced in their production system, but works perfectly well in dev & Q system. It is difficult to debug in their production system for trouble shooting.
After analyzing related code, I have one doubt: according to ABAP help on CALL FUNCTION aaa IN UPDATE TASK, I know the function module aaa is called in a new update work process. I wonder whether there is any possibility there this issue might be caused because the update function module fails to get called at all? ( perhaps due to heavy system load so no free update function module could serve the table B update ? )
If update function module fails to execute, is there any system utility to record this? That is to say, will it be recorded in such as SM13 or SM21?
Looking forward to your expertise on this topic!
Best regards,
Jerry

Hello friends,
Thanks a lot for your interests on this issue. I update all my findings:
1. issue background: this issue occurs in SAP CRM Channel manageement Solution, software component CRM-CHM-POS.
2. due to some limitations, the table CMSD_CI_HISTORY and history table are not updated in the same LUW. Instead the first one is updated in normal work process while the other is done in update work process. Since I am not the original developer I didn't know the whole complex scenario ( I did see this is done delibrately in note 1764006 - CMS:Sell In Release creating PB with zero available quantity ).
So for the moment we have to accept this design.
3. during our testing ,we ensure COMMIT WORK is always called.
4. So why sometimes the first table update fails, however there is no hint at all for this failure in the system like ST22 and SM21 ?? ( forget SM13, since it is updated in normal work process ).
The root cause is the flaw of SAP code below.
The code has planned to raise exception if insertion failed due to duplicate records to be inserted.
Unfortunately, the fact is if we use "INSERT db FROM TABLE xxx" to insert records into database and some record already exists with the same key, it will result in a termination but SY-SUBRC is STILL 0; Just compare it with single insertion using "INSERT db FROM <work area>", in the same error situation, processing does not terminate, and SY-SUBRC is set to 4.
As a result in this case even the insertion fails, line 29 will never be executed as sy-subrc is always 0. Since the insertion fails and the exception is caught without any notification, so customer sufferred because they do not know what has happened.
Best regards,
Jerry

Potential problems with using a report to run a commit in a separate LUW.

I am working with a classic Badi within a transaction where I wanted to commit some information to a database before the commit that occurs at the end of the transaction.
Putting a commit point directly inside the BADI caused problems with cursors that were open inside the transaction, so I researched some and discovered that Report Programs can run in a separate database Logical Unit of Work (LUW).
I coded my BADI to call a report which does some database work based on input parameters, and then commits this work to the database before returning control back to the calling BADI function.
Does anyone know of any potential problems from doing this? It seems like a good way to get around restrictions on the use of commit points inside transactions, but I'm not sure if there could be potential undesired effects from doing this.
Has anyone tried this before?

Hi Clay,
Yes I did it too. We faced some issues with commit when using fm HR_INFOTYPE_OPERATION . We had to enclose it in separate report which only then let us do physical change in DB.
What is to be noticed here as well is (according to SAP) that DB commit is triggered each time work process is released which happens when:
- system shows dialog message
- RFC call is executed
- new transaction is called
The above however didn't work for me in couple cases, but using separate SAP LUW solves the problem (as you already read). This happens each time:
- new report is called (SUBMIT ...),
- new transaction is called (CALL TRANSACTION ...)
- new asynchoronus RFC call is executed (CALL FUNCTION...STARTING NEW TASK).
This approach works fine for cases I met and had to overcome with such solution. So far we didn't face any issues with that. Works perfectly
Regards
Marcin

Regarding COMMIT WORK

Hi,
I am using two BAPIs 'BAPI_ACC_ACTIVITY_ALLOC_POST' and 'BAPI_NETWORK_CONF_ADD' in my custom function module. These two BAPIs are used as explained below:
1) Fisrt the BAPI 'BAPI_ACC_ACTIVITY_ALLOC_POST' is called. If sy-subrc NE '0', the error messages are read.
2) Then the BAPI 'BAPI_NETWORK_CONF_ADD' is called. If sy-subrc NE '0', its error messages are read.
3) If there is no error for the two BAPIs called above, then the actual posting is done by calling the BAPI
'BAPI_ACC_ACTIVITY_ALLOC_POST'. If sy-subrc EQ 0, Commit work.
I would like to know if the Commit work in third step will commit the changes of the steps 1 and 2 as the the statement COMMIT WORK completes the current SAP LUW.
Or will it commit the step 3 only.
Thanks & Regards,
Soumya.

Hi soumya,
you can rollback for the step 1& 2 if sy-subrc ne 0.
and then use the comit work if sy-subrc eq 0 for step 3.
Hope this will help you.
regards,
Phani.

Discrepancy between the confirmation and deletion of qRFC-LUWs

Hi experts,
When I started PC to loading data from CRM system,data loading stopped.I check the
Log.
"discrepancy between the confirmation and deletion of qRFC-LUWs" (Message no. RSQU016)
How to solve it? Thank you.

Hi Gavin,
Please use Transaction code, SMQ1.
Drill in to the queue and delete the respective queue.
Or use transaction LBWQ
to get to the same information. Select your queue and delete it.
Regards,
Aby

Which files are require for sap IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1

Hi professionals,
Please help me out which file are require to download for SAP IDES ecc6.0 ehp6 with windows 2008 and db2 LUW 10.1
My requirement is to install Windows2008 R2 Service pack 1 + ECC6.0 ehp6 + DB2 LUW
So according to this i found these files,please tell me which one i require. second thing i am not able to find instalation master DVD in it.So which file is best for my environment.
51044815_1           BD IDES SAP ERP 6.0 EHP6 Inst. Export 1 of 40
51041991_1                 BS2011 Java Components - NW 7.03 1 of 4
51041992                SAP ERP 6.0 EHP6 Components
51041988_6                 NW703 UC-Kernel 720_EXT Windows Server on x64 64bit
51041988_5
NW703 Kernel 720_EXT Windows Server on x64 64bit
51041988_7
SL CONTROLLER 700
51041988_8
SL CONTROLLER 720
51041991_1
BS2011 Java Components - NW 7.03 1 of 4
51048277_3
721 NUC Kernel for SWPM SP06 - Windows Server on x64 64bit
51048277_6
721 UC Kernel for SWPM SP06 - Windows Server on x64 64bit
51048277_7
SL CONTROLLER 700 for SWPM SP06
51048277_8
SL CONTROLLER 721 for SWPM SP06
51048285_2
721_EXT NUC Kernel for SWPM SP06 - Windows Server x64 64bit
51048285_4
721_EXT UC Kernel for SWPM SP06 - Windows Server x64 64bit
51048285_5
SL CONTROLLER 700 for SWPM SP06
51048285_6
SL CONTROLLER 721 for SWPM SP06
51048532
DB2 LUW 10.1 FP4 RDBMS Windows x64
51048533
DB2 LUW 10.1 FP4 RDBMS CLI/JDBC-Driver
51041988_9
DB2 USER ENV
51041988_11
DB6 USER ENV
51041988_10
DB4 USER ENV
Thanks & Regards,
Bhipra Sakti

Hi Bhipra,
You need below DVDs for ERP 6.0 EHP6 IDES
51041985_11
DB2 USER ENV
70SWPM10SP06_4-20009707.sar
70SWPM10SP06
51044815_1
BD IDES SAP ERP 6.0 EHP6 Inst. Export 1 of 40
51044815_10
BD IDES SAP ERP 6.0 EHP6 Inst. Export 10 of 40
51044815_11
BD IDES SAP ERP 6.0 EHP6 Inst. Export 11 of 40
51044815_12
BD IDES SAP ERP 6.0 EHP6 Inst. Export 12 of 40
51044815_13
BD IDES SAP ERP 6.0 EHP6 Inst. Export 13 of 40
51044815_14
BD IDES SAP ERP 6.0 EHP6 Inst. Export 14 of 40
51044815_15
BD IDES SAP ERP 6.0 EHP6 Inst. Export 15 of 40
51044815_16
BD IDES SAP ERP 6.0 EHP6 Inst. Export 16 of 40
51044815_17
BD IDES SAP ERP 6.0 EHP6 Inst. Export 17 of 40
51044815_18
BD IDES SAP ERP 6.0 EHP6 Inst. Export 18 of 40
51044815_19
BD IDES SAP ERP 6.0 EHP6 Inst. Export 19 of 40
51044815_2
BD IDES SAP ERP 6.0 EHP6 Inst. Export 2 of 40
51044815_20
BD IDES SAP ERP 6.0 EHP6 Inst. Export 20 of 40
51044815_21
BD IDES SAP ERP 6.0 EHP6 Inst. Export 21 of 40
51044815_22
BD IDES SAP ERP 6.0 EHP6 Inst. Export 22 of 40
51044815_23
BD IDES SAP ERP 6.0 EHP6 Inst. Export 23 of 40
51044815_24
BD IDES SAP ERP 6.0 EHP6 Inst. Export 24 of 40
51044815_25
BD IDES SAP ERP 6.0 EHP6 Inst. Export 25 of 40
51044815_26
BD IDES SAP ERP 6.0 EHP6 Inst. Export 26 of 40
51044815_27
BD IDES SAP ERP 6.0 EHP6 Inst. Export 27 of 40
51044815_28
BD IDES SAP ERP 6.0 EHP6 Inst. Export 28 of 40
51044815_29
BD IDES SAP ERP 6.0 EHP6 Inst. Export 29 of 40
51044815_3
BD IDES SAP ERP 6.0 EHP6 Inst. Export 3 of 40
51044815_30
BD IDES SAP ERP 6.0 EHP6 Inst. Export 30 of 40
51044815_31
BD IDES SAP ERP 6.0 EHP6 Inst. Export 31 of 40
51044815_32
BD IDES SAP ERP 6.0 EHP6 Inst. Export 32 of 40
51044815_33
BD IDES SAP ERP 6.0 EHP6 Inst. Export 33 of 40
51044815_34
BD IDES SAP ERP 6.0 EHP6 Inst. Export 34 of 40
51044815_35
BD IDES SAP ERP 6.0 EHP6 Inst. Export 35 of 40
51044815_36
BD IDES SAP ERP 6.0 EHP6 Inst. Export 36 of 40
51044815_37
BD IDES SAP ERP 6.0 EHP6 Inst. Export 37 of 40
51044815_38
BD IDES SAP ERP 6.0 EHP6 Inst. Export 38 of 40
51044815_39
BD IDES SAP ERP 6.0 EHP6 Inst. Export 39 of 40
51044815_4
BD IDES SAP ERP 6.0 EHP6 Inst. Export 4 of 40
51044815_40
BD IDES SAP ERP 6.0 EHP6 Inst. Export 40 of 40
51044815_5
BD IDES SAP ERP 6.0 EHP6 Inst. Export 5 of 40
51044815_6
BD IDES SAP ERP 6.0 EHP6 Inst. Export 6 of 40
51044815_7
BD IDES SAP ERP 6.0 EHP6 Inst. Export 7 of 40
51044815_8
BD IDES SAP ERP 6.0 EHP6 Inst. Export 8 of 40
51044815_9
BD IDES SAP ERP 6.0 EHP6 Inst. Export 9 of 40
51048277_6
721 UC Kernel for SWPM SP06 - Windows Server on x64 64bit
51048277_8
SL CONTROLLER 721 for SWPM SP06
51048532
DB2 LUW 10.1 FP4 RDBMS Windows x64
51048533
DB2 LUW 10.1 FP4 RDBMS CLI/JDBC-Driver
Hope this helps.
Regards,
Deepak Kori

Regarding LUW

Similar Messages

Maybe you are looking for