My Oracle Support Banner

EEX 9.2: Fluid Expense Report Triggers Error Message at Line Distribution Level 'Require ChartField 1, ChartField 2 for This Transaction' (Doc ID 3068651.1)

Last updated on JANUARY 23, 2025

Applies to:

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

Symptoms


When an Employee is creating a new Expense Report transaction in Fluid UI, and the Distribution Accounting Line page is being accessed to change/populate some of the Accounting ChartFields, the system is throwing an Error Message stating that ChartField1 and ChartField2 fields cannot be left as blank, as they are required.

When doing the same steps in Online Classic pages, the Expense Report can be saved, and submitted for approval without any problems.

REPLICATION STEPS:

  1.- Log into the FSCM 9.2 Online Application as an Expenses User.
  2.- Go to the Employee Self Service Fluid Homepage.
  3.- Click on the Expenses tile.
  4.- Click on the Create Expense Report tile.
  5.- Define the Expense Report Header main fields, (Business Purpose, Description, Default Location).
  6.- Select the option of 'Add Expense Lines' in the Expense Report Action drop-down list.
  7.- At the Expense Entry page, fill in an Expense Type, Description, Payment Type, Billing Type, and Expense Amount.
  8.- Click on the Accounting button to access the Distribution Line.
  9.- Fill in the needed Accounting ChartFields such as Business Unit GL, Account, Department ID, and alike fields.
  10.- Click on Done button.
  11.- PROBLEM: The system throws an Error Message.

ERROR MESSAGE:

  " Require ChartField 1, ChartField 2 for this transaction.
    Review each accounting line and populate the required chartfield values. "

 
Users are unable to save, and submit for approval, the desired Expense Report, if the ChartField1 and ChartField2 fields are left blank at the Distribution Accounting Line level.

Once all required Accounting ChartFields have been properly populated, (those fields with an asterisk sign should be deemed required), the system should not trigger such Error Message, and instead, should allow the transaction to be saved, and submitted for approval.

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


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