CE_STMT_INT_TMP - Intermediate table - OK for multiple concurrent statement processing

Hi All

My team are uncertain whether the bank statement interface process is meant to handle multiple bank statement interfaces at a time.

We see that there is a SQL loader routine that fills CE_STMT_INT_TMP from the bank flat file and then a 'Load Bank Statement Data' that applies the map and then fills the ORG_ID striped Interface tables.

But will multiple submissoins of the loader processes start to conflict with each others use of ce_stmt_int_tmp ... ie. delete rows just added by the previous process ... that's still running.

I feel sure that there must be some kind of table lock protection going on ?