Reg. LUW

[Former Member]

Hi All,

This is regarding a doubt on LUW,

1, Whether a batch process is a single LUW.

2, Then if i am Creating the Billing Documents in background that is through VF06 , then whether it will come under single LUW.\

3, Then some where inside the Invoice creation if they have used Select for update then a lock which has created will be held till the batch job completes ?

Regards,

Sen

[Former Member]

Hi All,

This is regarding a doubt on LUW,

1, Whether a batch process is a single LUW.

2, Then if i am Creating the Billing Documents in background that is through VF06 , then whether it will come under single LUW.\

3, Then some where inside the Invoice creation if they have used Select for update then a lock which has created will be held till the batch job completes ?

Regards,

Sen

[Former Member]

RV60SBAT (VF06) works in this way:

according to the criteria you specified on the selection screen RV60SBAT will create separate jobs running RV60SBT1 or (since release 4.7) SDBILLDL in those separate jobs. the number of separate jobs created varies in accordance to your selection.

these jobs will be spread across the available and free batch-workprocesses you have - this may be across several application serves, if available. this is where LUW comes into it: every job is processed in it's 'own' workprocess = LUW in this case which it will hold until the job ends. so according to the number of jobs it is possible that you have several batch processes working on your documents in parallel.

the lock processed on a documents will not be held from the start of the job until the very end, but just as long as it takes to bill a single document and make sure of the consistency of the whole process. so if you have lock-problems or documents not being billed due to locks held this can have several causes which you would have to investigate. there's no out of the box-rule for approaching this.

since you didn't tell us what release you are on i advise you to set the radio-button for posting in VF06 to: asynchronous.

as a workaround you might want to try to run program SDBILLDL in background with asyncronous posting, so there should not be a lock-problem any longer but of course this will kill the benefit of parallel-processing.

[Former Member]

Hi

This thread looks related to a problem we are experiencing:

We are using VF06 on version ERP 6.0 and at go lives we have to create a very large volume of invoices. When we run this job, SAP seems to find every available update process across all application and database servers and uses them all. Of course this stops everyone else doing any updates.

How can we control the number of update processes that SAP allocates to this billing job? We want to take advantage of the benefits of the parallel processing, but we don't want SAP to take every available update process.

Thanks Terry

[mvoros]

Hi,

the ABAP command COMMIT WORK AND WAIT interrupts the current LUW and stores the changes. I assume that you have an internal table and for each record from this table you run batch input. Maybe you can try to call after X batch inputs command COMMIT WORK AND WAIT. It should wait for all current updates. Something like

CALL VF01 line1

CALL VF01 line2

CALL VF01 line3

CALL VF01 line4

CALL VF01 line5

COMMIT WORK AND WAIT.

If you change mode in your command CALL TRANSACTION to synchronous you will lose the benefits of parallel processing.

[former_member240105]

Hello Terry,

                   Are you able to solve the problem ? We have the similar kind of problem  in our system.All the available update processes are occupied and there are huge number of updates waiting in the queue when SDBILLDL job kicked off with asynchronous update in variant.This is causing delay in updates as all others are waiting in the queue.

Appreciate your help in this regard.

Thanks,

Hari