EAM: Effective Dated Combo Edits Not Recognized In AM (Doc ID 1962883.1)

Last updated on JULY 14, 2017

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Although combo edits are in place, when saving an asset with dates which fall in the range of the combo edit rule, no combo edit message is received.

Business Impact:
Invalid combinations are allowed to be saved. However if the asset uses dates that fall within the SYSTEM date (i.e. the date you're physically saving the transaction), a Combo Edit error correctly appears.

Steps to replicate:
1. Set up the BU so it has a chartfield edit option of Reject with error.
2. Set up a Combo Rule of a small range of dates (e.g. 06/01/2014 - 08/01/2014), but do your test in September of 2014.
3. Add an asset with an invalid deptid using trans date and accounting date which fall in that range (e.g. 07/01/2014), but do the test today (e.g. 09/17/2014).
4. Save

Expected results:
Expected a combo edit message about an invalid combination, so unable to save the asset.

Actual results:
No message appears and we're able to save the asset.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms