EAR9.0+: Direct Journal Payment Account Prompt Showing Incorrect SetID (Doc ID 2102560.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

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

Symptoms

On : 9 version, Direct Journal

ACTUAL BEHAVIOR
---------------
Direct Journal payment account prompt is showing incorrect SetID.

EXPECTED BEHAVIOR
-----------------------
Direct Journal payment account prompt should be showing correct SetID.

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

  1. FS_05 is linked to SetID SHARE where Set Control Value is US001 and FS_05 is linked to SetID SPN01 where Set Control Value is SPN01.
  2. Account 620000 exists for both SetID SHARE and SPN01.
  3. Bank USBNK and accout CHCK is linked to GL Unit US001.
  4. AR business unit US001 is linked to GL business unit US001 and AR business unit SPN01 is linked to GL business unit SPN01.
  5. Create a regular deposit for business unit US001, Bank Code USBNK and Bank Account CHCK. Select ‘Journal Directly’ and save deposit.
  6. Navigate to Accounts Receivable > Payments > Direct Journal Payments > Create Accounting Entries.
  7. Change GL Unit to SPN01 and account to 620000.
  8. Do NOT save changes. Look Up Account, SetID is SPN01. This is correct.
  9. Save changes.
  10. Use Look Up Account again, this time SetID is SHARE. This is wrong!


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are able to enter an invalid account for direct journal payments.

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