actually this case didnt occured in my ECC side, so why this case happen in SRM system? since the configuration is done in ECC system, and if we create reservation manually using the same asset number, it will also post to the same account which is not raise any error in the ECC, so its only happen if we trigger the creation of the reservation from SRM, so somehow the system not working as ECC side which is we dont want. Also the message was thrown from ECC system because the SRM send something which is not correct.
So the only thing is that we fix in SRM side, cause in ECC side we cannot change anything because all the transaction for good movement is working well icluding reservation