Skip to main content
Question

Programmatically generating/serializing a saved search into FNDRR_CLIENT_PROFILE_VALUE

  • August 12, 2026
  • 0 replies
  • 12 views

Environment: IFS Apps 10

Background 

We have a set of saved searches on Site on Purchase Requisition, that filter by site cluster, e.g.:

contract IN (SELECT contract FROM &AO.site_cluster_node WHERE site_cluster_id = '<CLUSTER>')

These saved searches are stored on a shared base profile that all user profiles inherit from.

 

The business requirement is

When a new Site is added to basic data (Site Cluster), a custom event should fire a custom PL/SQL block which builds the site-relevant saved-search condition and writes it as a new record into the base profile — so the new site automatically appears in everyone's saved searches without manual profile edits.

 

What I've found so far

Saved searches are stored in FNDRR_CLIENT_PROFILE_VALUE as a CLOB, but the PL/SQL condition is not stored as readable text — it's held in profile_binary_value as a serialized/encoded string. This query fetches the relevant records:

SQL:

SELECT Fndrr_Client_Profile_Api.Get_Owner(t.profile_id) PROFILE_ID,
t.*,
t.profile_binary_value AS EncodedQuery
FROM FNDRR_CLIENT_PROFILE_VALUE t,
FNDRR_CLIENT_PROFILE_TAB s
WHERE t.profile_id = s.profile_id
AND profile_section LIKE 'User/Windows/Application Data/Search%'
AND profile_entry = 'CONDITION';

The question

The record insertion itself is straightforward. The hard part is the serialization — converting a plain text SQL condition into the encoded format, which is expected in profile_binary_value.

  1. Is there a supported/public API (e.g. under Fndrr_Client_Profile_API or similar) to generate the serialized profile value from a SQL condition, rather than reverse-engineering the binary format?
  2. If not, is directly reading/writing these serialized values considered supported, or is there a recommended alternative pattern for programmatically maintaining shared saved searches?
  3. Has anyone done this saved-search maintenance from a custom event this way — any pitfalls around the encoding, profile inheritance, or client caching?

Any pointers appreciated.

/BR
Buddhika Janith Hasthanayake