My Oracle Support Banner

EEX 9.2: Error Message "Field Does Not Exist – EX_ER_LINE_WRK.APPROVAL_DT. (2,104)" Triggered When Attaching a Receipt File Into a Fluid Expense Report Line (Doc ID 2976264.1)

Last updated on OCTOBER 05, 2023

Applies to:

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

Symptoms

Employees receive an Error Message when trying to upload a new attachment file into a Fluid Expense Report Line transaction level.

REPLICATION STEPS:

    1.- Create a Change Package that contains the codeline changes from major Patch 33540509, along with all listed/detected requisites missing
    2.- Apply the Change Package into the FSCM 9.2 Image #37 Target Environment
    3.- Log into the FSCM Online Application as an Expenses Employee
    4.- Go to the Employee Self Service Fluid Homepage
    5.- Click on the Expenses Tile
    6.- Click on the Create Expense Report Tile
    7.- Define all the Expense Report Header field details
    8.- Select the Expense Report Action of 'Add Expense Lines'
    9.- Define all needed fields from an Expense Report Line
    10.- Click on the Attach Receipt button
    11.- PROBLEM: The system throws an Error Message

ERROR MESSAGE:

    " Field does not exist -- EX_ER_LINE_WRK.APPROVAL_DT. (2,104)

      EX_ER_ATT_LN_SCF.Activate  PCPC:33  Statement:1

      A reference to a record.field name was made and the record.field name was not found to exist. Verify that the field exists on the page in which the PeopleCode program is being executed.

      Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed. "


This prevents the upload of any file receipts as attachments on Expense Report Lines in the system using Fluid UI, which subsequently delays the potential transactions' approvals, and eventually, reimbursement.

The system should enable Employees create new Expense Report transactions using Fluid User Interface without any such Error Messages being triggered.

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.