E1: 53: Need a Workflow for the Change Request Entry (P5310) For Approving Change Requests, Planned Change Orders and Change Orders (Doc ID 1950404.1)

Last updated on NOVEMBER 23, 2015

Applies to:

JD Edwards EnterpriseOne Project Costing - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

Would like functionality that allows one user to enter the change request and another user to approve it before it updates the ledgers.  It only updates certain ledgers based on what is setup in the Detail Status Code file.  Based on the software, there is not a way to lock out some users to the Approval Process.  The statuses just move the change request along the different statuses updating different ledger types, but does not have the ability to limit users to certain statuses.  The Detail Status file controls what statuses are used and what ledgers are updated and what fields in the file get updated.

The only other control feature is the PO on the P5310.  The system always uses the below processing option to determine if F0911 records are created.  It does not matter if the system is going from one status to another status.  It just writes to the F0911 based on the below PO
that is on the Audit Tab of the P5310.

1. Audit Trail - F0911
Blank = create per period change
1 = create audit trail records
2 = no audit trail records are created

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