Data Conversion Defaulting Vat_Item.Vat_Code From Vat_Deps
(Doc ID 3018812.1)
Last updated on MAY 01, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Data Conversion adding Standard VAT record for Zero VAT Items
When converting/loading some Items which have (only) Zero VAT:
- DCT is loading to the VAT_ITEM the record from the "VAT_ITEM.dat" file with the Zero VAT, as expected;
- However, it is also adding a new record (not in the "VAT_ITEM.dat" file) in the VAT_ITEM table with the Standard VAT and with Active Date as the loading date - this additional record is not expected.
This is based on the information on the VAT_DEPS table, which has a default for newly created Items to add a Standard VAT record for this particular Department, these additional records are being loaded when loading the DC_ITEM files (and the VAT_ITEM file is only loaded later).
EXPECTED BEHAVIOR
-----------------------
This is a problem, as these Items should have Zero VAT; and end up having the Standard VAT, which is not correct.
STEPS
-----------------------
The issue can be displayed the following steps:
Load the DC_ITEM data entity with success using the Data Conversion application.
The items (ITEM_MASTER.ITEM_LEVEL <= ITEM_MASTER.TRAN_LEVEL) were loaded to the ITEM_MASTER table
The problem is that, for those items loaded to the ITEM_MASTER table, some records were also automatically loaded to the VAT_ITEM (with VAT_ITEM.ACTIVE_DATE = VDATE), although the VAT_ITEM file was yet to be loaded:
These additional VAT_ITEM records seem to be based on the VAT_DEPS table for the Items department, which have created an additional ITEM_VAT table with the item and the respective VAT_DEPS.VAT_CODE for the ITEM department:
This is a problem, as these migrated Items should have Zero VAT (which is what we have on the VAT_ITEM file we’re loading/migrating); and end up having the Standard VAT (due to these additional records loaded automatically based on VAT_DEPS), which is not correct.
The VAT_ITEM file is then loaded for the same set of items:
And this is the result for one of the Items just as an example:
There is a record with Zero VAT rate, which was loaded from the VAT_ITEM data conversion file, and has the original Active Date;
There is also an additional record for Standard VAT (“S_UK”), which was automatically added by the Data Conversion application, which has the Active Date when Data Conversion was run.
This last record is a problem, as this Item should have Zero VAT; and end up having the Standard VAT, which is not correct.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |