Hi @vadivelan, your requirement fits the classic request-response messaging pattern.
Synchronous request-response may not fit in the scheme of SCS as it is more geared for asynchronous interactions.
However, request-response can be implemented asynchronously, with a response being returned at some unknown later time but the request, response, and any other intermediate messages all carry the same correlation-id. This is something that can be controlled in the code. This is a “sync over async”, or “sync/async” pattern.