Loop through matrix before document saved (or get doc number after save)

Question

Hi All,
I would like to loop through the matrix of a document (e.g. an invoice) before it is posted to the database (when the add button is clicked), but I would like to know at that point whether the invoice will definitely be posted.  When you look at ActionSuccess, the items in the matrix are already cleared.
Alternatively I would like to get the number of the invoice that was added so I can loop through the invoice lines records in SQL.
I have looked at quite a number of posts on tjis forum, but none of them has a definite answer to either of the options - or none I could find at least
Your help is appreciated and thanks in advance,
Adele

Answer 1

Hi Adele,
Here some thoughts form Frank and me:
As you mention, it makes basically no sense to process anything in such a document when a user can still cancel the saving (what about approvals???!!!!!).
To do the checks "after save" there are two options:
An easier one which is not 100% reliable from a "data perspective" - and one which is 100% reliable, but is a bit more "dangerous" because you will need to rely on an event to come BeforeAction = True AND BeforeAction = False (remember the "BubbleEvent" etc.)
Option 1.
(Not 100% (99.5%?) reliable is like suggested in some posts, but sometimes basic things are missed:
Use SQL in the ItemEvent handler:
If pVal.ItemUID = "1" And
pVal.EventType = SAPbouiCOM.BoEventTypes.et_ITEM_PRESSED And
pVal.ActionSuccess = True Then
"SELECT DocEntry FROM OINV WHERE UserSign = <internal number of user> AND UpdateDate = '<today>' AND DocTotal = <the value in UI> AND ...<maybe additional criteria as another person can reuse the user code - or a "DI API Add-On" may add a document in parallel>... ORDER BY DocEntry desc"
Theoretically it could happen that through a second connection / application instance a document could be posted at the same time. That's why this way is not 100% reliable...
Re time between "Add" and the SQL to retrieve the data being short (on what e.g. Florian relies on):
Please take in mind that you cannopt really count on the time being that short (milliseconds) when thinking about speed of the client PC, network traffic, users working at the same time with a company database, overall database response when working with a bigger database etc. etc.!!!
Option 2.
In the ItemEvent handler when BeforeAction = True start a global transaction that will block the table. After the ActionSuccess (BeforeAction = False) make a select to the table to get the desired data, and finally end the Transaction by commiting the data.
HTH,
Felipe & Frank