My Oracle Support Banner

Portuguese Annual VAT Report (JEPTAVAT) Ignores the 'Location Code' input parameter: All data is retrieved always. (Doc ID 1560043.1)

Last updated on MARCH 16, 2020

Applies to:

Oracle Financials for EMEA - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.

Symptoms

On : 11.5.10.2 version, Portugal Localizations for GL

ACTUAL BEHAVIOR
---------------
Portuguese Annual VAT Report (JEPTAVAT), when ran for the islands (Location parameter 'M' or 'A') , is picking values related to transactions done using VAT codes setup with Global_attribute1 (location) on the Additional Information for Portugal value ‘C’ instead of picking up values which have global_attribute1(location) setup as ‘A’ or ‘M’.

EXPECTED BEHAVIOR
-----------------------
From AP it seems to be picking the correct tax data. The issue seems to be related with journals with Tax data directly inserted on GL.
Running JEPTAVAT For 'M' customer doesn't expect to be caught 'C' or 'A' location journals
Running JEPTAVAT For 'A' customer doesn't expect to be caught 'C' or 'M' journals
Running JEPTAVAT For 'C' customer doesn't expect to be caught 'M' or 'A' journals


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Running JEPTAVAT For 'M' customer doesn't expect to be caught 'C' or 'A' location journals
2. Running JEPTAVAT For 'A' customer doesn't expect to be caught 'C' or 'M' journals
3. Running JEPTAVAT For 'C' customer doesn't expect to be caught 'M' or 'A' journals



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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.