Pluggable Mappings and Input Parameters

Question

Hi All,
I have a mapping which receives 2 input parameters. I have created a pluggable mapping to which I would like to pass those same values. Is is possible to pass parameter values into a pluggable mapping such that these values are NOT part of the input signature?
thanks
Ok, I have more information. When I deploy my mapping, I found the following code commented out of the main procedure:
-- register custom input parameters:
-- Temp fix until selective registration ensures correct handling of complex types
-- wb_rt_mapaudit_util.register_custom_param(x_audit_id,
-- '"MY_PARAM"',
-- TO_CHAR("MY_PARAM"));
What is the "selective registration" that they mention and how do I do it?
thanks, again
Edited by: philip_b on Mar 26, 2010 8:39 AM

Answer 1

Thanks for responding David. I am using Client: 10.2.0.1.31 and Repo: 10.2.0.1.0
I was hoping I didn't have to include it in the signature because I didn't want these values to be part of the incoming dataset; that just complicates the mapping logic for me.
It would make sense to me that the pluggable mapping should have access to the parent mapping's parameter values.
Why is the parameter registration code commented out inside the generated package? Do you know what it is referring to when it mentions "selective registration"? I can't find any reference to it:-/
Someone else had the same issue last year on the following thread, but there were no responses to the issue:
wb_rt_mapaudit_util register_custom_param call commented out in gen'd sql