Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Filter Value Set based on Page Item Reference

769246Oct 11 2010 — edited Oct 12 2010
I need to use the account number from the customer account site page to populate a table validation value set that is attached to the dff on the customer account site page.

I have found several requests on how to do this but no solution. I have tried to create a flex map via the page personalization setting the "Reference Value" to ${oa.page.acctnum}, and setting "Name" to CUSTOMER_NUMBER, then using this syntax of the table where clause of the value set:

"customer_number = :$PROFILES$.CUSTOMER_NUMBER"

We have a large migration from 11i to R12 & many of our DFF validation, value sets are done this way, and we must correct them. I need the missing link on how to correct these.

We have associated a LOV to the DFF on the Customer Account Site form in 11.5.10. The value set used to populate the LOV references the CUST.CUSTOMER_NUMBER on the form. This is making a reference the CUSTOMER_NUMBER on the CUST block of the form. Apparently, this was only available in 11i for backwards compatibility and is not longer allowed in R12. As a result, after the upgrade, when we try to open the Customer Account Site form we get the following error: "No field listener is registered to resolve field CUST.CUSTOMER_NUMBER referenced by the flexfield with application short name AR and the name RA_ADDRESSES_HZ. Please contact your system administrator." We researched this on Metalink and found the following note:

QUOTE
ACTION PLAN
*===========*
It appears that you are using a BLOCK:FIELD definition in a flexfield - this is not supported in Oracle Framework In Flexfield manual for the bind variable :block.field, there is a warning that states the following: "The :block.field mechanism is present for backward comparibility only. Value sets that use this mechanism will not be compatible with a future release of Oracle Applications....." At the present time, there is no workaround for using :block.field in Oracle Application Framework architecture. Please can you review your defined flexfield structures and where there is a BLOCK:field design please ensure this is not used.
END QUOTE

Thanks
Sue
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Nov 9 2010
Added on Oct 11 2010
4 comments
622 views