My Oracle Support Banner

EBI 9.2: The India GST E-Invoice Process (BI_GST_EINV AE Program) Generates Duplicate Transaction Rows Into CSV File if Same Bank Code and Bank Account Combination Defined Under Different Set IDs (Doc ID 2740660.1)

Last updated on JANUARY 25, 2021

Applies to:

PeopleSoft Enterprise SCM Billing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms


It has been detected that the India GST E-Invoice Process (BI_GST_EINV AE Program) will generate duplicate Transaction Rows for the same GST enabled Billing Invoice into the CSV File output. There will be as many duplicate rows as combinations of the same Bank Code and Bank Account are defined under different Set ID values.

The Invoice Header stores the values of the Bank Code (Record Field PS_BI_HDR.BANK_CD), and Bank Account (Record Field PS_BI_HDR.BANK_ACCT_KEY) to be used in this transaction. However, the India GST E-Invoice Process (BI_GST_EINV AE Program) does not seem to look into the TableSet Control functionality for the Billing Business Unit (Record Group FS_39 - Banks), and as such, is not considering the Set ID field value. As a result, the process will add as many duplicate rows as the same combination of Bank Code and Bank Account exist under different Set IDs.

REPLICATION STEPS:

  1.- Define the same combination of Bank Code (INBNK) and Bank Account (CHCK) under different Set ID values (Example: SHARE, SHR02, and INDIA)
  2.- At the TableSet Control level, for Set ID IND01, ensure that Record Group FS_39 (Banks) is pointing to Set ID SHARE
  3.- Enable GST E-Invoicing functionality into Billing Business Unit IND01
  4.- Configure Customer ID IND05 to support the applicability of India GST E-Invoice
  5.- Create a new Billing Invoice under Business Unit IND01, and Customer ID IND05, using Bank Code (INBNK) and Bank Account (CHCK)
  6.- Set the Invoice into a Ready status
  7.- Launch the BIJOB41 PSJob process against the newly created Invoice
  8.- Launch the India GST E-Invoice Process (BI_GST_EINV AE Program)
  9.- Confirm the CSV file is generated, but instead of having one single Transaction Row for the Invoice at hand, find 3 duplicate rows instead

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

The CSV file generated by the India GST E-Invoice Process (BI_GST_EINV AE Program) cannot be sent out to the Indian Tax Authorities because it contains incorrect duplicate rows. Manual correction is needed, but prone to User's mistakes.

The India GST E-Invoice Process (BI_GST_EINV AE Program) should invoke the configuration under which Set ID is being used (Record Group FS_39 - Banks) for the Bank Code and Bank Account defined at the Invoice level, and generate a unique Transaction Row into the CSV file.

NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

 

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
Changes
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.