Last updated on OCTOBER 25, 2016
Applies to:Oracle Internet Expenses - Version 12.1.3 and later
Information in this document applies to any platform.
Expense Location Field LOV
After applying RPC4 patches the functionality of the LOV changed for Location when entering Tax Merchant fields for VAT tax related expenses.
Prior to patching the LOV for Location showed just those locations enabled for merchant tax fields.
After patching the Expense locations now show all locations instead of just those enabled for merchant tax fields.
NOTE: To be confirmed which were applied:
, '14098047','R12.1.3 OIE-RPC Aug 2012'
, '13563489','R12.1.3 PCARD-RPC Jan 2012'
, '16234880','R12.1.3 OIE-RPC Mar 2013'
, '16213660','R12.1.3 PCARD-RPC Mar 2013'
, '17176060','R12.1.3 PCARD-RPC Sep 2013'
, '19163626','R12.1.3 OIE-RPC Aug 2014'
, '19018819','R12.1.3 PCARD-RPC Aug 2014'
, '20315551','R12.1.3 OIE-RPC Feb 2015'
, '20178726','R12.1.3 PCARD-RPC Feb 2015'
, '22526147','R12.1.3 OIE-RPC Feb 2016'
This contradicts the intended behavior of the LOV, which is (per both the Implementation Guide and unpublished through Bug 10329388 : THE LOCATIONS ARE NOT SHOWING UP IF TAX LOCATIOIN IS NOT DEFINED FOR THE COUNTRY) as follows:
Generally a location is assigned to a policy schedule and the user can select
the location in the details page when the user selects the expense type that
has the policy schedule attached.
Text from implementation guide:
If there is no schedule assigned, or if the assigned schedule is not
location-based, then these pages display location fields for text entry only.
If the assigned schedule is location-based, or if you have merchant fields
enabled, then Internet Expenses displays location fields with a list of values."
Expect the LOV for Location to behave in the same manner that it did before patching.
The issue can be reproduced at will with the following steps:
1. Have locations enabled but *NO* schedule defined for Policy
2. Have an expense type defined that has VAT merchant tax fields enabled including Location, again with no Policy/schedule defined
3. Enter an expense report and see that the LOV for Location only displayed VAT enabled locations.
4. Apply patch(es) XX
5. Retest the issue and see that the LOV now contains all locations not just VAT enabled locations.
6. Review the file versions and code, see the following changes were made:
Before RPC4 Patch:
LocationsVOImpl.java 120.9.12010000.10 LocationsVORowImpl.java 120.1
After RPC4 Patch:
LocationsVOImpl.java 120.9.12010000.11 LocationsVORowImpl.java 120.1
The following SQL in the view has changed:
FROM ap_web_vat_setup vat_setup
WHERE vat_setup.enabled_code = 'Y'
) ) )
The prior view had this sql where it also joined the territory code:
SELECT locations.location location,
FROM fnd_territories_vl territories,
WHERE 'Y' = :6
AND vat_setup.territory_code = locations.territory_code
AND vat_setup.enabled_code = 'Y'
AND locations.territory_code = territories.territory_code
AND locations.status = 'ACTIVE'
AND TRUNC(sysdate) <= TRUNC(NVL(locations.end_date + :7, sysdate))
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