Transaction Workbench Issue: How Can the Additional Information DFF For Global Countries Be Turned Off?
Last updated on JUNE 01, 2016
Applies to:Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.
How can the Global Descriptive Flexfield (DFF) in the transaction form be removed for a given country?
Controlling the globalization features has changed in R12 due to the Multi-Org Access (MOAC) features.
In R12, the globalization enabling/disabling functionality is differed for Org based products like AP, AR and PO and non-org based products like FA and GL. For org-based products, it will be based on org_id value. The internal code logic derives the country code for the given org from the LE setup. (Org ID -> Legal Entity > Country). If the derived country is a JX country, then Globalization Code will get fired. Due to this, there is no control for the user to stop Globalization code execution. For Non-Org Based products like FA and GL, Globalization code still works in the same way that it was in 11i based on JG profiles.
The logic in R12 to disable a DFF for globalization was changed in <Bug 8872063> RECEIVE THE ERROR APP-JL-62181 IN AR SYSTEM OPTIONS
The following text is lifted from the bug:
A new lookup named "JG_DISABLE_GLOBALIZATION" was added in the applications. Customer has to provide the country codes as lookup code for this new lookup type to disable the globalization feature for those countries.
After setting the lookup, the following profiles values need to be reset to NULL to disable the globalization features completely for the country:
- JG: Territory
- JG: Applications
- JG: Product
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms