E1: 43: Approval Incorrectly Restarted When Using User Defined Critical Fields
Last updated on JANUARY 02, 2018
Applies to:JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.2 and later
Information in this document applies to any platform.
Order Approvals restart to first approver when you change a non-critical field while the order is still awaiting approval from other approvers.
BUG 24341897 - CHANGE TO NON-CRITICAL FIELD TRIGGERS RE-APPROVAL fixes this if the processing option Reapprove Changed Lines = 3 Standard Critical Fields, but not for Reapprove Changed Lines = 2 User Activated Critical Fields.
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