Project

General

Profile

Feature #1624

Reviewed splitting forecast process

Added by Luis Gustavo do Valle Bastos over 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Immediate
Target version:
Start date:
10/06/2015
Due date:
11/19/2015
% Done:

0%


Description

Based on the latest prototype released (merging Redmine issues #1444 and # 1577):

- Change the name of the menu option from “Split” to “Split forecast . . .”

- Once forecasting is executed users click the menu option and a new window with fields for selection in the same layout as the regular fields in the parameters tab should appears. The information existing in the fields of the “mother” forecasting will be displayed in this window as well. See figure attached.

- In this window all fields would be editable by the user, except the reference date which will be automated set up and displayed by the system based on the start date of the forecasting period minus the lead time defined by the user.

- The stock on hand existing at this “automated reference date” will be used for calculations as the new reference date.

- User would be allowed to select forecasting period of minimum one month. A warning message should be displayed in this situation, such as: “Forecasting period must be at least one month”

- The new start date of forecasting period selected by the user minus the lead time selected by the user cannot be lower than the reference date assigned on the “mother” forecasting. A warning message should be displayed in this situation, such as: “Start date of forecasting period minus the lead time cannot be earlier than the reference date assigned for the original forecasting.”

- Instead of allowing user to split the forecasting in many “slices” at once (as in the current prototype) users should be allowed to take one "slice" at a time. Meaning that at the end the addition of all “slices” not necessarily reflects the same quantities in the “mother” forecast.

- After editing the new parameters the users would hit “Execute forecasting” button to get results.

- The new forecasting information and results would be reflected in all tabs (Summary, Med report, Case report, Med detailed report, Order and Dashboard).

- The system should automatically display one observation in all tabs of the split forecasting and also to be exported to excel, such as: “Original Forecasting Split by User".

- Features of Redmine issues # 1579 and # 1578 would be effective when splitting the forecasting as well.

Parameters for splitting forecast.JPG (49.7 KB) Luis Gustavo do Valle Bastos, 10/06/2015 05:26 PM

image.png (42.7 KB) Luis Gustavo do Valle Bastos, 10/16/2015 05:21 PM

image (1).png (60.9 KB) Luis Gustavo do Valle Bastos, 10/16/2015 05:21 PM

image (2).png (78.2 KB) Luis Gustavo do Valle Bastos, 10/16/2015 05:21 PM

image (3).png (80.9 KB) Luis Gustavo do Valle Bastos, 10/16/2015 05:21 PM

image (4).JPG (15.3 KB) Luis Gustavo do Valle Bastos, 10/16/2015 05:21 PM

Date displayed incorrect.JPG (78.6 KB) Luis Gustavo do Valle Bastos, 11/03/2015 08:28 PM

Final date off FC period-incorrect.JPG (128 KB) Luis Gustavo do Valle Bastos, 11/03/2015 08:28 PM

Months of buffer off FC period-correct.JPG (143 KB) Luis Gustavo do Valle Bastos, 11/03/2015 08:28 PM

Initial and final date off FC period-correct.JPG (107 KB) Luis Gustavo do Valle Bastos, 11/03/2015 08:28 PM

Review error message.JPG (70.4 KB) Luis Gustavo do Valle Bastos, 11/06/2015 07:25 PM

749
762
763
764
765
766
789
790
791
792
816

History

#1 Updated by Oleksii Kurasov over 9 years ago

  • Status changed from New to Resolved
  • Assignee changed from Oleksii Kurasov to Luis Gustavo do Valle Bastos

#2 Updated by Luis Gustavo do Valle Bastos over 9 years ago

762
763
764
765
766

1) Change the label of the item in the menu from "Split" to “Divide . . .”. See file called "Image" attached.

2) Change the title of the dialog box from "Get a slice" to “Divide forecasting”. See file called "Image (1)" attached.

3) Remove the calendar symbol (not only "gray' it as now), as long as user won't be able to change the reference date anyways. See file called "Image (1)" attached.

4) Change the error message from "Forecasting period for the slice should begin after MONTH DD, YYYY" to "Your start date of the subdivided forecasting (MONTH DD, YYYY) minus the lead time cannot be earlier than the reference date of the original forecasting.” See file called "Image (2)" attached.

5) Change the error message from "Forecasting period should be at least 1 month" to "Forecasting period must be at least 1 month." See file called "Image (3)" attached.

6) Create an error message when users try to select the start date or the final date of the forecasting period after the final date of the original forecasting period plus the months of buffer. The message must be: "Your start and final dates of the subdivided forecasting period (MONTH DD, YYYY) must be within the original forecasting period plus the months of buffer."

7) Allow lead time to be set up as zero and replace the related error message [See file called "Image (4)" attached] by a warning message in both original and subdivided forecastings. This warning message must have a title “Do you want to continue? and the text “Lead time is 0” and the buttons “Yes” and “No” at the bottom.

#3 Updated by Luis Gustavo do Valle Bastos over 9 years ago

For item 6 above both start and final dates should be displayed in the error message as: (MONTH DD, YYYY and MONTH DD, YYYY).

#4 Updated by Luis Gustavo do Valle Bastos over 9 years ago

Still for item 6 above the months of buffer stock entered by the user should be displayed in the text of the message as number between brackets.

#5 Updated by Oleksii Kurasov over 9 years ago

  • Due date set to 10/23/2015
  • Status changed from Feedback to Resolved

#6 Updated by Oleksii Kurasov over 9 years ago

  • Assignee changed from Oleksii Kurasov to Luis Gustavo do Valle Bastos

#7 Updated by Luis Gustavo do Valle Bastos over 9 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Luis Gustavo do Valle Bastos to Oleksii Kurasov

#8 Updated by Luis Gustavo do Valle Bastos over 9 years ago

- Information entered in all fields of the subdivided forecasting have not been saved after hitting the button "Save".

- Label of the item "Divide" in the menu must have 3 dots after it.

- The error message "Your start date of the subdivided forecasting (MONTH DD, YYYY) minus the lead time cannot be earlier than the reference date of the original forecasting." must display the date entered by the user and not the original date. Please correct.

- The error message "Your start and final dates of the subdivided forecasting period (MONTH DD, YYYY, MONTH DD, YYYY) must be within the original forecasting period plus the months of buffer (number)." must be triggered by entering the final date date of the forecasting and the months of buffer. Currently it is working properly only when entering the months of buffer. Please correct.

- When triggered by final date of the forecasting, the message above should display the date entered by the user (not the previous date) and the date in the field must be switch back to the previous date (not entered by the user).

- Keep all fields as displayed now at the "Divide forecasting" dialog box (it is different from what we have discussed by skype).

#9 Updated by Luis Gustavo do Valle Bastos over 9 years ago

- Include the field "Comment" in the dialog box of the divide forecasting.

#10 Updated by Oleksii Kurasov over 9 years ago

  • Due date changed from 10/23/2015 to 10/26/2015
  • Status changed from Feedback to Resolved
  • Assignee changed from Oleksii Kurasov to Luis Gustavo do Valle Bastos

#11 Updated by Luis Gustavo do Valle Bastos over 9 years ago

789
790
791
792

Still pending:

- Label of the item "Divide" in the Forecasting menu must have 3 dots after it (currently has only 2 dots).

- The error message "Your start date of the subdivided forecasting (MONTH DD, YYYY) minus the lead time cannot be earlier than the reference date of the original forecasting" must display the date entered by the user and NOT the original date. Please correct. See figure "Date displayed incorrect" attached.

- System doesn't display the error message "Your start and final dates of the subdivided forecasting period (MONTH DD, YYYY, MONTH DD, YYYY) must be within the original forecasting period plus the months of buffer (number)" when changing ONLY the final date off the original forecasting period. Please correct. See figure "Final date off FC period-incorrect" attached.

- However system displays correctly the error message above when keeping the same dates as above but changing the months of buffer. No action needed. See figure "Months of buffer off FC period-correct" attached.

- When changing the initial date (but keeping it within the original period) and changing also the final date (but putting it off the original period) system displays the above message correctly. No action required. See figure "Initial and final date off FC period-correct" attached.

#12 Updated by Oleksii Kurasov over 9 years ago

  • Due date changed from 10/26/2015 to 11/05/2015
  • Status changed from Feedback to Resolved
  • Assignee changed from Oleksii Kurasov to Luis Gustavo do Valle Bastos

#13 Updated by Luis Gustavo do Valle Bastos over 9 years ago

  • File Review error message.JPG added
  • Status changed from Resolved to Feedback
  • Assignee changed from Luis Gustavo do Valle Bastos to Oleksii Kurasov
816

- Include the lead time entered by the user between brackets when it triggers the error message as "Your start date of the subdivided forecasting (MONTH DD, YYYY) minus the lead time (Number) cannot be earlier than the reference date of the original forecasting (MONTH DD, YYYY)"

- Display the lead time of the original forecasting between brackets in the message above also when the start date of the forecasting triggers the message.

- Delete the dot before the (MONTH DD, YYYY) at the end of the message above.

See figure attached

#14 Updated by Oleksii Kurasov over 9 years ago

  • Due date changed from 11/05/2015 to 11/10/2015
  • Status changed from Feedback to Resolved
  • Assignee changed from Oleksii Kurasov to Luis Gustavo do Valle Bastos

#15 Updated by Luis Gustavo do Valle Bastos over 9 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Luis Gustavo do Valle Bastos to Oleksii Kurasov

- Display the lead time number between brackets in the error message. Currently it is not displayed between brackets and we have to be consistent with other information displayed in the message.

#16 Updated by Oleksii Kurasov over 9 years ago

  • Due date changed from 11/10/2015 to 11/19/2015
  • Status changed from Feedback to Resolved
  • Assignee changed from Oleksii Kurasov to Luis Gustavo do Valle Bastos

#17 Updated by Oleksii Kurasov over 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF