Hi Irfan,
I assumed that your resource endpoint would be updated with the following XML payload.
<root>
<reqid-lac1>0001</reqid-lac1>
<source-lac1>mfa</source-lac1>
<inward>1119099</inward>
</root>
Its JSON expression is:
{
"reqid-lac1" : "0001",
"source-lac1" : "mfa",
"inward" : "1119099"
}
The APIs created by LAC accept both types of payload at the same URI by specifying the Content-Type as "application/xml" or "application/json".
They both are passed to Request Event Handlers in JSON format before the actual resource endpoint is invoked. If you send the following XML body to your resource endpoint:
<root>
<reqid>00001</reqid>
<source>mfa</source>
<inward>11119099</inward>
</root>
It is passed to Event Handlers as a JSON string like this:
{
"reqid": "00001",
"source": "mfa",
"inward": "11119099"
}
XML to JSON conversion is automatically done by LAC in the very early stage, so I think JSON to JSON transformation is necessary in a Request Event Handler (javascript code) of your resource endpoint.
Request Event Handlers work as "filters" for Resources and Functions, so it is enough to put the reformatted JSON string back to the "json" variable.

I found an example about "Reformat Request" was included in the Web UI of LAC 5.0.

Best regards,
Seiji