The 'Tax Date' field in the GDF 'Additional Information for Poland' is not well validated: APP-JG-68128
(Doc ID 578832.1)
Last updated on MARCH 02, 2019
Applies to:Oracle Financials for EMEA - Version 18.104.22.168 to 22.214.171.124 [Release 11.5]
Information in this document applies to any platform.
FORM:APXINWKB.FMB - Invoice Workbench
Global Flexfield Definition: JG_AP_INVOICES
Value Set: FND_STANDARD_DATE
The 'tax date' in GDF field in the APXINWKB form it is validated only if it is placed as the last field in this form (by default, it is the last field).
If you change it's place to any other position, the validation does not occurs. Any valid date can be entered as an tax date.
Is there any validity check for the tax date to be entered within globalization flexfield for poland (GDF) within "Invoices entry" (APXINWKB) form when this GDF field is not the last field in the form ?
Also, when it validates, this validity is not accurate:
- Inserting a tax date in APXINWKB form, the tax date (global flexfield in APXINWKB for polish
localization), is not validated against the tax calendar but against value set FND_STANDARD_DATE (see global flexfield definition: JG_AP_INVOICES, context: JE.PL.APXINWKB.INVOICE_INFO )
Any valid date can be entered as an tax date.
As a result, invoices having a tax date which not matches a tax calendar period can be entered - this should not occur.
System validation message that shows up when inserting a not defined 'tax date':
"APP-JG-68128: Please either enter a date from a period that is defined in your VAT reporting calendar or extend your VAT reporting calendar to include this date".
Note 1: VAT reporting calendar = Tax calendar
Note 2: In spite of that message, APPS will accept any valid date no matter if it is inside the defined Tax calendar or not (!) This is a problem.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Go to Poland AP Responsability;
2. Nav.: Invoices / Entry / Invoices;
3. Insert an invoice entering a tax date in the Poland GDF that is valid but outside of your tax calendar (like 01.01.1900):
3.1. If this GDF it's the last column in this form, the following message will pop-up:
"APP-JG-68128: Please either enter a date from a period that is defined
in your VAT reporting calendar or extend your VAT reporting calendar to include this date"
3.2. if it's not the last column in the form, the message does not show up and you may save it.
Any date you want to insert outside the tax calendar it will not validated against the tax calendar but against value set FND_STANDARD_DATE.
So, any valid date can be entered as an tax date and that shouldn't happen.
Work with a folder that has the GDF defined as the last column of the invoices Header screen AND trust on Users that insert invoices that they are inserting a date that is defined as inside our defined (setup) Tax calendar.
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