Announcements
Dear Experts,
I`m having an odd error message upon selecting supplier account on PR line level...
--------------------------------------------------------------------------------------------------------
SourceDocumentLineItem object not initialised.
Stack trace
(S)\Classes\SourceDocumentLineItem\newFromSourceDocumentLineImplementation - line 27
(S)\Classes\SourceDocumentProcessorBase\parmCurrentItem - line 5
(S)\Classes\SourceDocumentLineState\validatePostTransition - line 18
(S)\Classes\SourceDocumentStateBase\transitionTo - line 27
(S)\Classes\SourceDocumentProcessorBase\submit - line 11
(S)\Classes\SourceDocumentLineProcessor\submitSourceDocumentLineImplementation - line 124
(S)\Classes\SourceDocumentProcessorFacade\submitSourceDocumentLineImplementation - line 26
(S)\Data Dictionary\Tables\PurchReqLine\Methods\createSourceDocumentLine - line 7
(S)\Data Dictionary\Tables\PurchReqLine\Methods\Insert - line 8
(S)\Classes\xRecord\dbOpInTransaction
(C)\Classes\FormDataSource\write
(C)\Forms\PurchReqTable\Data Sources\PurchReqLine\Methods\write - line 14
(C)\Forms\PurchReqTable\Data Sources\PurchReqLine\Fields\VendAccount\Methods\modified - line 19
(C)\Classes\FormStringControl\modified
--------------------------------------------------------------------------------------------------------
Any suggestions whats causing above error?
Kind Regards,
V
*This post is locked for comments
Go to procurement and sourcing module and perform purchase order distribution reset and once completed, confirm po again it will work.
Hello, I am took one per one objects in the error message and compiled and sincronized (tables) them... , run cil complete ... but it didn't work
Then I recalculated the taxes (in code taxes form has the menu option for open transactions) Again didn't work
Later I compiled "maps" and "Clasess" nodes ...(all) and suddenly worked. the problem was solved.
Regards.
Hi,
Run a full CIL compile and see if this solves your problem.
Regards Hossein
In this case - complete AOS service/SQL server reboot solved above error.
Regards,
V
Also this discussion is related, there are different reasons like bad data/setup/record references elsewhere too:
Hi Vilmos,
Thank you for your quick response - how can I check if the record has broken reference or not? Is there any specific tables I need to compare/look at?
If the code is involved - I might just skip it, as it's not my strongest side.
Forgot to mention - found out that SQL server rebooted over the night while AOS was still operating and suddenly everyone is getting loads of error messages. I`ll try to restart AOS and reboot SQL - see if that fixes the major issues from this morning.
Regards,
V
We had a similar error this week but with purchase orders during source document processing.
We have discovered that there were orphaned records in the SourceDocumentLine table that did not tie in with the purchase order id, and had to delete them before we could do the posting again correctly.
Have a look at this discussion and see if you have a similar case:
André Arnaud de Cal...
294,110
Super User 2025 Season 1
Martin Dráb
232,866
Most Valuable Professional
nmaenpaa
101,158
Moderator