Transaction Workbench Issue: How To Restrict Tax Classification Code By Operating Unit?
Last updated on AUGUST 31, 2017
Applies to:Oracle Receivables - Version 12.1.1 to 12.1.3 [Release 12.1]
Oracle E-Business Tax - Version 12.2.4 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.
In Transactions Workbench, what are the setups required to Restrict Tax Classification Code By Operating Unit when there are multiple operating units used in a single instance?
Currently, the Tax Classification Code List of Values (LOV) shows all the tax rates which are created:
1) specific for the Operating Unit as configuration owner for which you are entering the transaction and
2) for all others created under 'Global Configuration Owner' as configuration owner
You only want to see 1) which are specific for the operating unit you are processing in.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms