My Oracle Support Banner

EAR9.2: Customer Look Up in Aging Detail By Unit Rpt Is Using Wrong SetID When Customers Are not Shared. (Doc ID 1923236.1)

Last updated on MARCH 09, 2017

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Aging

ACTUAL BEHAVIOR
---------------
The customer look up in Aging Detail by Unit Rpt is using the wrong SetID.

EXPECTED BEHAVIOR
-----------------------
The customer look up in Aging Detail by Unit Rpt should be using the correct SetID.

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

  1. Record Group ID FS_23 (Customers) is linked to SetID SHR02 for Set Control Value US007.
  2. Record Group ID AR_02 (Aging) and AR_03 (Business Unit Options) is linked to SetID SHARE for Set Control Value US007.
  3. Navigate to Accounts Receivable > Receivables Analysis > Aging > Aging Detail by Unit Rpt and Add a new value.
  4. Enter SetID SHARE, Aging ID STD and business unit US007.
  5. Look Up customer ID and wrong SetID is used. SetID SHARE is used, this should be SetID SHR02.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot run the Aging Detail by Unit Rpt for specific customers.
We are using a shared SetID for Aging but each business unit has it’s unique customer SetID!

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
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.