Last updated on AUGUST 29, 2017
Applies to:JD Edwards EnterpriseOne Demand Scheduling Execution - Version 9.2 and later
Information in this document applies to any platform.
When client has a set up to track CUM by customer PO and a customer changes PO numbers on an existing release/shipping schedule and doesn't send a "Final" release to remove the demand with the old PO, those records will remain in the F40R11. As there is no purge for the F40R11 the result is that there are F40R11 records with past dues dates which require manual intervention to remove those records. The records with past due dates also can produce “unpredictable” results when the R40R010 calculates the forecast.
The request is to add logic to the R40R010 to ignore demand records in the F40R11 with past dues dates.
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