Transaction register report shows data for all Operating Units when Reporting level is ledger. (Doc ID 2054992.1)

Last updated on JANUARY 09, 2017

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Reports Issues

ACTUAL BEHAVIOR
---------------
AR Transaction Register report not restricted by Ledger Access security, meaning when passed a Company segment range it lists out even though it doesn't belong to the Ledger parameter passed.

  a) Ignoring Ledger Security: The below variables that's getting initialized by "XLA_MO_REPORTING_API.Initialize" are removed from the where clause, which is implicating the control of the parameters "reporting_entity_id" and "Ledger ID" on the report as Null and Void.
  L_RECDIST_ORG_WHERE := XLA_MO_REPORTING_API.Get_Predicate('RECDIST',NULL);
  L_CT_ORG_WHERE := XLA_MO_REPORTING_API.Get_Predicate('CT',NULL);
  L_TRX_TYPE_ORG_WHERE := XLA_MO_REPORTING_API.Get_Predicate('TRX_TYPE',NULL);
  L_BILL_TO_ORG_WHERE := XLA_MO_REPORTING_API.Get_Predicate('BILL_TO',NULL);
  L_BS_ORG_WHERE := XLA_MO_REPORTING_API.Get_Predicate('BS',NULL);
 

EXPECTED BEHAVIOR
-----------------------
1) Report should list output based on given ledger parameter

2) Report should list output based on GL segments parameter

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Control > Requests > Run
2. Transaction Register

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get desired data from report.

Cause

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