FIM-SQL ambiguous-import-flow-from-multiple-connector / already exists in management agent

I have a SQL table called transaction

This table would have entries employeeNo , field1, field2 , field3 ,...
I need to import the data from transaction and project unique Entries to FIM and AD
The data in transaction table would get an entry every time there is an update for any field for employee


Problem : 
When I import the data with unique Records as shown in the table for Batch 1 .. The record gets provisioned to AD and FIM with no issue

Asuming the next batch transaction were added Batch 2 as shown in the table 


I get an error for ambiguty ambiguous-import-flow-from-multiple-connector. I need a module in which i read the data from sql MA and delete the respective entry from table. 
For this structure I deleted the old records from batch1 and now I get error 

Microsoft.MetadirectoryServices.ObjectAlreadyExistsException: An object with DN "Emp1" already exists in management agent "MANAME".
   at Microsoft.MetadirectoryServices.Impl.ConnectorImpl.Commit()
The above error line number is provisioning code used to commit new connector for a MA when the number of connectors for the MA is 0.

I know why the above error already exist is comming, however i want it to join and not make a new connector. Join Rules are in place for EmployeeNo for this SQL MA and other MA.

I need to know if this kind of module can be implemented or not ? Where in I just read the transaction and next time update if already exist. 

Let me know if any questions.

Thanks in advance :)