Entity Framework 6 + Transaction – Multiple SaveChange with Error "Violation of PRIMARY KEY constraint"

Entity Framework 6 + Transaction – Multiple SaveChange with Error "Violation of PRIMARY KEY constraint"
 
Error : Violation of PRIMARY KEY constraint "PK__TEAM__C406B58F03317E3D". Cannot insert duplicate key in object "dbo.TEAM". The duplicate key value is (900). The statement has been terminated.

 
   // Code with Error ..
 
   using (TransactionScope scope = new TransactionScope())
   {
      TEAM item = null;
      var objectContext = (this.context as IObjectContextAdapter).ObjectContext;
 
      item = new TEAM();
      item.TEAM_ID = 1900;
      … …
 
      this.context.TEAMs.Add(item);
      objectContext.SaveChanges(System.Data.Entity.Core.Objects.SaveOptions.None);
 
      item = new TEAM();
      item.TEAM_ID = 1910;
      … …
 
      this.context.TEAMs.Add(item);
      objectContext.SaveChanges(System.Data.Entity.Core.Objects.SaveOptions.None); <= Error would be occurred from this line.
 
      scope.Complete();
      objectContext.AcceptAllChanges();
   }
 
 
   // Executable Code ..
 
   using (TransactionScope scope = new TransactionScope())
   {
      TEAM item = null;
      var objectContext = (this.context as IObjectContextAdapter).ObjectContext;
 
      item = new TEAM();
      item.TEAM_ID = 900;
      … …
      this.context.TEAMs.Add(item);
 
      item = new TEAM();
      item.TEAM_ID = 901;
      … …
      this.context.TEAMs.Add(item);
 
      objectContext.SaveChanges(System.Data.Entity.Core.Objects.SaveOptions.None);
 
      scope.Complete();
      objectContext.AcceptAllChanges();
   }
 

Error Reason : The Error would be occurred from 2nd SaveChange() Execution.
For 1st SaveChange() Execution, the First TEAM Object Item has been added and has not been committed on the Database.
For 2nd SaveChange() Execution, the First TEAM Object Item would be added again.
The same Item would be added twice.
The Entity Framework would validate the Item with same Primary Key during adding twice.