One possible way is in the case of synchronous interface if ECC does not get response from PI after some period of time due to some errors or so, then abap application coding can write logic to place the mesgs in the queue for reprocessing. SO the mesg will be resend to PI for the reprocessing
actually my scenario is SAP ECC
>SAP PI>external system and it is done proxy to file its asynch; the situation is, for some reason the payload sent from ECC is not accepted by PI mapping; so its failing this interface. now what i wanted to do is, modify the payload in ECC system and resend to PI to process it again..
This is mere data issue that comes from ECC. You need to fix there and push the message request from ECC. If the data issue occurs, how do you handle manually for every mesg? Fix the data and provide details to ecc side and ask them to resend the request data as needed again.
Ya Baskar that is the solution.. but as of now it takes lot of time to fix the issue and transport the request from DEV to QA to PROD; and we have lot of client proxy programs like this, which is going to take lot of time.. so now i want to modify the payload in ECC and send it to PI ASAP; so looking for solution to this immediately...
If basis provide you authorization to debug the program in production, you can do it.
But, I would not recomend it . should be the last option.
I think, only solution is to change the logic of ECC program.
try it for 1 program, if it works well, go for other programs.