Self Incompatibility for Print Receivables Transaction at BU Level and Performance benchmark stats

Summary:

If multiple print receivables transaction jobs are run for a single BU simultaneously, can it lead to same invoice being picked by more than 1 job and lead to data discrepancy or jobs might reach a deadlock situation as this job also updates print status related columns in ra_customer_Trx_All table?

Can you please confirm if Print Receivables transaction job is already set as self incompatible at BU Level?

What are the performance benchmark stats for Print Receivables Transaction job for understanding parallel processing that can be handled when the job is being run parallely for different BUs.