E1: 34: 36: R34610 Force Changes Down by Customer Category Codes
Last updated on OCTOBER 12, 2016
Applies to:JD Edwards EnterpriseOne Requirements Planning - Version 9.1 and later
Information in this document applies to any platform.
On : 9.1 version, Forecasting R34610
R34610 Forecast Forcing Issue
Forcing down using customer address cat codes is resulting in forecast changes for records that were not part of the customer address cat codes criteria to summarize the initial record, such as ALL items within a particular branch.
The expectation is that when forecast changes are forced down, it will update the forecast quantity in the detail records only for those records that meet the summary constant criteria used to summarize the record initially.
Our expectation is that when we make a change to an upper level summary hierarchy record for a particular group of customers, based on a specific cat code in the summary constants, it will update only those customer records.
The issue can be reproduced at will with the following steps:
Run Summarize detail forecast records for a particular customer address book category code setting.Adjust the forecast at a upper level summary level and force changes down.
Note that the detail records update include the items used in the summarization process as well as additional items, such as ALL items with a particular branch. The additional items being updated is the issue.
The issue has the following business impact:
Due to this issue, users cannot force changes down the hierarchy in a controlled fashion. This has a significant impact on planning as detail forecasts are being updated when no change is intended.
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