My Oracle Support Banner

EEX 9.2: Cash Advance Accounting Chartfield Changes to Current Default after Being Approved (Doc ID 2417707.1)

Last updated on MARCH 27, 2019

Applies to:

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

Symptoms

After a cash advance is submitted for approval the accounting chartfield values on the cash advance are equal to the Default Chartfield Accounting values on the Default Profile for the Traveler. If the Default Chartfield Accounting values on the Default Profile for the Traveler are change before the cash advance is approve, then the original accounting chartfield values on the cash advance are changed to the new Default Chartfield Accounting values on the Default Profile for the Traveler, when the cash advance is approved by the approver.

 

Steps:

1. Create and submit a cash advance (do not approve it yet)
2. From the User Profile, change the Default Chartfield Accounting for the Default Profile for the Traveler. This is the only way to change the accounting for a Cash Advance. Change at least the department but change several other fields as well.
3. Create and submit a second cash advance (do not approve it yet)
4. Query out EX_ADV_DIST for both Cash Advances and the accounting is as expected, the first for the earlier profile defaults and the second with the new defaults
5. Approve the first cash advance
6. Query out EX_ADV_DIST for both Cash Advances and the accounting for the first changed from the original to the new default.

Actual Result:

The accounting chartfield values for the first cash advance changed from the original accounting chartfield values to the new default accounting chartfield values.

Expected Result:

The accounting chartfield values for the first cash advance should not be changed from the original accounting chartfield values.

Please see the replication steps document for more details.

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.