R12: Drilldown to Subledger Transactions Not Working in a Specific Responsibility (Doc ID 1589646.1)

Last updated on NOVEMBER 13, 2023

Applies to:

Symptoms

Drilldown functionality is not the same across different responsibilities where the same profile option values were set up in both responsibilities.

Example:

User has 2 responsibilities:
1) Custom responsibility created by user.
2) Standard General Ledger Super User responsibility.

Profile Options:
=============
1) MO:Operating unit 
2) MO:Security profile 
3) SLA: Enable Subledger Transaction Security 
4) GL: Data Access Set
5) SLA: Enable Data Access Set Security in Subledger
6) SLA: Additional Data Access Set 

The above profile option setups are identical for both the custom responsibility and standard responsibility.

The issue can be reproduced at will with the following steps:

1) User navigates to each of the 2 responsibilities .
2) Inquiry --> Account
3) Query for the journal batch
4) Click on Drilldown
5) OAF page opens up.
6) Clicking on the 'View Transaction'.

When attempting to drill down, the OAF Page is displayed. However, upon clicking 'View Transaction,' the expectation is for the control to shift to the subledger form to display the Payables invoice.

The control successfully navigates to the subledger when drilling down from the General Ledger Super User responsibility. Nevertheless, when attempting the same action through a custom responsibility, clicking on 'View Transaction' has no effect. The control remains on the current page and fails to transition to the subledger form.

Changes

Upgrade to R12.1.3

Cause

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