My Oracle Support Banner

EAR 9.2: Negative Amount Direct Journal Payment Flagged by AR_EXCL_EDIT AE Program With 'Credits Do Not Equal Payment Amount' Error Message (Doc ID 3043617.1)

Last updated on OCTOBER 10, 2024

Applies to:

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

Symptoms

The Excel Edit Request process (AR_EXCL_EDIT AE Program) incorrectly flags in Error an interfaced Deposit when using the new ExcelUploadforDirectJournalDeposits.xlsm spreadsheet file, should it contain a negative amount Direct Journal Payment transaction, stating that the Credit Amount does not equal to the expected Payment Amount at the Accounting Distribution Lines level.

REPLICATION STEPS:

    1.- Ensure that the FSCM Online Application environment used is at PeopleSoft Enterprise FSCM 9.2 PUM Image #49, or has at least <Bug 35596820> - (ENH: RECEIVABLES 9.2 DJ EXCEL UPLOAD) applied
    2.- Enable all PeopleTools Integration Broker configuration for Direct Journal Payments upload via Excel functionality
    3.- Obtain the latest version of the ExcelUploadforDirectJournalDeposits.xlsm spreadsheet file
    4.- Open the Excel spreadsheet, and fill in the details for a Deposit, containing a Payment transaction marked as Direct Journal, all with a negative amount value of -1,000.00 USD
    5.- On the same Excel file, in the section for Accounting Details, define the User Distribution Line, with an amount of 1,000.00 USD (positive amount, as it must be reverse sign), with any needed accounting ChartField values
    6.- Proceed to save the XLS spreadsheet file
    7.- Click on the 'Generate XML and Post' button
    8.- Fill in the login credentials, URL Address, and Local Node
    9.- Complete the interface, and receive the message that the system imported a direct journal deposit
    10.- Log into the FSCM Online Application as a Receivables User
    11.- Navigate to: Accounts Receivable > Payments > Electronic Payments > Excel Edit Request
    12.- Create a new Run Control ID for the Deposit Unit, and User ID values, and proceed to launch the AR_EXCL_EDIT AE Program
    13.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
    14.- Review the Message Log from the AR_EXCL_EDIT AE Program process instance, and confirm that it has flagged with errors one Excel Deposit
    15.- Navigate to: Accounts Receivable > Payments > Electronic Payments > Excel Error Correction
    16.- Find the Deposit ID flagged in Error, and click on its link
    17.- PROBLEM: At the Excel Upload Error Correction page, confirm that the system has stored an Error Message against the Direct Journal Payment accounting
    18.- Click on the 'Direct Journal Acctg Entries' link
    19.- Confirm that the User Distribution line has a positive amount of 1,000.00 USD, while the Cash AR line has a negative amount of -1,000.00 USD, which is properly balanced

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.

ERROR MESSAGE:

" Credits do not equal the payment amount. "


Those interfaced Deposits, and their Direct Journal Payment transactions containing negative amounts, cannot be corrected online, nor be further processed into the FIN Receivables module. The new ExcelUploadforDirectJournalDeposits.xlsm spreadsheet cannot be used for such transactions.

Negative amount Direct Journal Payments can be manually entered online in the Application, and its Accounting Entries can be automatically generated, and properly balanced with no problems. The same functionality is expected if the Regular Deposit and Direct Journal Payment transaction is interfaced using the new ExcelUploadforDirectJournalDeposits.xlsm spreadsheet file delivered in FSCM 9.2 PUM Image #49.

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.