My Oracle Support Banner

EEX 9.1+: Invalid Date (180,112) Error Message In Expense History Icon From Mobile Expenses In MSSQL Platform (Doc ID 1673780.1)

Last updated on APRIL 10, 2019

Applies to:

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

Symptoms

ISSUE:

When an Employee is attempting to access the Expense History functionality within the Mobile Expenses Applications, an Error Message is thrown by the system on those Databases whose platform is Microsoft SQLServer.

Once the Error Message has taken place, the BACK Button is also not usable, and Users have to make use of the HOME Button as the only option to proceed within Mobile Applications.

REPLICATION STEPS:

 - Have an FSCM Environment using a Microsoft SQLServer Database Platform
 - Log into the FSCM Online Application as User ID VP1
 - Navigate to: Employee Self-Service > Mobile Applications
 - Click on the Expenses icon
 - Click on the Expense History icon
 - The system throws the Error Message

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

ERROR MESSAGE:

  " Invalid date. (180,112) EX_MOBILE_EXPENSE_REPORT.Utilities.OnExecute Name:getExpRptHistory PCPC:5719 Statement:111
    Called from:EX_MOBILE_EXPENSE_REPORT.Controller.ExpenseHistoryController.OnExecute Name:ExpenseHistoryController Statement:17
    Called from:WEBLIB_MBL_EX.ISCRIPT1.FieldFormula Name:iScript_expenseHistory_Home Statement:64 "

ACTUAL RESULT:

The Mobile Expenses Application becomes unusable when the Employee tries to review the Historic transactions in the system. The Error Message cannot be bypassed, and prevents the user from going further.

EXPECTED BEHAVIOR:

The Mobile Expenses Application should work properly in Microsoft SQLServer Database Platform just as it is working in any other supported Platform (Oracle, DB2, Sybase, ...).

 

NOTE: In 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.