Hi Kalpana
There maybe some folks out there with a better answer, however my recommendation is this.
DO NOT RUSH THE FIX FOR THIS!!!
* Regardless of that the fact that this is now a production issue...trying to rush a fix will most likely cause more issues...as it already has.
The very fact that the transport has gone in out of sequence points to some not so hot import processes, which is only emphasized by a second failed attempt.
Go back through all of the related transports and identify all of the related objects in these transports requests...then get these into a separate transport.
If the words "This is way too hard" come to mind...this is where you learn that taking you time is ensuring your transports go in, in the correct sequence actually has benefits.
Good luck and take your time
Regards
Arden