Graphical Mapper - Parameterised Stored Procedure or Function call in Select Where Clause - Oracle DB

Kindly refer the PMR (31762,999,796) for more detailed coversations related to the issue which isn't *documented* in IBM information center at the moment.

This RFE is a request to get this documented, the UseCase / Scenario in which 'Oracle Parameterized Packaged Stored Procedure/Function is written in the 'Where' clause of SELECT statement, using Graphical Mapper' in IIBv10 and WMBv8.

In WMBv8, Applications were designed/implemented to call Oracle tables/views with Packaged Parameterized Function in its where clause, have been working properly with no issues. It seems, it doesn't call function in the where clause, whereas it passes that select/where clause to Oracle to handle it at runtime. It appears IBM doesn't have a use case for this scenario, with where clause function (with parameters), which gets evaluated and Oracle database handles it at the runtime.
As far as IIBv10FP009 is concerned, the same behaviour works fine too. The only difference we have found out is that the graphical mapper has more validations in syntax while formulating call to oracle table/view with function in where clause. Fixing the expected blank space issues in the passed parameters of the called function, resolves the xpath issue. It appears, xpath errors were the false errors and more of related to syntactical and validation issues, set at toolkit level, on the graphical mapper. Hence, IBM can document this use case somewhere for the future references.

Following is the response from IBM in the aforementioned PMR:

I believe the map has modified to make these SQL Select Where clauses like 1=cdm_product_conversion.set_ret_main_bft( ? , ?1 , ?2 ) That is adding the space character after each parameter place holder, as would be done when using drag drop action in the SQL clause builder from the "available inputs for column values". The validation issue arises because the comma character used to separate the Oracle function call parameters is not an expected SQL syntax character, and the product requires a occurrence of a whitespace character triggers our validation to recognise each separate placeholder. Note that when editing the Mapping Select Where clause the user is promoted and cannot click "OK" until the syntax is valid. For IBM to document the use case of including an Oracle function call in a Mapping Select Where clause would require that full testing of the feature be added to the product release process in addition to updating the documentation to detail its use.
If the customer wishes this we would suggest that an RFE is raised.