E-Invoicing Submission Failing - SQL Trigger Error on BUSINESSDOCUMENTEXECUTIONREQUEST Table

(3) Share

Report

Posted on by RM-09090509-0

Hi all,
We have implemented the standard E-Invoicing feature in Dynamics 365 Finance & Operations for Saudi Arabia and Egypt. The setup was working as expected, and we were able to successfully submit our sales invoices using the standard submission process.
However, without any changes made to the configuration or customizations, the submission process has suddenly stopped working in our UAT environment.
We are now encountering the following error when attempting to submit invoices:

[Error] Sql command failed: Inner System.Data.SqlClient.SqlException
The target table 'dbo.BUSINESSDOCUMENTEXECUTIONREQUEST' of the DML statement cannot have any enabled triggers
if the statement contains an OUTPUT clause without INTO clause. Try again or contact with the system administrator.

Context: [CountryISOCode: SA, DocumentType: Customer invoice, LegalEntityID: e355, SubmissionType: blank]

This issue occurs at the point of submission, and the record is not being submitted at all.

It’s worth noting that the same feature is already deployed and working fine in the Production environment for one of the entities. The issue appears to be isolated to UAT, which makes it even more confusing since there have been no recent deployments or changes made to UAT either.

Has anyone encountered this error recently or can shed light on what might be causing this behavior?
Appreciate any support or insights on how to resolve this.

Thank you!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Syed Amir Ali 205 on at

Like (1)

Report
Copy link

Link copied!

Hey,

The BUSINESSDOCUMENTEXECUTIONREQUEST is a standard table used internally by the E-Invoicing module. This BUSINESSDOCUMENTEXECUTIONREQUEST table contains the electronic documents execution request details.

The error suggests either a trigger was recently added/enabled manually (possibly through SQL or script in UAT) or UAT and PROD differ in SQL Server version/configurations, making the same code behave differently.

Run the below script on the UAT database to check if any trigger enabled then disabled it temporarily.

SELECT name, is_disabled
FROM sys.triggers
WHERE parent_id = OBJECT_ID('dbo.BUSINESSDOCUMENTEXECUTIONREQUEST');

Please mark my answer as 'Verified' if it works for you.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Yng Lih 1,612 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi RM,

When E-invoicing doesn't work, it could be:

- the data i.e. the master data that you are trying in UAT has missing values

- the key vault expiration date or some other Azure setups has expired

- could it be there is a prod database restoration to UAT previously? if so, you may want to check the E-Invoicing setup to ensure its still pointing to UAT.

- since its UAT, you may want to try to go LCS > UAT > Maintain > Restart service

- last resort would be to seek help from Microsoft support via LCS support ticket submission

If this information was helpful, kindly mark it as 'Verified'. Thank you. :)

1 people found this reply helpful.

Was this reply helpful? Yes No
RM-09090509-0 67 on at

Like (2)

Report
Copy link

Link copied!

Hi @Syed Amir Ali,

Thank you for the solution on this.

We did find a trigger which was added, upon removing the trigger, The E-invoice submission started working as required.

Was this reply helpful? Yes No