Release Notes 8.090.0

APH Database Form: An issue was found where System-generated child lines were printing on the APH Database form, and if AOI data had an ampersand, it was not printing on the form correctly.

Nursery: RMA has created a new pilot program, Nursery Value Select (Commodity 1010). This new pilot requires a Monthly Unit Value Plan (MUVP) form for each basic unit and is included with each Nursery Value Report (NVR) the insured submits. The new MUVP form is available to print from the MPCI policy Print tab and the Batch Printing menus and displays with the title of "Monthly Unit Value Plan". The form is available in the blank, pre-headed with agency only, and pre-headed with insured and agency / agent report styles, and its format follows base form standards and the example in the handbook. This form will be available for all years, but the System will determine when the Nursery Value Select pilot policies can be entered into the System.

Nursery: The Federal Crop Insurance Corporation (FCIC) released Nursery Value Select Pilot Crop Provisions. The changes are applicable for the 2020 Reinsurance Year / 2021 Crop Year.

Nursery: A new form, Nursery Value Report (NVR), was implemented in the System for use with acreage reporting for the new pilot program, Nursery Value Select. With this ticket, the NVR form has been updated in the following ways:

2020 Special Provisions were made available by the RMA and have been implemented in the System. The following Provisions have been updated for the 2020 RY / 2021 CY:

Enterprise Units by Cropping Practice: Beginning in the 2020 RY, for Soybeans and Grain Sorghum in counties with an 11/30 or later Contract Change Date and both an FAC (following another crop) and NFAC (not following another crop) practices available, RMA will allow Enterprise Units by Cropping Practice (EC Unit Structure). Several changes are being made in the System to accommodate this new unit structure. Enterprise Units by Cropping Practice will work very similarly to Enterprise Units by Irrigation Practice.

Functionality to elect EC on the coverage was implemented in the 8.085 release with TFS #112455. This release includes additional changes for EC functionality:

NOTE: MCEU is not available with Enterprise Units by Cropping Practice (EC) for 2020.

Updated Validation

With TFS #111155, the Enterprise Unit validation logic that occurs at Mark Complete has been updated for Enterprise Units by Cropping Practice. This includes the following:

If both practice qualify for an Enterprise Unit, the System will apply EC unit structure to the detail lines.

NOTE: See the Crop Insurance Handbook for more information on Enterprise Unit qualification rules.

Updated Manage Unit Structure Popup

With TFS #112460, the Manage Unit Structure popup has been updated to account for EC. This includes the following:

NOTE: This mirrors functionality for Enterprise Units by Irrigation Practice that displays separate rows for IRR and NI

Rating Logic

With TFS #112462, the rating logic was updated to account for the new EC unit structure. When applied, EC rating will follow the M13 premium calculation exhibits.

Suspensions

With TFS #112459, new suspensions were added to trigger when some form of Enterprise Units by Cropping Practice is elected on the coverage but the System determines during Mark Complete that the coverage/cropping practice does not qualify for the EC election on the coverage. The new suspension messages are listed below:

Hybrid Vegetable Seed: TFS #112814 removed the "Seed Company code required" validation from the Hybrid Vegetable Seed detail line. The M13 confirmed that the P11 (field 61) for Hybrid Vegetable Seed (0066) must be empty, so a Seed Company code is not required. The presence of the Seed Company dropdown on the detail line has been causing confusion for users. With this ticket, the Seed Company dropdown was removed from the Maintain Detail Line page if the crop is "Hybrid Vegetable Seed". This field must be retained on all other Plan 55 crops.

Perennials: During internal review of Caneberry functionality, a bug was identified with the APH Calculation for Caneberries. Caneberries are a lag year crop, so an 11th year displays in the APH for tracking purposes only and is not intended to be included in calculation of the APH. However, it was found that the System was incorrectly using the lag year when calculating the APH. This issue has been resolved.

NOTE: During testing of this functionality, an issue was identified with the record type validation logic where the System is displaying the hard error stating a record type is required when a record type is missing from an APH other than the one being saved. TFS #114362 has been set up to address this issue in a future release.

Hemp: When Hemp procedures were originally implemented, the P14 record required a Type. However, RMA changed their procedures with CR 213216 so that the P14 records for Hemp will no longer require a Type Code or a Class Code.

With this ticket, the validation logic requiring a Type upon save was removed. The coverage functions similarly to other mandatory type crops where a type is entered only if electing a different coverage level. This change impacts the Add New Policy, Coverage (Add/Edit/Maintain), and Quote (Add/Edit/Maintain) pages. A new message will display on those pages to notify users that "Selection of Type only applies when different coverage levels are elected."

As part of this ticket, a post-production script was run to remove the Type from any Hemp coverages added prior to the 3/26/2020 release date unless there are multiple coverages by Type with different coverage levels elected.