Release Notes 9.040.0

These release notes provide brief descriptions of changes included in eHarvest9.040.0.

System Updates

Forms & Reports

DESCRIPTION ID #

LRP App: An issue was found where the LRP Application was missing page 1 when printing with a policy that had canceled coverages. With this ticket, the LRP Application has been updated to include page 1 when the form is being printed for active and canceled coverages for all report styles. This update applies for all years.

120554

SOI: The Schedule of Insurance (SOI) has been updated in the following ways for all years:

• The Detail Line title and column / field labels will print above the first detail line on each page. Then, these will only print on the page when there is a county change or if there is a change in a field label (e.g., with Fruit, Trees, Nursery, and Grapes).
• For multi-year module crops (Pecans, Olives, and Pistachios), the year of the module will print under the Unit number for the parent unit when data is available (e.g., Year 2 of 2 Year Module OR Year 1 of 2 Year Module). This will not print on child lines.

62433

RMA added the Forage Seed (Alfalfa Seed) Underwriting Report to the 2021 DSSH. With this ticket, this form was updated to meet DSSH form requirements and base form standards as well as include some AIP requests. Some of the changes include:

• The "Date Planted MM/DD/YYYY" label was updated to "Date Planted M / D / YY". The data format was updated to print in the same format.
• The Signature Section was updated to have Printed Name fields on left and Signature and Sign Date fields on the right. Also pre-filling Insured's name in the Printed Name field when applicable.

119099

SPOI: Forage Production (0033) with Plan AYP (04) 2021 Special Provisions in IL, MN, PA, and WI were updated and made available from RMA on July 30, 2020. These Special Provisions for 2021 have been downloaded and implemented in the System.

119399

Provisions: With this ticket, the 2021 WFRP Policy and Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

120287

SPOI: California (CA) Citrus Trees and WFRP 2021 Special Provisions were updated and made available from RMA on August 28, 2020. These Special Provisions for 2021 have been downloaded and implemented in the System.

120294

Provisions: With this ticket, the 2021 Hurricane Insurance Protection (HIP) Data Provisions and Wind Index Endorsement have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

120306

Provisions: With this ticket, the 2022 Florida (FL) Citrus Fruit Crop Provisions with the APH (90) Plan have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

120307

Provisions: With this ticket, the 2021 California Citrus Trees Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

120308

Provisions: With this ticket, the 2021 Pistachio Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

NOTE: RMA published updated Pistachio Crop Provisions on September 11, 2020; these will be implemented in the System in a future release with TFS #120774.

120309

Provisions: With this ticket, the 2021 Rainfall (RI) Policy for PRF (008), API (1191), and Annual Forage (0332) has been implemented in the System. Additionally, the 2021 Provisions for PRF and API have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

120228

SPOI: Florida (FL) Citrus Fruit 2022 Special Provisions were updated and made available from RMA on August 31, 2020. These Special Provisions for 2022 have been downloaded and implemented in the System.

120409

MPCI App: An issue was found where, on the main MPCI Application, the Crop Year in the page 2+ header was not printing with the +1 when the pre-print for next year print option was selected. This issue has been resolved for all Crop Years.

120728

SOI: On the Schedule of Insurance (SOI), an issue was found where data was printing for coverages with zero acres in the MP Premium Reduction Section. With this ticket, the SOI has been updated to print premium information correctly in the MP Premium Reduction Section. This update applies for all years.

120468

SPOI: PRF (0088), API (1191), and Pistachios (0470) 2021 Special Provisions were updated and made available from RMA on August 27, 2020. These Special Provisions for 2021 have been downloaded and implemented in the System.

120274

SOI: The Schedule of Insurance (SOI) for Nursery Value Select (NVS) has been updated in the following ways for all years:

• The Nursery Reported Inventory Values were updated to print the full value on the detail lines. Previously, the last digit was not printing for both Nursery Value Select (NVS) and FG&C.
• The Nursery Reported Inventory Value for FG&C was updated to print with a dollar sign in the Premium Summary.
• The sort order in the Premium Summary for NVS was updated to match FG&C (print by Practice, not Type, in alpha order).
• The HIP lines in the Premium Summary for both NVS and FG&C were updated to print Practice data before Type data in the Crop field. Previously, Type was printing before Practice in the Premium Summary.

120609

Global

DESCRIPTION ID #

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

118647

Mapping

DESCRIPTION ID #

Users requested the addition of an ESRI Hybrid layer with road labels; this has been implemented and the ESRI Hybrid layer is now an option on the Layers panel. When printing a map book from within the Mapping Module and this layer is active, then the layer's details print on the map book.

111895

For PRF fields, a data extract of PRF information is now available via Tools > Export Fields in the Mapping Module. This is only available to users who have the proper permissions.

120247

Users requested to have the option to shade by unit group when printing a PRF Mapbook. Now, users can select "Unit Group" from the Shade By dropdown in the PRF Map Book print tab.

120164

A new mapping layer for September 2020 was released by the RMA and has been implemented in the System.

120952

It was found while testing that when using the Sync from AR function to load PRF fields, the System was not setting the Grid ID on the planting records. Then, when the PRF Wizard was used, the System was creating a duplicate planting record that had the Grid ID, which caused acres too appear doubled. This has been corrected.

121040

Users requested that, when drawing a polygon map region, that the selection area be made transparent to be able to identify the fields being included in the map region. This has been implemented.

118363

MPCI

DESCRIPTION ID #

HIP: RMA issued a new GAP option for HIP that will be applicable for the 2020 RY only. The Gap, or "HE", option allows producers of certain crops, where the end of insurance period is before the end of the hurricane season and prior to the beginning of the insurance period for the next crop year, to purchase coverage for the time period coverage gap between the end of insurance period and the beginning of the new crop year's insurance period. TFS #118537 in the 9.030 release implemented functionality to elect this option on the coverage, but at that time RMA had not released the premium calculation. This ticket implemented the rating logic for the new GAP option.

119654

Production Reporting Lockouts: Functionality was originally stood up with TFS #54399 for the PRD Lockout logic as it relates to Added Land/New Crop P/T. An exception to the PRD lockout logic was put in place around Added Land and New Crop P/T since APHs for these procedures would be added during ARD and well after the PRD lockout. The exception allows for a new APH to be created by an agency user after the PRD lockout date but only if the following criteria exist:

1. The current date is prior to the ARD lockout date;
2. The override on the APH is set to "Added Land - Simple Average", "Added Land - Variable T-Yield", or "New Crop P/T"; and
3. The users is creating a new APH rather than an existing APH.

The last criterion was the piece the AIP had found issues with. Agency users were creating a new APH by performing a preliminary save and then attempting to perform a standard save after that. Once the preliminary save was performed, the System saved the APH record to the database and viewed the APH as existing rather than a new APH. Therefore, when the user subsequently performs a standard save to calculate the APH (since only a preliminary save was previously performed, the APH does not get calculated), they received the lockout error since #3 was no longer met.

The System logic was updated so an agency user can create a new APH after the PRD lockout date—BUT ONLY if the following criteria exist:

1. The current date is prior to the ARD lockout date;
2. The override on the APH is set to "Added Land-Simple Average", "Added Land - Variable T-Yield", or "New Crop P/T"; and
3. The user is saving an existing APH where the Approved Yield = 0.00 (indicating the Approved APH yield has not yet been calculated for the current RY) AND APH did not roll from prior year.

119000

MCEU: As part of the 2021 MCEU changes, RMA updated procedures to allow additional options for assigning unit structure when the coverage(s) do not qualify for the original election on the ARD, including additional forms of MCEU. This specifically affects when MC is elected with EP on both Irrigation Practices. In this scenario if the coverages do not qualify for MC with EP on both Irrigation Practices and the coverage also does not qualify for EP on both practices without MC, then the following MCEU options are available when assigning unit structure on the ARD:

• MC + EU
• MC + EP Irrigated Practice Only
• MC + EP Non-Irrigated Practice Only

These options are in addition to several non-MCEU unit structure assignments. TFS #116578 in the 9.035 release implemented new override options to allow the AIP to assign unit structure on the ARD based on the 2021 procedures. Prior to 2021, in order to qualify for MCEU, the coverage(s) had to qualify using the original unit structure election; otherwise, the grower was not eligible for MCEU.

Given that MCEU can now be applied using a different unit structure election than what was elected on the coverage, the System's rating logic needed to be updated. Part of the System's rating logic for MCEU determines the total number of acres in each MCEU for use in the premium calculation. In 2020 and prior years, the System used the unit structure election on the coverage to determine which detail lines belonged in which enterprise units when the MC unit structure was applied to the detail lines. For example, if MC + EU is elected, then all detail lines for both coverages are in one enterprise unit, but if MC + EP Both is elected, then all irrigated lines for both coverages would be one enterprise unit and all non-irrigated lines for both coverages would be a separate enterprise unit. However, now that different forms of MCEU can be applied via an override, this logic must first determine if an MCEU override applies, and if so, use the selected override to determine which detail lines make up which enterprise unit. Otherwise, the logic that uses the election on the coverage will continue to apply.

With this ticket the rating logic for MCEU, which determines the total number of acres in each enterprise unit, has been updated to first determine if an MCEU override applies. If so, the System will use that override to determine which detail lines/acres make up each enterprise unit. If an MCEU override is not applied and MC unit structure exists on the detail line, then the System will use the unit structure election on the coverage to determine which detail lines/acres make up each enterprise unit. Each override and coverage election scenario is outlined below.

1. Override = MC + EU or Override is not applied and election on the coverage = MC + EU
• All detail lines for both coverages will be one enterprise unit
2. Override = MC + EP Both or Override is not applied and selected on the coverage = MC + EP Both
• All irrigated detail lines for both coverages will be one enterprise unit
• All non-irrigated detail lines for both coverages will be another enterprise unit
3. Override = MC + EP Irr Only or Override is not applied and election on the coverage = MC + EP Irr Only
• All irrigated detail lines for both coverages will be one enterprise unit
• Non-irrigated detail lines will be BU/OU as applicable
4. Override = MC + EP NI Only or Override is not applied and election on the coverage = MC + EP NI Only
• All non-irrigated detail lines for both coverages will be one enterprise unit
• Irrigated detail lines will be BU/OU as applicable

118857

Quality Loss Option: A new Qualifies for QL flag of "Q" was added to the Production History tab of the APH to indicate when a crop year in the APH qualifies for the Quality Loss Option.

• If the QL option exists for a coverage AND the Qualifies for QL flag is set for a given Crop Year, then on the APH Utilities tab, a "Q" indicator displays within in the APH Utilities grid. The QL checkbox is also selected by default (unless a user removed it because the grower opted out of QL for the given Crop Year(s)). If the QL option is added to a coverage, the Quality Loss checkbox will be applied to all CYs that reflect a Qualifies for QL flag in the database.
• The Pre-Quality Production display in the APH Utilities grid for the qualifying Crop Year. The Pre-Quality Yield values will also display and be used in the calculation of the APH.

119398

Quality Loss Option: It was determined that some adjustments were needed to the original functionality from TFS #108176 that implemented support of the new Quality Loss Option (QLO) in the 9.015 release. These changes were needed to support the ability to designate Crop Years that might qualify for QLO (implemented with TFS #119398 in the 9.040 release).

For the 2021+ RY, any time a Pre Quality Production and/or Yield value is applied to a CY, the Qualifies for QL flag (new with TFS #119398) will be set for that CY. This flag will only be used to indicate that the CY qualifies for QLO because Pre-Quality information is available. It does not mean QLO is actually applied to a given CY(s). Only the QL checkbox indicates QLO is actually applied to a CY(s). This is the flag that displays in the APH Utilities grid of the APH database.

Once set, the only time the new QL flag can be removed for a given CY is if the Pre-Quality Prod and Pre-Quality Yield values are both removed for that CY. This determination will happen upon save of the APH database. If the flag is removed for any reason (by accidentally removing Production and Yield info or deleting a premium line for instance), the System will not be able to restore these values. The user will be required to manually restore the flag by rekeying the Pre-Quality Production and Pre-Quality Yield. This, in turn, will reapply the Qualifies for QL flag.

The following adjustments were also made with this ticket:

• A Pre Quality Production Value cannot be applied without a Pre Quality Yield and vice versa: if a user keys a Pre Quality Prod value without a Pre Quality Yield value, at save of the APH, the System will determine and apply the Pre Quality Yield value for that CY as follows:
• Pre Quality Production / Planted Acres = Pre Quality Yield

NOTE: If a user keys a Pre-Quality Yield value without a Pre-Quality Prod value, at save of the APH, the System will throw the following validation, which already exist with the original functionality from TFS #108176 (hard edit): "Pre-Quality Production is required when Pre-Quality Yield is entered."

• If the Qualifies for QL flag is set, the System will no longer zero out the Pre-Quality Prod and Pre-Quality Yield values if a user unchecks the Quality Loss flag (which indicates that the grower opted out of QL for that CY). These values will be retained as long as the Qualifies for QL flag is set in case the grower opts back in at some point in future CYs.

120199