BBritain
VIP Member
Hi Gurus,
I have been working on a table trigger on the F0911 (After Record is Inserted) which will take an F0911 record, determine if it is eligible for splitting, and if so, create a reversing record and multiple split records.
Unfortunately, I have only gotten to creating messages in a custom table before I started getting errors related to "ASYNCHRONOUS BUSINESS FUNCTION ERROR" and "TRANSACTION ERROR" (see below for complete errors). So this was narrowed down to an Table I/O Insert to a custom table.
I was able to avoid the errors by going in to the application, finding the F0911 End Document function and unchecking the "Include in Transaction" checkbox (in multiple locations). Philisophically I feel this is not the way to go, since there could be multiple more applications that would need this modification, so I am looking for alternatives.
Can anyone recommend (with experience) using subsystem jobs, or database triggers, or any other method/combination that might accomplish this task? I would even still consider table triggers if I could get around the transaction processing issues without modifying the Applications/MBFs.
I worry that since I am using MBFs to create the new records that the recursiveness will also make the table trigger alternative a poor choice.
Thanks for any and all suggestions,
Ben Again,
Error 1: ASYNCHRONOUS BUSINESS FUNCTION ERROR - Asynchronous business function did not finish successfully for form P0911_W0911A_ZJDE0001/nThere was a problem with the server while running the business function F0911FSEndDoc. The server may still be available, but because of state information, the entire unit of work must be resubmitted. Please exit the application and restart it.
Error 2: TRANSACTION ERROR - Transaction cannot be committed. It was canceled.
I have been working on a table trigger on the F0911 (After Record is Inserted) which will take an F0911 record, determine if it is eligible for splitting, and if so, create a reversing record and multiple split records.
Unfortunately, I have only gotten to creating messages in a custom table before I started getting errors related to "ASYNCHRONOUS BUSINESS FUNCTION ERROR" and "TRANSACTION ERROR" (see below for complete errors). So this was narrowed down to an Table I/O Insert to a custom table.
I was able to avoid the errors by going in to the application, finding the F0911 End Document function and unchecking the "Include in Transaction" checkbox (in multiple locations). Philisophically I feel this is not the way to go, since there could be multiple more applications that would need this modification, so I am looking for alternatives.
Can anyone recommend (with experience) using subsystem jobs, or database triggers, or any other method/combination that might accomplish this task? I would even still consider table triggers if I could get around the transaction processing issues without modifying the Applications/MBFs.
I worry that since I am using MBFs to create the new records that the recursiveness will also make the table trigger alternative a poor choice.
Thanks for any and all suggestions,
Ben Again,
Error 1: ASYNCHRONOUS BUSINESS FUNCTION ERROR - Asynchronous business function did not finish successfully for form P0911_W0911A_ZJDE0001/nThere was a problem with the server while running the business function F0911FSEndDoc. The server may still be available, but because of state information, the entire unit of work must be resubmitted. Please exit the application and restart it.
Error 2: TRANSACTION ERROR - Transaction cannot be committed. It was canceled.