My Oracle Support Banner

GLLEZL Concurrent Ends in Error With Requestor as "ANONYMOUS" (Doc ID 2726062.1)

Last updated on NOVEMBER 11, 2020

Applies to:

Oracle General Ledger - Version 12.1.3 and later
Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

GLLEZL (Import Journals) concurrent is triggered by GLLEZLSRS (Program - Import Journals).
When GLLEZLSRS is launched from GL Super User responsibility it completes successfully. The problem is that GLLEZL is not spawned from GLLEZLSRS.
GLLEZL is not run as standalone concurrent.
Under GL Super User responsibility only GLLEZLSRS can be seen as completed successfully.
The spawned GLLEZL concurrent and error can be seen only when logged with System Administrator responsibility. Here, when clicking to view the Parameters details of the errored GLLEZL concurrent, the Requestor is shown as 'ANONYMOUS'.

Note: From GL concurrent program "Import Journals'( gljirun.sql ) calls function fnd_request.submit_request for which Requestor is showed as 'ANONYMOUS'


ERROR: No log file exists for request xxxx. The concurrent manager may have encountered an error while attempting to create this file.
--------

Note: The error occurs for data imported from external sources.


STEPS to reproduce:
-------------------------
The issue can be reproduced at will with the following steps:
1. Go to General Ledger Superuser responsibility
2. Navigate to Requests > Run
3. Single request
4. Select ‘Program – Import Journals’ request
5. Fill in Parameters
6. Submit request

 

Changes

More than 5 DELTA patches applied in instance.

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.