India : Service Tax Processing Populates Wrong Curr_conv_date In JAI_RGM_TRX_RECORDS table (Doc ID 2116824.1)

Last updated on MARCH 15, 2016

Applies to:

Oracle Financials for India - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Service Tax - P2P

ACTUAL BEHAVIOR
---------------
India -Service Tax Processing program is populating incorrect curr_conv_date in JAI_RGM_TRX_RECORDS

Currency conversion Date is picked up from Invoice Date instead of GL Date.
This is causing the settlement amount to be incorrect.

EXPECTED BEHAVIOR
-----------------------
Currency conversion Date should be picked up from GL Date.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Responsibility: Oracle Payables - India localization
Production and Test instances

2. Path: Invoices -> Entry -> Invoices
3. Create an invoice with USD currency with Invoice Date as 01-OCT-2015 and GL Date as 03-MAR-2016
4. Apply service Tax with reverse charge which includes basic service tax and swachh bharat cess
5. Validate the invoice and Create Accounting.

6. Path: Other -> Requests -> Run
7. Run the India - Service Tax Processing (JAISRVTP) with date range from 01-OCT-15 till 03-Mar-2016

India - Service Tax Processing is populating an incorrect curr_conv_date in JAI_RGM_TRX_RECORDS table.

The JAI_RGM_TRX_RECORDS table has curr_conv_date populated as 01-OCT-15 instead of 03-MAR-16.

Currency conversion Date is picked up from Invoice Date instead of GL Date.
This is causing the settlement amount to be incorrect.

The issue can be reproduced at will.

8. Note

The problem started after applying patch 22626281 (as requested in SR 3-12086638431 to solve an issue for SBC Tax).
This patch updated the following files:

jai_cmn_reverse_charge_pkg.plb 120.0.12010000.36
jai_cmn_rgm_rec.plb 120.14.12010000.44

Prior to this patch, the file versions in production were:

jai_cmn_reverse_charge_pkg.plb 120.0.12010000.33
jai_cmn_rgm_rec.plb 120.14.12010000.41

Uploaded the screen-shots of the comparison and the piece of code in 36 version that is causing the issue.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the settlement amount is incorrect.

Unable to do settlement and make payment to authorities by tomorrow.
There will be a huge penalty from Govt. in case of delay in payment.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms