Release Notes 9.015.0

Special Provisions: 2021 LRP Special Provisions were updated and made available from RMA on June 26, 2020. The following Special Provisions for 2021 have been implemented in the System:

Special Provisions: 2021 DRP and LRP Special Provisions were updated and made available from RMA on April 15, 2020. The following Special Provisions for 2021 have been implemented in the System:

Sales Period Begin Date 7/20/2020

LRP Effective Dates (Not Yet Available)

MPCI Application: It was found that there was a blank extra page printing after Page 1 of the MPCI Application when the Remarks field got close to the Page 1 Legend. This has been corrected. Additionally, other changes were made, including this update to County Election:

If the form is printed pre-filled AND pre-print for next year has not been selected:

Applications: The "Include Cancelled Coverages" print option (added with TFS #114380 in the 8.115 release) was updated to default as unselected. This change is for all years and applies to the following application type of forms:

Crop Provisions: With this ticket, Canola and Rapeseed Crop Provisions were implemented in the System for the 2021+ CYs. 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.

Crop Provisions: With this ticket, the Quarantine Endorsement Crop Provision has been implemented in the System for the 2011+ RYs. 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.

SOI: MCT received an enhancement request for the Schedule of Insurance (SOI) for Annual Forage, Apiculture (API), and PRF to reflect revisions in acres or colonies that occur due to interval based claim payments. The following updates have been made to the SOI for all years:

API / PRF SOI Updates

Annual Forage SOI Updates

Performance Optimization: It was found that pre-compiling razor pages helps the form Print Options load faster on the policy Print tab when the user selects a form (e.g., application, combo form, etc.). Pre-compiling has been added to razor pages in the System for all Crop Years to improve the loading time of the form Print Options on the policy Print tab.

Users reported that the TX survey layers were no longer displaying in the Mapping module. This has been fixed.

Users reported that, for specific policies, the format of the unit number was being stored with only the basic unit number and not the optional unit number. It appears it was stored that way on sync from ACRSI. This has been corrected so that the basic and optional unit numbers display correctly.

Raisins: When a Final Tonnage Report is filed for Raisins in March of each year, there are times when the farmer may file a Final Tonnage Report where the estimated acres are greater than zero but the final tons keyed equals zero (i.e., they elect to "go green", which means they harvest the grapes as table grapes instead of making raisins, so there is zero final tons). These policies were being included in the Unprocessed Final Tonnage Report (MPCI Reporting > Unprocessed Reports > Final Tonnage) as there was no way to indicate they were intentionally reported with zero final tons. So, users needed a better way to identify incomplete policies when producers decided to harvest "green" and file a "0" Final Tonnage Report.

With this ticket, a new Final Tonnage Report checkbox was added on the View and Maintain Detail Line page. This new checkbox will help to further identify those unprocessed policies that are incomplete by helping users distinguish between intentional 0 final tonnage and incomplete coverages. Now, only those coverages that don't have the Final Tonnage Report checkbox selected and where estimated acres are greater than zero and the final tons are equal to zero will be pulled into the unprocessed report.

NOTE: TFS# 117958 has been opened and will address the addition of the Final Tonnage Report checkbox in regards to the Unprocessed Final Tonnage report.

An AIP reported that the following P14 keys were transmitted to RMA on some new fall Margin Protection (MP) coverages that they entered last year (for the 2020 RY) before the related coverage information was applied: Associated Policy Producer Key – Field 47 and Associated Insurance In Force Key – Field 48.

In these scenarios, the related coverages existed on 2019 RY policies that had not rolled yet, so when the new MP policies were created, they were tied to the prior year policy in order to allow the relationships to be established once the related spring coverages rolled. However, once the related spring coverages rolled, the Associated Insurance In Force Key that was initially established changed. This change caused RMA errors because once the initial Associated Keys are established, PASS doesn't allow them to change.

It was determined that the standard Policy Producer Key and Insurance In Force Key values from Fields 4 and 5 on the new MP Coverage (i.e., P14) were incorrectly being sent in Fields 47 and 48 when the new Margin Protection policy was created in 2020. This was because the Related Coverage checkbox was selected when the new policy was created but a related coverage wasn’t actually selected because it hadn’t rolled yet. Once the related coverage did roll, it was applied to the new MP coverage and the correct Associated Insurance In Force Key was populated in Fields 47 and 48. But, again, this caused PASS errors because the keys cannot change once initially submitted.

NOTE: The Associated Key values in P14 Fields 47 and 48 are only transmitted when the Related Coverage flag is selected.

The following changes have been made to resolve this issue for Margin Protection with a Related MPCI Coverage:

NOTE: The same changes will not be implemented for Related Coverage functionality that currently exists for STAX and WFRP plans because there is other functionality that could be impacted and the underlying issue that is being fixed for MP doesn't seem to be an issue for the other plans.

HIP: RMA recently released a Q & A document pertaining to HIP in conjunction with Nursery (FG & C) and Nursery Value Select (NVS). Due to the clarifications received in the document, a few changes were made to the System's HIP functionality for the Nursery and NVS commodities.

With a previous ticket (TFS #117241), HIP functionality was updated for Nursery and NVS to allow users to elect HIP with one Practice but not the other if both Container and Field Grown Practices were set up for a Type. The System will remove the validation and Mark Complete validations upon save of coverages when the commodity is "Nursery" or "NVS" and the insured has the same Type insured under both Field Grown and Container Practices. During UAT of that ticket it was found that not all scenarios were accounted for. This ticket fixed that gap in logic.

PRF & Apiculture: A request was received to improve the workflow around adding AR Sign Dates for PRF and Apiculture. Previously, in order to apply AR Sign Dates, the user had to navigate to the legacy Signature Maintenance page to apply AR Sign Dates for PRF and Apiculture. To avoid this additional step, with this ticket, the AR Sign Dates fields on the detail line for PRF and Apiculture have been updated to display in edit mode rather than read-only format for the 2020+ RYs. The following logic applies to this new functionality: