Well Count when populating the Forecast

[JasonSchneider19]

@cameliabalan @arcurve-cheryl-chan @JeffFlowerday When populating the forecast sheet from the sales projects, the well count is used to determine how many wells to put in the forecast Currently the well count has 2 different values. there is a well count in the program that is imported. There is also a well count that is entered by the sales rep in the sales forecast. These values often differ. The well count from the program import is now used We would like to change this to use the value entered in the sales forecast. For example: the well count is 6 if i open up the drill order to see the value from the imported program: The well count is 1 So today we import 1 well or 3 jobs. We would like to import 6 wells, or 18 jobs

[JeffFlowerday]

@JasonSchneider19 What if the well count defined on the drill order is larger than the well count defined on the project?

[cameliabalan]

Examples on how well count will be used: Example 1:

Project well count = 10 DrillOrder 1 well count = 3 DrillOrder 2 well count = 8 DrillOrder 3 well count = 1

It will use the program of drill order 1 to create the jobs for the 3 wells. It will use the program of drill order 2 to create the jobs for 7 wells. It does nothing with drill order 3.

Example 2:

Project well count = 10 Drill Order 1 well count = 4 Drill Order 2 well count = 4

If will use the program from drill order 1 for 4 wells. It will use the program from drill order 2 for 4 wells. It will then do 2 more wells using drill order 1's program. This logic will always use program from the first drill order no matter how many additional wells it needs to process to get to project well count.

Example 3:

Project well count = 10 Drill Order 1 well count = 0 Drill Order 2 well count = 0

It will create jobs for 10 wells using the program for drill order 1.

[cameliabalan]

Tested in Test environment build #202 and passed, all scenarios mentioned are working as described.