Release Notes 6.105.0

RMA updated the Pre-Acceptance Inspection Report (PAIR) for Florida (FL) Citrus Fruit in the December 21st publication of the 2018 Document and Supplemental Standards Handbook (DSSH). The updates are effective for policies with a contract change date for the 2018 and succeeding Crop Years for crops with a contract change date of November 30, 2017 or later. In the 6.080 release, the FL Citrus Fruit PAIR was deployed with TFS #74772. With this ticket, an update was made to set the attachment type to "PAIR" for this form when it is attached to a policy from the Batch Scanning tool. This update applies to all years.

While testing updates to the Plant Inventory Value Report (PIVR) made with TFS #85898 in the 6.090 release, it was found that additional updates were needed. The following updates have been made to the PIVR for all Crop Years:

A new form, Acreage Report - CLU, has been added to the System. This form can be printed in the following report styles: "Blank", "Pre-Headed Form - with Agency info only", "Pre-Headed Form - with Applicant / Insured & Agency info only", and "Pre-Filled Form - With All Land IDs Displayed". This form can be printed from the MPCI policy Print tab as well as from the Batch Printing tool (Tools > Batch Printing).

NOTE: This form is not intended to be used for Annual Forage, Pasture, Rangeland, Forage (PRF), Apiculture (API), Category C Crops, Perennial Crops, Plan Code MP (16) associated with a YP or RP coverage, Plan Code MP-HPO (17) associated with a YP or RP coverage, Plan Code STAX-RP (35) associated with a YP or RP coverage, Plan Code STAX-RPHPE (36) associated with a YP or RP coverage, Nursery, or WFRP.

A bug was discovered where the print option "Print Premium Lines with No Acres" on the Print Forms tab was not working consistently. This issue was fixed.

A bug was reported that the Supplemental Land Page was not printing all of the fields. This has been corrected.

A request was received to add Production Hail / CPP to print on the MPCI / Hail Combo Application with the other Hail products. These updates are applicable to all Crop Years. The Application / Change / Transfer / Cancel Form is available to print within an individual MPCI policy's Print tab and via the Batch Printing tool (Tools > Batch Printing).

Batch Printing: An issue was found within the Batch Printing tool (Tools > Batch Printing). After users entered their search criteria and clicked on the Preview Batch button, when multiple policies were loaded, they had to scroll to see the bottom of the list. When they scrolled down and selected or deselected a grower from the bottom of the list, the page took themback to the top of the list—forcing the user to scroll down the list again to get to the place on the page where they previously were. This issue was fixed.

A 2019 ADM update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2019:

An ICE 2014 update was made by RMA and has been implemented in the System. The following tables have been updated for 2014:

An ICE 2015 update was made by RMA and has been implemented in the System. The following tables have been updated for 2015:

An ICE 2016 update was made by RMA and has been implemented in the System. The following tables have been updated for 2016:

An ICE 2017 update was made by RMA and has been implemented in the System. The following tables have been updated for 2017:

An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:

A 2019 ADM update was made by RMA and has been implemented in the System. The following tables have been updated for 2019:

An ICE 2014 update was made by RMA and has been implemented in the System. The following table has been updated for 2014:

An ICE 2017 update was made by RMA and has been implemented in the System. The following table has been updated for 2017:

An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:

An ICE 2015 update was made by RMA and has been implemented in the System. The following table has been updated for 2015:

Livestock: A request was received to add a Notes tab to Livestock policies. A new tab, Notes, will now display for Livestock policies.

Following the Sales Closing Date, each AIP establishes a lockout date upon which agency users are no longer able to make changes to the coverage, grower, or SBIs. However, by design, agency users are still allowed to edit addresses, phone numbers, and email addresses, at any time, since this information could change following the lockout date. A bug was reported where the System was not allowing agency users to edit SBI address, phone number, or email information following the lockout date. This has been corrected.

Nursery: Beginning in the 2018 Reinsurance Year (RY) / 2019 Crop Year, RMA has updated the Nursery policy to allow basic units by non-contiguous land. Prior to this change, RMA only allowed basic units by share or by type on Nursery Policies. The new option to divide basic units by non-contiguous land will be available on additional coverage policies and field-grown practices only. In addition, when basic units are elected by non-contiguous land, the same coverage level must be applied to all coverages on which the option is elected and the option must be elected on all coverages for the same field grown practice. However, the insured can choose this election on a practice-by-practice basis. For example, basic units by non-contiguous land can be elected on all coverages with a Traditional Field Grown Practice (007) but not on the Certified Organic Field Grown Practice (765). Finally, when basic units by non-contiguous land are elected, the user will be responsible for assigning a different unit number to each non-contiguous land location.

With this ticket, the System will allow the selection of the "BL" option code on Nursery coverages, and logic was added to the detail lines for Nursery to account for basic units by non-contiguous land ("BL" option). Also, a new Nursery coverage validation/warning was added to account for basic units by non-contiguous land ("BL" option), and a new Nursery coverage suspension was added to account for basic units by non-contiguous land ("BL" option).

PTY & APH: In the 6.090 release with TFS 69944, functionality was added to allow users to add a new APH in Fast Edit AR. During internal QA testing of this functionality, an issue was found around adding new APHs and PTY summary units.

By design, once PTY summary units are created, users cannot edit existing APHs or create new ones. The PTY summary units must first be removed, APH changes processed, and then the PTY summary unit recreated. This is necessary in order to correctly calculate the PTY and apply it to the underlying APHs.

The issue found in Fast Edit AR was that the link to add a new APH was still displaying and allowing users to create a new APH, even if a PTY summary unit already existed. The Add New APH drawer logic in Fast Edit AR has been updated to account for PTY summary units as follows:

Acreage Type Code: The Acreage Type Code of "K" is for UUF/Third Party Damage, which is only applicable to APH crops. During internal testing, this code was being displayed for all crops. The Acreage Type Code dropdown on the legacy detail line, detail line drawer, and CLU grid have been updated to only display the "K" Acreage Type for selection when the coverage is for one of the following plan codes: 01, 02, 03, 41, 47, and 90.

APH Overrides: In the 6.075 release with TFS #83396, a new APH Override was added for Classification Yield. This allowed the classification yield logic for Peanuts that require an "F" yield type to be separated from the RSO Determined Yield and Written Agreement logic that also requires an "F" Yield Type. A bug has been reported with this new APH Override and how it relates to reference years.

When "F" Yield Types exist in the APH for classification yields, the System should adjust the reference years to account for classification yields. However, when "F" yields exist in the APH for an RSO Determined Yield or Written Agreement, the reference years should not be adjusted for classification yields. Reference year adjustments for classification yields work as follows:

The bug found with this reference year logic was that the System was utilizing this adjustment for classification yields when the APH Override was "RSO Determined Yield" and was not utilizing the adjustment when the APH Override is "Classification Yield". This adjustment should apply for APH Overrides of "Classification Yield" only. With this ticket, the reference year adjustment logic for classification yields was updated so that it applies only when the APH Override of "Classification Yield" is used.

APH: Per the Crop Insurance Handbook (CIH), a year when only uninsurable acreage of a second crop is grown will be considered a year of production of the crop for both New Producer determination as well as a year of actual yields for determining the applicable percentage of the variable T-Yield. Back in early 2016, a new UI 2nd Crop Acres Apply checkbox was added to the APH page. When this checkbox is selected, the Reference Years field becomes editable to allow users to adjust the reference years to account for years when uninsurable acreage of a second crop only was grown.

The initial design called for this checkbox to only display when the coverage was marked as New Producer. However, New Producer is only applicable the first two years a grower produces a crop in a county, and once the number of reference years reaches 3 or more, the System automatically removes the New Producer status from the coverage. Given that the CIH allows uninsurable acres from a second crop to be used in determining the applicable variable t-yield and the variable t-yield is different when a grower has 3 years of history vs. only 2 years of actual history, the UI 2nd Crop Acres Apply checkbox could be applicable even once New Producer no longer applies. To account for this, the logic that displays the UI 2nd Crop Acres Apply checkbox was updated to display even when New Producer Status is no longer on the coverage.

EP by Practice: As part of the Enterprise Unit functionality, after acres and AR Sign Dates are applied, if the System determines the coverage does not qualify for the unit structure elected on the coverage (EU, EP on both practices, EP on irrigated practices only, or EP on non-irrigated practices only), the System triggers a suspension. This suspension varies depending on what unit structure is elected on the coverage and what unit structure the System determines applies.

Once one of these suspensions triggers, an EU/EP Status Verified checkbox displays on the coverage to allow AIP users to suppress this suspension on future mark completes if they agree with the System's determination.

NOTE: The EU/EP Status Verified checkbox only displays for users with the MPCI EU Override System Function.

During internal QA testing of the new EP functionality on a single irrigation practice, it was found that the new suspensions that trigger when EP is elected for irrigated practices only or when EP is elected for the non-irrigated practice only were not accounting for the EU/EP Status Verified checkbox. The suspensions were continuing to trigger even when the checkbox was selected. The suspension logic for the new EP on a single practice suspensions has been updated to no longer trigger if the EU/EP Status Verified checkbox is selected on the coverage.

EU/EP: As part of the EU/EP validation logic, there are a series of suspensions that can trigger during mark complete, after acres/AR sign dates are applied, when the System determines the coverage does not qualify for the unit structure elected on the coverage. These suspension messages vary depending on what unit structure is elected on the coverage and what the System determines the coverage qualifies for.

During some internal testing of the EU/EP functionality, a bug was identified where the System was incorrectly triggering two of these suspensions in a specific scenario. When EP is elected on a single practice and the System determines that practice does not qualify for EP and there are acres keyed to both practices in such a way that EU could have applied had EU or EP been elected on both practices, the System triggers two suspensions. One stating the selected practice does not qualify for EP and another stating EP does not apply but EU does. This second suspension should not be received since EU never applies when EP is elected on a single practice. The EU/EP suspension logic has been updated so the suspension stating EP does not apply but EU does no longer triggers when EP is elected on a single practice. This suspension is only valid when EP is elected on both practices.

EU/EP: Enterprise Unit validation logic looks at all land IDs with acres across all detail lines on which EP is elected. The System then uses the acres and land IDs to determine if the EU/EP rules are met. For example, in order to qualify for EU, the lessor of 20 acres or 20% of total acres must exist in 2 or more unique land IDs. Or, 660 or more acres must exist in a single land ID. See the CIH for more information on enterprise unit qualification rules.

During internal testing of some recent changes around the EP unit structure, a bug was identified. The System was previously utilizing acres from both the parent and child option lines (e.g., SE) in the EU/EP validation logic. Since child options lines are duplicate acres of the parent line, these acres should not have been included in the EU/EP validation logic. The EU/EP validation logic has been updated to no longer use acres from child option lines in the determination.

EU/EP: In the 6.095 release with TFS #86089, a bug with the EU/EP validation logic was fixed. When EP was elected on a single practice and that practice did not qualify for EP, the System was setting the unit structure to EU rather than BU/OU when it was determined that the practice did not qualify for EP. During testing of this bug fix, a very specific scenario was identified that was causing this bug to still occur.

In addition, a second bug was reported with 2017 policies. When EP was elected on the coverage and the System has previously determined EP did not apply, but EU did, a second mark complete was removing EU and applying BU/OU.

The EU/EP validation logic has been updated to no longer apply EU when EP is elected on a single irrigation practice and the System determines the practice does not qualify for EP. In this scenario, the System will apply the underlying BU/OU unit structure. In addition, the logic for 2017 policies when EP was elected and the System determined EU applied has been updated to no longer remove EU.

Fast Edit AR: In the 6.090.0 release with TFS #69944, functionality was added to allow users to add a new APH in Fast Edit AR. During internal QA testing of this functionality, an issue was found around adding new APHs and Master Yield (MY) summary units. By design, once MY summary units are created, if changes are made to an underlying APH or a new APH is added, the System recalculates the MY summary unit and applies the MY to the new APH.

The issue found in Fast Edit AR was that when a new APH was created, the System was not recalculating the MY summary unit or applying the MY to the newly created APH. The Add New APH drawer logic in Fast Edit AR has been updated to recalculate the MY when a new APH is created and apply the MY to the newly created APH.

PIPE: An AIP reported that, for an ICE detail line, when changing the PIPE Price Election, it was not holding upon save of the line. A correction was made for PIPE policies so the user can now edit the PIPE Price Election and save the line and see the saved value.

SRC/ICE: A request was made for an enhancement to allow acres to import that have an approved HR Written Agreement attached to the detail line. When a Written Agreement is approved by RMA for HR ground to be rated as standard, there is a WA# that is in the line details of the detail line. The WA# number should be identified and added to the list of WA numbers that are acceptable to import the acres.