CVR Rule With Future Date Start Date Was Triggered Prior To The Set Start Date (Doc ID 2962274.1)

Last updated on AUGUST 12, 2024

Applies to:

Goal

If you create a Cross Validation Rule (CVR) with a Start Date = 07/01/2023 then on 6/07/2023 (creation date) during the same evening, the ESS Job "Manage Cross-Validation Rule Violations" ran, all the COA combinations that was triggered by the rule were disabled.

With the Start Date = 7/01/2023, the expected result would be for the rule to be active on 7/01/2023 and any new COA combinations that trigger that rule should error and the ESS job that runs in the evening would disable any prior COA combinations that violates the rule effective 7/01/2023.

Please advise why the ESS job that ran on 6/07/2023 disabled the COA combinations when the rule shouldn't be active until 7/01/2023?   The process does not check the dates if the CVR is enable it will be used when running the ESS job.
 

Solution

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