When the consistency check's "Payment" option is enabled, it examines whether all specification (SpecTrans records) are referring to an existing journal or transaction.

This check does not work, if specifications are referring to shared table records (SaveDataPerCompany = No), because it uses a generic select statement, that requires the referred table to have a dataAreaId field, which shared tables have not

As a result, if the consistency check is configured to "Fix error", then valid specifications are being deleted, which is quite unfortunate


Therefore, I suggest excluding "originator.DataAreaId == specTransSelect.SpecCompany" from the select statement in CustVendPaymentConsistencyCheck.checkFixSpecTrans method, when the referred table is shared. This should be rather easy as a DictTable object has already been initialized, allowing usage of the dictTable.dataPrCompany method