E1: 53: Change Management Integrity Report
Last updated on JANUARY 29, 2018
Applies to:JD Edwards EnterpriseOne Project Costing - Version 9.2 and later
Information in this document applies to any platform.
Change Management Integrity Report:
Have had a large number of Change Requests where the GL Date has been entered in the wrong month and moved in the Change Management system into the correct month. We also know that the Job Cost tables F0911 and F0902 do not update when the only change from the Change Management system is a change to the GL Date. There is currently no visibility into the integrity of the data between the Change Management and Job Cost systems. If the system is out of sync by month or out of balance there is no organized way to know. The current procedure is for Cost Engineers to watch their Forecasts and reports closely to know if something is incorrect. Unfortunately, there are times when the issue is brought to the Cost Engineers attention by a member of senior management, or when the issue is on a job whose profit is being watched carefully. This level of visibility is not good for either the Cost Engineers or the satisfaction level of Senior Management with the JDE system.
The request is for JDE to develop a Change Management Integrity report that would verify that the amounts in the F5311 and F0911/F0902 tables remain in sync with each other.
The report will need to validate Change Requests by:
Subledger / Change Request number
Ledger Type / Status
GL Date / Change Date
The report will need to take into account that there are Cost, Revenue and Subcontract sections to the Change Management table.
The ability to find issues in a timely and organized way will go a long way toward keeping the integrity of the system.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms