For an inbound Application Message carrying binary data (like a PDF), documentation describes the framework wrapping the file as Base64-encoded content inside a BIN_DATA element under a BINARY_PARAMETER XML wrapper, with the receiving PL/SQL method's input therefore expected to be that XML. In practice, though, a test PL/SQL function that simply returns its input clob unchanged ends up producing the raw file itself as the message response, not XML. Is this a documentation error?

All FAQ questions / Integrations and APIs

Answer

No — the documentation and the actual behavior are both correct; the apparent contradiction comes from what happens on the way OUT rather than the way in. The input truly is the XML-wrapped BINARY_PARAMETER/BIN_DATA structure as documented. But when the response message returned by your PL/SQL method itself contains that same BINARY_PARAMETER/BIN_DATA element structure, the framework automatically detects it and extracts the embedded binary content, returning the raw file itself as the actual output rather than the XML wrapper — so a function that simply echoes its XML input back out ends up producing the raw file as its visible response, purely because of this automatic unwrapping behavior on the response side, not because the input itself wasn't genuinely XML.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions