My Oracle Support Banner

E1: 34: 36: Request R34610 Force Changes Down by Customer Category Codes Without Customer Number Included in Hierarchy (Doc ID 2903030.1)

Last updated on SEPTEMBER 27, 2024

Applies to:

JD Edwards EnterpriseOne Requirements Planning - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When a Summary Forecast Hierarchy includes Customer Category Codes, but the customer address book number is not included in the hierarchy, the force changes down can update item and branch records in another branch (cust) of the hierarchy.

  1. Create a Forecast Summary Hierarchy that uses Customer Cat Codes, not Item Branch Cat Codes, but leave the Customer Address level as blank, to not include as a hierarchy level.
  2. Generate F3400 summary forecasts.
  3. Make changes at summary level for a particular record
  4. Run R34610, forcing the changes down to the detail.
  5. Review the detail records. The updates at the item branch level are not correct.

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.  This is a known issue and is not supported in current code. Per KM Solution E1: 34: 36: R34610 Force Changes Down by Customer Category Codes (Doc ID 2192386.1), the solution is to include the Customer Address in the hierarchy.

This does not always meet business requirements. 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.

Here are the basic requirements requested.

  1. Establish the item and branch percentages for each hierarchy based on the detail history in the F3460 Detail Forecast File.
  2. Review forecast type per processing option 3 (default = AA)
  3. Review months of historical forecast to review per processing option 4
  4. Review address book record number for each forecast to determine the sales territory
  5. Join F3460.AN8 to F0101.AN8, Retrieve F0101 Cat Code
  6. Summarize F3460.FQT by 2nd Item Number, F0101 Cat Code, then the branch plant
  7. This summary will be for the number of months specified in processing option 4
  8. Derive the percentage of each branch relative to the total for each summary.
  9. Store this data in a new custom table
  10. Generate the detail forecast data
  11. Review each F3400 record based on processing options 1 Hierarchy Summary Constant and 2 Forecast Type (Default = BF)
  12. For each F3400.ITM, F3400.DRQJ, F3400.KV02.
  13. Review F3400.FQT, distribute the quantities to each branch plant per the percentages established in step 1. Round to 2 decimals. Accumulate this number for each item/branch/month. Use F3400.ITM to retrieve F4101.LITM. Loop through this logic for all the F3400 summary data (12 – 24 months)

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.