Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

General Ledger - EBS (MOSC)

GLLDEL "Program - Delete Journal Import Data" Is Not Deleting Records From GL_Interface

Oct 8, 2018 6:39AM edited Nov 1, 2018 5:10AM in General Ledger - EBS (MOSC) 1 commentAnswered

Hi,

I have a customer using R12.1.3, they have RPC3 and RPC5 applied.

They have a load of old data in the GL Interface table, for a range of sources - none of it is from the sub-ledgers.

They are trying to delete data from the interface using the "Program - Delete Journal Import Data" job.

This is what we know:

The REQUEST_ID and GROUP_ID values for the relevant data on the GL Interface are populated.
The Journal Source is not frozen
When submitting the delete job, the Request ID and Group ID parameters are populated.
The responsibility is linked to a Data Access Set which has full read and write access to the same Ledger on the GL interface which the user wants to delete.

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month