Enabling Translations for Existing Non-Translatable DFF/EFF Value Sets in Oracle Fusion
Hello Everyone, We have a client that has been using Oracle Fusion for several years, during which a significant number of DFFs (Descriptive Flexfields) and EFFs (Extensible Flexfields) have been configured across various modules.
The client is now planning to enable the Japanese language for their local users. However, we've encountered a challenge: Translation is enabled at Attribute Group level not value set, which prevents us from adding Japanese translations to the existing lookup values.
Has anyone encountered a similar situation in an existing Oracle Fusion implementation?
We're interested in understanding:
•What approaches or workarounds have you used to address this requirement?
Tagged:
0