Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Merchandising System - Version 13.1 and later
Information in this document applies to any platform.
Batch process vatdlxpl incorrectly changes the active VAT_CODE if a VAT_RATE change is done for another VAT_CODE which was active in the past for the item.
Steps to reproduce:
1. Create an item with current VAT_CODE as 'C', for a specific Value Added Tax (VAT) region/VAT type combination.
2. The item should be associated with VAT code 'S' in the past and future.
3. Go to Control -> setup -> VAT code maintenance -> Edit -> Rates .
Add a new VAT rate for the VAT_CODE 'S' with active date as VDATE+1.
4. Run the vatdlxpl batch on VDATE.
Expected result: No new row should be inserted with (VDATE+1) in VAT_ITEM table for that item/VAT region/VAT code/VAT type combination since it is associated with a different VAT code('C') currently.
Also, update should not happen for the those future entries in VAT_ITEM table with VAT code 'S' , if there exists a different VAT rate in VAT_CODE_RATES table for that future period.
Actual result: The above mentioned insert and update are done by the batch.
User scheduled a VAT rate change for VAT_CODE 'A' from 17.5% to 20%, for 04th Jan 2011.
For the item x, current active VAT_CODE was 'L' (5%).
Since item x had a VAT_CODE = 'A' in the past, the vatdlxpl batch is inserting a record for VAT_CODE = 'A' for item x even though there is no change in the VAT_RATE/VAT_CODE for the item x.
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