GLOCPP: Close Period with Warning R_CLPR0003: Unprocessed Records Exist in GL_INTERFACE
Last updated on MARCH 02, 2017
Applies to:Oracle General Ledger - Version 12.0.4 and later
Information in this document applies to any platform.
EXECUTABLE:GLLEZL - Journal Import
GLOCPP module: Periods - Close Period
When running the program GLOCPP Periods - Close Period it ends with a warning and the logfile shows the entry:
SHRD0008: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Warning ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
R_CLPR0003: Unprocessed records exist in GL_INTERFACE for period XXX-XX
The period is closed anyway, in spite of the warning. This is normal behavior.
The message can happen under the following circumstances :
- There are genuinely unprocessed rows in GL_INTERFACE table. In this case, the period can be reopened and the journal import executed again to import the unprocessed lines.
- There are no transactions in the GL_INTERFACE Table for the period in question. The program is displaying an incorrect message even when the GL_INTERFACE table has zero records.
- There are "Processed" transactions in the GL_INTERFACE Table which Journal Import has not deleted. The journals however are created in General Ledger.
The following scripts will show all the records with problems:
null, 'No Group Id',
'Has Group Id') group_id,
FROM gl_interface gli,
WHERE gli.user_je_source_name = js.user_je_source_name
AND (gli.user_je_source_name, gli.group_id) NOT IN
(SELECT gli.user_je_source_name, gli.group_id
FROM gl_interface gli
WHERE status != 'PROCESSED')
GROUP BY gli.user_je_source_name,
null, 'No Group Id',
'Has Group Id');
You will need to know the Ledger id and period name for this script:
select * from GL_INTERFACE
DECODE (ledger_id, (-1), set_of_books_id, ledger_id) = &LEDGERID
and period_name= '&period_name';
The sql used in GLOCCP includes a comparison between the accounting_date in the interface and the start and end date in the period, so the issue may occur if the accounting date is outside the start and end date that it has been placed in. This would only occur if the calendar had been changed but the gl_date_period_map had not.
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