Enterprise Administration > Implementing Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Understanding Windchill ESI Architecture > Transaction Management > Transaction Resubmission
  
Transaction Resubmission
When a transaction fails, the overall Windchill ESI release is considered to have failed and the user who published the object can correct the problems that led to the failure and republish the object. For more information, see Enterprise Systems Transaction Administration Graphical User Interface. Resubmitted data originates from the Windchill ESI services; the EAI components of Windchill ESI do not store or handle any previous transactions or validate new transaction data against previous publications. All resubmitted data is processed as newly published objects. When objects are republished, by default only those objects that have changed since the last successful attempt to publish the objects was made are published. This maintains consistency between the Windchill ESI services and the distribution targets.
* 
Upon republishing an object by resubmitting the data, a new transaction object is created for every ERP instance where a failure occurred. However, the resubmitted data gets sent only to those distribution targets for which the original publish failed.