My Oracle Support Banner

EAR 9.2: Payment Worksheet Will Not Allow 100% Write-Off From a Payment’s Amount After Patch 31668543 Is Implemented (Doc ID 2992133.1)

Last updated on DECEMBER 15, 2023

Applies to:

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

Symptoms

At the User Preferences level, within the Receivables Data Entry 2 set up page, the Write Off Percent fields for Payment Worksheet can only accommodate 2 digits, up to 99%:

    - Write Off Percent Under     (Record Field PS_OPR_DEF_TBL_AR.WO_PERCENT_UNDER)
    - Write Off Percent Over     (Record Field PS_OPR_DEF_TBL_AR.WO_PERCENT_OVER)

Before the solution delivered via <Bug 31668543> - (PAYMENT WORKSHEET - OVERPAYMENT WRITE OFF TOLERANCES NOT WORKING WHEN SET TO 0), included within PeopleSoft Enterprise FIN 9.2 PUM Image #38, Payments' Amount could be written-off at 100% of the original/remaining value.

Similar Write-Off Percent fields for Maintenance Worksheets do allow 100 percent value be defined in them, (3 digits).

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as System Administrator User
    2.- Navigate to:  Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences
    3.- Open the User ID desired
    4.- Click on the Receivables Data Entry 2 link
    5.- Confirm that the below Fields only accommodate up to 2 digits:
           a) Write Off Percent Under
           b) Write Off Percent Over

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the problem.

Since <Bug 31668543> is implemented, a Payment Worksheet will not allow the writing-off from the complete Payment's Amount.

FIN Receivables Users should be able to write-off the complete 100% of the Payment Amount, just like with Maintenance Worksheet write-offs. 

NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

 

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


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