My Oracle Support Banner

OPSFi Standing Charges: Syncronize Standing Charges with Purge = Y - Transactions remain Trapped In Interface RA_INTERFACE_ALL (Doc ID 2396564.1)

Last updated on JULY 04, 2023

Applies to:

Oracle Public Sector Financials (International) - Version 12.1.3 and later
Information in this document applies to any platform.


User entered incorrect date as parameter to Run Date when running Standing Charges: Generate Interface Data.

All invoices with a next due date in the future were generated and are sitting in the interface tables.

Is there any way of reversing this action to allow the invoices to generate at the proper time, and not leave them in the interface tables?



 1) Run job with date typo, so generate a year's worth of invoices from
PERIODICS into the ra_interface_lines_all table.

2) Run AutoInvoice, which generates invoices in the open GL Period, and
errors for all the others as the GL Period is closed.

3) Run Synchronize Standing Charges with Purge set to Y for the date of the original run

   Almost all the invoice data is cleared from the interface table.

The remaining invoices in ra_interface_lines_all are for standing charges
that have been marked Closed since the original run.  They can't be in the
interface table and have invoices created as well.

The issue is the Synchronize process - it is not deleting the interface lines
that match with Closed Standing Charges.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.