My Oracle Support Banner

EGL9.2: Updating a ChartField Request with an Effective Date Change is Causing Existing Attributes to Change (Doc ID 2657444.1)

Last updated on APRIL 29, 2020

Applies to:

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


When using the Field Action of 'Update' on a ChartField Request, if the effective date is changed, then, the existing attributes are being updated to the new value.
The system throws a warning message. 


- Before allowing to view the Attributes, the system requires to save the request:

Steps to replicate:

1.  Check existing Chartfield value and its Attributes: (Ex: Operating Unit).
2.  Log in as Requester.
3.  Create Chartfield Request for an update on this Operating Unit Effective Date.
      Received warning message: `This change will cause removing of Attributes and/or Account / Alt-Account Mapping.  Continue? (9080,46)'
      Click Yes and Save.
5.  Select Request Action = Submit for Approval and click Go.
6.  Log in as Approver and access the Operating Unit pending for approval.  In Request Action, select Approve and click Go.
7.  Navigate to Chartfield Values and access Operating Unit.
      Notice that a new Effective Dated Operating Unit has been added.  
8.  Click Attributes link.
      Notice that its Attributes section is blank.  It did not inherit the CF Attribute from earlier Effective Date field value.

See replication here.




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.