My Oracle Support Banner

EAR 9.2: ExcelUploadForDeposits.xlsm Spreadsheet Throws Misleading Message on Imported Deposits in ARdepositlog.xlsx File when Deposit ID Exceeds 15 Characters (Doc ID 2665625.1)

Last updated on JUNE 08, 2021

Applies to:

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


In Application Designer it is defined that the delivered Field DEPOSIT_ID can only accommodate up to 15 characters, which is rightfully enforced when creating a new Regular Deposit online

However, when using the ExcelUploadforDeposits.xlsm feature to interface Deposit and Payment transaction data from the Excel Spreadsheet into the PeopleSoft Records, Users are able to enter any value in the DEPOSIT_ID column, with no limits. As such, should the User enter a Deposit ID value of more than 15 characters, the system is designed to cut that value, and drop any characters after position 15th.

Following this behavior, a problem has been detected with the ARdepositlog.xls file issuing incorrect messages stating the number of Deposit transactions successfully interfaced into the EXCEL Records within PeopleSoft, specially if multiple Deposit transactions are to be interfaced, with Deposit ID values very similar, that only start differing on character position 16 or onward. As the interface cuts the Deposit ID value to 15 characters, only the first transaction goes through, while all others are ignored. Nonetheless, the messages at the Excel spreadsheet level, as well as in the ARdepositlog.xls file indicate that all transactions were properly interfaced.


    1.- Ensure to enable all the needed configuration for Deposit Excel Upload functionality
    2.- Open the ExcelUploadforDeposits.xlsm Excel file, and add three new Deposit ID rows, each with its own Payment, Customer, and Item information
    3.- Ensure that under the DEPOSIT_ID column the values used are: (All have 16 characters, with only a difference in 16th position)
         a) DEPOSITNUMBER001
         b) DEPOSITNUMBER002
         c) DEPOSITNUMBER003
    4.- Proceed to click on the 'Generate XML and Post' button
    5.- Define the log in credentials to the target environment, and press OK button
    6.- Save the XML file into a specific location
    7.- The system throws a new message: " The XML data file created successfully, uploading file to data base "
    8.- ISSUE: The next message has a misleading statement saying " Imported 3 deposits "
    9.- Click OK button
    10.- On the ARdepositlog.xls file, the Log Message also states that 3 deposits were successfully interfaced
    11.- Query the Excel related staging tables within PeopleSoft (see below), and confirm only one single Deposit transaction is present, that of Deposit ID DEPOSITNUMBER00 and its first Payment.
         a) PS_DEPOSIT_EXCEL
         b) PS_PAYMENT_EXCEL
         c) PS_ID_CUST_EXCEL
         d) PS_ID_ITEM_EXCEL

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 issue.

The Users loading data manually into the ExcelUploadforDeposits.xlsm assume that all 3 Deposit transactions and their respective Payments were successfully stored into PeopleSoft tables, but the truth is that only one transaction made it. The ARdepositlog.xls file also contains misleading information, and Users are only able to find one transaction online, not knowing what happened to the other two. Integration Broker Asynchronous Services can no longer be reviewed for any potential issues.

Upon entering the data manually into the ExcelUploadforDeposit.xlsm spreadsheet, and before interfacing the transactions into PeopleSoft, the Excel file should have validations, and issue an Error Message stating that DEPOSIT_ID Field contained a longer value than expected. Or have ARdepositlog.xls file to contain in its Log Message the information stating that only one Deposit was interfaced, and other 2 went into Error.


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.




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

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