EAP: GST Transaction Loader Process Either Fails with Unique Constraint Error at LC_GSTLOAD.INS_AP.Step01 (SQL) Or Load Excise/ Sales Tax Data
(Doc ID 2440252.1)
Last updated on MAY 23, 2019
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When there are 2 vouchers with same voucher id but different business units are present in PS_VCHR_LN_EXS_DTL and Transaction Loader is executed for only one BU, then it is picking up the data of other BU as well. This results in either Unique Constraint Error or picking up of Excise / Sales Tax data.
1) Create 2 Vouchers for 2 different India Tax applicable BU's such that both Voucher Ids are same.
2) Post the Vouchers.
3) Run GST Transaction Loader process for one GL BU.
GST data should be loaded only for one voucher.
a) If Excise / Sales Tax is applicable for one Voucher and GST is applicable for another - it results in Excise / Sales Tax row being picked up.
b) If India GST is applicable for both Vouchers - it results in Unique Constraint Error.
-- 03:01:33.966 Process 164619 ABENDED at Step LC_GSTLOAD.INS_AP.Step01 (Action SQL) -- RC = 805
-- 03:01:34.030 SQL Error: ORA-00001: unique constraint (EMDBO.PS_GST_TXN_TAOx) violated
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