Fiscal Date Patterns
Fiscal date patterns are user-defined codes (UDCs) (H00/DP) that identify the year and the order of the months of that year for which the system creates the forecast. JD Edwards EnterpriseOne Forecast Management uses fiscal date patterns to determine the time periods into which the sales order history is grouped. Before you can generate a detail forecast, you must set up a standard monthly date pattern. The system divides the sales history into weeks or months, depending on the processing option that you select. If you want to forecast by months, you must set up the fiscal date pattern. If you want to forecast by weeks, you must set up both the fiscal date pattern and a 52 period date pattern.
To set up fiscal date patterns, specify the beginning fiscal year, current fiscal period, and which date pattern to follow. JD Edwards EnterpriseOne Forecast Management uses this information during data entry, updating, and reporting. Set up fiscal date patterns for as far back as the sales history extends and as far forward as you want to forecast.
Use the same fiscal date pattern for all forecasted items. A mix of date patterns across items that are summarized at higher levels in the hierarchy causes unpredictable results. The fiscal date pattern must be an annual calendar: For example, from January 1, through December 31; or from June 1, through May 31.
The JD Edwards EnterpriseOne System recommends that you set up a separate fiscal date pattern for forecasting only so that you can control the date pattern. If you use the date pattern that is already established in Oracle's JD Edwards EnterpriseOne Financial Management system, the financial officer controls the date pattern.