KevinCourtney
Active Member
Hello,
I have a several processes, UBEs and Table Triggers that create F0911 G/L entries using the F0911 BeginDoc, EditLine, and EndDoc (B0900049).
I examine the cErrorFlag parameter that returns a ‘2’ if there is an error and then report back to the user that the “Edit Line Failed”
This really isn’t enough information, I need to know why the EditLine failed then report back to the user ‘why’, like; “Invalid Account Number”, “Invalid date, G/L Period closed”, etc., etc.
Do any of you have any suggestions on how I can get more detail on why the EditLine failed? Whether it is in one of the EditLine parameters or messages in the workcenter…
If I can’t get this info in the event rules do any of you have suggestions on debugging the EditLines that fail? I’ve tried using the jdedebug.log with limited success and now am resorting to the C++ debugger…
Any suggestions or ideas are appreciated.
Thanks,
I have a several processes, UBEs and Table Triggers that create F0911 G/L entries using the F0911 BeginDoc, EditLine, and EndDoc (B0900049).
I examine the cErrorFlag parameter that returns a ‘2’ if there is an error and then report back to the user that the “Edit Line Failed”
This really isn’t enough information, I need to know why the EditLine failed then report back to the user ‘why’, like; “Invalid Account Number”, “Invalid date, G/L Period closed”, etc., etc.
Do any of you have any suggestions on how I can get more detail on why the EditLine failed? Whether it is in one of the EditLine parameters or messages in the workcenter…
If I can’t get this info in the event rules do any of you have suggestions on debugging the EditLines that fail? I’ve tried using the jdedebug.log with limited success and now am resorting to the C++ debugger…
Any suggestions or ideas are appreciated.
Thanks,