My Oracle Support Banner

GST: TDS Section Code is not defaulting based on Natural Account and Section code mapping setup in case of PO matched invoices (Doc ID 2607493.1)

Last updated on NOVEMBER 04, 2019

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
TDS Section Code is not defaulting based on Natural Account and Section code mapping setup in case of PO matched invoices.

EXPECTED BEHAVIOR
-----------------------
TDS Section Code should be defaulted based on Natural Account and Section code mapping setups.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Created PO with 2-way matching and invoice match option as 'PO'.
2. Enter PO charge account.
3. Ensure that Accrue at Receipt flag is set to N.
4. Created AP invoice and matched it with PO.
5. Noticed that TDS section code did not default based on Natural Account Section Code mapping.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot determine the correct TDS liability.

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.