GL - Unable To Set The Default Context On The LOOKUP Descriptive Flexfield
(Doc ID 2659347.1)
Last updated on MAY 21, 2020
Applies to:Oracle Fusion General Ledger Cloud Service - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Technology Management - Application Customization
GL - Unable to set the Default Context on the LOOKUP descriptive Flexfield
We are currently configuring our Descriptive Flexfields on the Common Lookup tables (lookup values descriptive flexfield) and are trying to automatically default the context based on the Lookup Name...
This functionality was available in EBS and allowed the automatic selection of the context so that the user could access the Context DFF immediately.
Note there is a Default Type and SQL section that implies the functionality is available in Fusion, though i am unsure what the syntax would like in my scenario.
Currently, the context segment does not default and requires manual selection before the ATTRIBUTE1 DFF (XXX Integration field) is available.
The expectation is that the Context Segment can be dynamic and consequently hidden so the user would see XXX integration as soon as the lookup "SRLC_XXX_LEDGERS" was selected.. Where a different lookup was selected (and no comparable context sensitive segment exists) no DFF would be displayed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document