Release Notes 9.110.0

These release notes provide brief descriptions of changes included in eHarvest 9.110.0.

System Updates

Forms & Reports

DESCRIPTION ID #

PRH: With this ticket, a Production Revenue History (PRH) form has been added to the System for all years (the System will determine when PRH is able to be added. This form is available to print from the MPCI policy Print tab as well as from the Batch Printing menu (for the Batch Printing menu, it'll display when "Production Reporting" or "Show All Forms" are selected from the Processing Season dropdown). The following report styles will be available for the PRH form: Blank Form, Pre-Headed Form - with Agency info only, and Pre-Headed Form - with Applicant / Insured & Agency info only (default). The "Include Extra Page" print option is also available for the PRH form and is unselected by default. Additionally, "PRH Report" was added to the Attachment Type list for attachments, and a QR code will print when the form is printed in the Pre-Headed Form - with Applicant / Insured & Agency info only report style. Users can manually attach or attach via Batch Scanning.

119810

AR: The MCEU Section and Summary Units for PTY and MY on the Acreage Report (AR) have been updated in the following ways for all years:

• Units with a unit number of 0000-0000 on the form will no longer print on the Acreage Report as Growers do not report data on those Summary Units. The System creates a summary 0000-0000 unit for MY and PTY.
• Previously, when the unit structure for an MCEU coverage was EU, the MCEU data was not printing in the MCEU section. The MCEU data was printing with the EP unit structure, however. The MCEU section was updated to print with EU MCEU data also.

121888

CLU AR: The MCEU Section and Summary Units for PTY and MY on the CLU Acreage Report (AR) have been updated in the following ways for all years:

• Units with a unit number of 0000-0000 on the form will no longer print on the CLU Acreage Report as Growers do not report data on those Summary Units. The System creates a summary 0000-0000 unit for MY and PTY.
• Previously, when the unit structure for an MCEU coverage was EU, the MCEU data was not printing in the MCEU section. The MCEU data was printing with the EP unit structure, however. The MCEU section was updated to print with EU MCEU data also.

121889

SPOIs were updated and made available from RMA on April 1. The Special Provisions for 2022 have been implemented in the System.

126603

Global

DESCRIPTION ID #

The Online Help Site was updated with topics as well as with current release notes.

126326

The 2022 Reinsurance Year was added to the RY options in the System. Users can now create 2022 policies and growers.

125864

Livestock

DESCRIPTION ID #

A comment,"Balance Currently Billable: $###", which displays the Livestock Detail Lines total amounts that are currently billable has been added to the Livestock policy's Policy Balance tab. This comment is shown in the Premium Summary section on the tab in a smaller, italic font. The dollar value reflected in this comment is the current summed amount of all reflected Detail Lines where the RMA Bill Date is prior or equal to the current (today’s) date. If there is no RMA Bill Date reflected on a Detail Line, the Detail Line's balance will still be included in the comment, regardless of the current date.

125549

An enhancement request was received asking to update the Save & Exit button on the DRP Detail Line pages to be conditional. If both the Insured Signature Date and the Agent Signature Date exist, the Save & Exit button has been updated to now read "Save & Submit". If no Signature Dates or only one of the two Signature Dates exists, then the button will continue to read "Save & Exit". There has been no change in the functionality of the button, only a wording update on the button itself.

124904

Mapping

DESCRIPTION ID #

Users have requested the ability to indicate on sync that they want to process remaining lines as zero acres, similar to how Fast Edit AR allows user to indicate they are completed with processing the AR. This has been done; however, an issue exists when the coverage page displays for selection, only coverages with mapped fields are displaying. This will be addressed with TFS #126726 created to allow coverages without mapped fields to display to allow a zero AR to be processed for the whole coverage.

71647

Users requested that the printing of map-based forms when all coverages for a policy are canceled no longer be allowed. This has been implemented.

71722

Since some parts of Missouri do not use standard surveyed sections, the PLSS Section layer had holes where those surveys exist. The section layer has been updated to add survey data from RMA/BLM to fill in those holes for these Missouri Counties: Bollinger, Boone, Callaway, Cape Giradeau, Chariton, Clay, Cooper, Franklin, Howard, Jefferson, Lafayette, Lincoln, Madison, Moniteau, New Madrid, Permiscot, Perry, Pike, Ralls, Ray, St. Charles, S. Clair, St. Genevvieve, St. Francois, St. Louis, Saline, Scott, Warren, Washington, Wayne.

NOTE: Although section boundaries for the current holes in MO, there are two known issues: 1: Some of the sections we received contain 4 digit section numbers. Currently, the System can only support 3 digits. Any section with a 4-digit section number is temporarily numbered with a section number of "0" and will be updated later once the System can support 4 digits. 2: Townships - This is still incomplete and will need to evaluated with future "manual" updates. In an areas where a new section does not contain a corresponding township, a full legal will not print on forms or validate in the MPCI Land ID page. In these cases, just use Farm Number and Tract for land ID reporting as has been done in the past.

117724

Users requested additional information display on the Sync to AR page to summarize Planted, PP, and UI acres by coverage prior to sync. This has been implemented. In Sync to AR tab, in the coverage banner, the following acre totals display:

• CLU Acres: the sum of the calculated CLU acres for fields associated to the coverage
• Planted Acres: sum of acres with a plant date (NOTE: if UI with a plant date, it will be included both in this total and the UI total)
• PP Acres: the sum of acres marked as PP
• Uninsurable Acres: the sum of acres marked with a UI Reason code

121081

Since some parts of Illinois do not use standard surveyed sections, the PLSS Section layer had holes where those surveys exist. The section layer has been updated to add survey data from RMA/BLM to fill in those holes for these Illinois Counties: Champaign, Clark, Cook, Crawford, Edgar, Ford, Iroquois, Jackson, Kankakee, Lawrence, Madison, Monroe, Randolph, St. Clair, Wabash, Will

NOTE: Although section boundaries were added for the current holes in IL, there are two known issues: 1: Some of the sections we received contain 4 digit section numbers. Currently, the System can only support 3 digits. Any section with a 4-digit section number is temporarily numbered with a section number of "0" and will be updated later once the System can support 4 digits. 2: Townships - This is still incomplete and will need to evaluated with future "manual" updates. In an areas where a new section does not contain a corresponding township, a full legal will not print on forms or validate in the MPCI Land ID page. In these cases, just use Farm Number and Tract for land ID reporting as has been done in the past.

125490

A new updated 2020 HR Map Layer is loaded into the Mapping module.

126270

Precision Ag: The following changes to printing have been made for the Precision Ag Module when the Planting Layer is included on the Printed Map Based Acreage Report:

1. When the Planting Layer is included in the MBAR Print, the polygon boundary of the planting layer is 6-8 times thicker than the display on the user interface. This has been corrected so the boundary thickness on printing is matching the user interface.

2. Set the Planting Layer planted acres label to apply the halo affect on the printed pages.

3. Do not label the planted acres from the Planting Layer on the overall page; these will only include on the individual map pages.

126301

MPCI

DESCRIPTION ID #

HIP: This ticket implemented the policy-side changes to support the HIP Acre Limitation Changes.

• A Prior Year Amount of Insurance was added and will display for Nursery, Nursery Value Select, and Tree Crops coverages. This value will be manually determined by the user and is necessary to apply the HIP Limitation should a hurricane occur before the insured provides their Acreage Report, Plant Value Inventory Report, and Nursery Value Report.
• A HIP AIP Approval Date field was added. This field will be available to AIP users to edit. This field is for the AIP to verify the greatest acres in the previous 4 years value calculated by the system or any intended acres or prior year amount of insurance values keyed by an agent. A date must be applied in this field in order for the premium calculation to apply any HIP Acre Limitations or HIP Amount of Insurance Limitations (for non-acre crops).

NOTE: HIP Limitation only applies if a hurricane hits before the insured provides their Acreage Report, Plant Value Inventory Report or Nursery Value Report.

• The logic that triggers the HIP Limitation portion of the premium calculation was also updated with this ticket:
• For acre crops, the HIP Acre Limitation will be applied if the following criteria exists:
• A HIP AIP Approval Date exists on the coverage,
• A triggering event date exists on the detail line (this date will only be populated if the AR Sign Date is after the Triggering Event Date), and
• Intended Acres (for new HIP coverages) or Greatest Acres in Previous 4 Years (for carryover HIP coverages) are less than acres planted at the time of the hurricane.
• For non-acres crops (Nursery, NVS, Tree Crops), the HIP premium will be calculated using the Prior Year Amount of Insurance if the following criteria exists:
• A HIP AIP Approval Date exists on the coverage,
• A triggering event date exists on the detail line (this date will only be populated if the AR/PIVR/NVR Sign Date is after the Triggering Event Date),
• The HIP policy is a carryover policy, and
• The prior year amount of insurance is less than the current year amount of insurance.

119335

PRH: The first of several updates were made to the System to support 2022+ Production Revenue History (Strawberries) coverages. This ticket implemented the Revenue History grid and Summary record within the user interface. Additional updates will continue to be made over upcoming releases.

120909

WFRP: Internal testing found a WFRP Quote bug that was requiring Prior Year Tax ID fields to be keyed before proceeding with saving a new WFRP Quote. With TFS #123904, these fields were implemented to match grower record data for RMA transmission purposes along with this validation when Revenue Cup (RC) applies. This ticket will update the Add MPCI Quote page to no longer triggering this validation when RC is elected on a quote so that the user can continue creating the quote with the RC option This ticket also implemented a hard stop error when Converting Quote To Policy functionality is invoked, so the user will have to add Prior Year Tax ID and Tax ID Type values on the quote before converting the Quote to a Policy.

126149

HIP: Three bugs were found while testing various combinations of HIP, SE, SCO, and STAX. Details surrounding each bug are provided below:

• Insured elected HIP, SE, STAX, and STAX + SE. In this scenario, the base MPCI coverage should only have the SE Option applied. The related STAX coverage should have HIP and SE Options applied. It was determined that the System was not generating the necessary HIP-SE line on the related STAX coverage in this scenario. It was working at one time, but the HIP-SE lines were being removed when STAX lines were re-created. This was most likely broken with TFS #121214 in the 9.090 Release.
• Insured elected HIP and STAX with SE. In this scenario, the base MPCI coverage should not have HIP applied to it. The related STAX Coverage should have HIP and SE Options applied. It was determined that the System was building a HIP-SE on the STAX Coverage. A HIP-SE line should not be created since the insured only elected SE for STAX and not the related MPCI Coverage. The same issue existed when the Insured elected HIP, SCO, STAX, and STAX + SE (again, no SE for the related MPCI Coverage).
• Insured elected HIP, SE, SCO (with or without SE), and STAX with SE. In this scenario, the base MPCI coverage should have the HIP, SE, and SCO (with out SE) Options applied. The related STAX coverage should have the HIP and SE Options applied. When a Unit with SCO Acres was keyed, the System was not generating the necessary HIP-SE line on the base MPCI coverage for the unit.

With this ticket, the System has been updated to build the correct lines in each of the scenarios described above. A cheat sheet document was created to help users understand different scenarios.

126409

Flue Cured Tobacco: With TFS #123640, changes were made for the 2021+ RY in order for the System to able to support contracted and non-contracted acreage for Flue Cured Tobacco (0229). With these changes, the user would be able to key a new contract for Flue Cured Tobacco even if the "CP" option had not been elected on the coverage. Validations were also added to be received within the Add New and Maintain Contract pages depending on whether the "CP" option was elected or not elected on the coverage. If "CP" was elected a validation of "Contracted price cannot exceed the Maximum Contract Price in ADM" would be received upon save of the contract if the value within the Contract Price field exceeded the "Maximum Contract Price" value from the Price ADM (A00810). If "CP" was not elected on the coverage a validation of "Contract Price cannot exceed the Maximum over Established price from ADM"' would be received upon save of the contract if the value within the Contract Price field exceeds the "Maximum Over Established Price' value from the Price ADM (A00810)".

There were some open questions around the calculation of the Weighted Average Price (WAP) that were pending at RMA during the development of that ticket. Clarifications have been received and a couple of modifications to the logic implemented in the earlier ticket will be required and made with this current ticket.

With this ticket the System logic will be updated to calculate the WAP across counties when multiple counties are insured on the SAME policy. At this time, there are no plans to extend the calculations across multiple policies due to performance concerns and the required calculations that would have to be performed each time details lines are saved, etc.

A new WAP Price Override field was also added on the current Contract page for Flue Cured Tobacco (0229). This WAP Price Override field will allow the user to manually calculate the correct WAP (across policies) and apply it to the applicable contract on each policy if applicable. When applied, the detail line logic will be updated to always use the Override value in the premium calculations and transmission.

126289