Issue with Database Commit

Question

Hello All,
I have two include in my user exit of the sales order.
In one include I am doing some validation on the Order quantity of the sales order depending upon the order quantity in one of my Z table. If every validation is OK then I am exporting this order quantity to memory ID.
In the second include I am importing this Order Quantity and updating this Quantity in my database in my same Z table.
If I process one order at a time then everything is working fine but when I try to create two sales order at the same time then only second order is getting validated and order quantity is getting updated whereas for the first order no validation is performed and also order quantity is not getting updated in the Z table.
I really do not know is this issue related to database commit or something else.
Kindly help.
Regards
Sachin yadav

Answer 1

Sachin,
I guess i am getting to understand your requirement a little bit,
In validation I am modify the records in the Ztable as well I mean to say for each order created I am updating the Quantity in my Z table.
So you are just updating the quantity fields in the Z table, and this doesn't have any affect on the actual order quantity what soever, is that right or is the order quantity changed or modified based on the entry in the Z table?
So for the next order the validation should be done depending upon the new order quantity not the old order quantity.
Now this is a little tricky, now by next order do you mean the next order with respect to the number range or the next order in general?
For ex: Orders 1234, 1235, 1236 in order, or let us say there are 10 people around the world creating order simultaneously depending on the sequence in which their orders are saved.
I mean to say for the first order the validation should be done depending upon the old Qty and for the second order validation should be done by new order Qty.
When I am saving the two order at same time validation on both the order is done by old qyt bcoz new oder Qty from the first order is not yet upadated in the database when second order try to fetch the data from the Z table as i am saving both the order at same time.
This is what will happen most probably, even though you use the lock concept, let me try and explain...once you save the order in the user exit you are locking the object with enqueue and dequeue...something like below.
Order 1
userexit_save_doc.
enqueue ztable
select from Z table
validate based on the entries from z table
update/modify the z table with udpated values
dequeue ztable
end of userexit.
Now by the above code it doesn't mean that your changes are available in the Z table immediately, the table will actually be updated by the update modules along with other standard tables. Now in the mean time if an other order that hits userexit_save_doc before the update module of the previous order is complete it will still be looking at the old values.
Now in order to overcome the above sitauation you might need to add a COMMIT WORK AND WAIT in the userexit. But this will compromise the data integrity of the order and IS NOT SUGGESTED.
So you see, by locking the table you still haven't achieved your results.
Now, you need to confirm if the entries in the Z table are used only for validation and updating of data in the Z table or does it have any kind of affect on the Order quantity or any other Order specific values in general.
If it is only to track the quantity in the Z Table, and there is no affect on the order data in general, then i suggest that you create a  Z program and get all the orders that have been created/changed in a given period and then update the Z Table quantity accordingly, you can have this scheduled as a background job in the non business hours.
Let me know if i was completely off track in getting your requirement
Regards,
Chen