Release Notes 7.040.0

A request was received to provide more room for the grower to write in the Yield, Record Type, and Total Production fields on the Schedule of Insurance (SOI) / Production Report. This form has been updated in the following ways:

DRP: A Schedule of Insurance (SOI) has been implemented for the new Dairy Revenue Protection (DRP) Livestock product. For this, the System has been updated in the following ways:

A 2019 Special Provisions update was made available from RMA on 8/25/2018 with updates for the following:

The files were downloaded and implemented in the System.

A 2019 Special Provisions update was made available from RMA on 9/5/2018 with updates for Apples (0054) with APH (90) plan and Pecans (0021) with the Pecan Revenue (41) plan. The files were downloaded and implemented in the System.

LGM: LGM detail lines provide users with the ability to pre-key their target marketings and change them up until the detail line is submitted for approval through eDas. Agents should have the ability to go into a pre-keyed detail line and make adjustments as needed until the detail line has been submitted and approved by RMA. Previously, the Submit button was not displaying for agent users (admin users were not experiencing a problem) once the detail line was initially saved. The permission issue has been corrected so the Submit button is now displaying on pre-keyed LGM detail lines for agent users.

NOTE: For agent users, the Submit button will only display on LGM detail lines that have not been sent to and approved by RMA.

DRP: The following issues found during the initial round of Dairy Revenue Protection (DRP) testing in the 7.031 release have been resolved with this ticket:

DRP: The following issues found during the initial round of DRP testing in the 7.031 release have been resolved:

NOTE: Only Livestock Admin users can currently see these fields for LGM and LRP.

DRP: The System was previously allowing users to select Quarterly Insurance Periods (QIPs) that had not been published for a particular Effective Date (e.g., QIP 806 was not published with the 09-26-2018 TEST Daily Price File/Effective Date but users were allowed to select the 806 QIP and create a detail line which then did not rate). There were also instances when only one of the two pricing options (types) had rates within a selected QIP, so that dropdown needed to be limited by the QIP selected.

Code has been updated so the QIP dropdown will now only contain QIPs that were published for that particular Daily Price File/Effective Date, and the Pricing Option dropdown is now reflective of only those pricing options applicable to the selected QIP.

Margin Protection: Beginning with the 2018 Reinsurance Year (RY), RMA announced that Hybrid Seed Corn and Corn Silage are now insurable types under the Margin Protection plan of insurance in certain states/counties. This insurance will be offered under the Corn Margin Protection Policy using Type Code "009" for Hybrid Seed Corn and Type Code "026" for Corn Silage. Whether or not Hybrid Seed Corn and Corn Silage Margin Protection coverages will be considered standalone or if it can have a base coverage will depend on whether Seed/Silage is an insurable type for Corn in the State/County under YP (01) , RP (02), or RPHPE (03). If Seed/Silage is not an insurable type under YP (01), RP (02), or RPHPE (03) plans of insurance for Corn (0041) in the selected State/County, then the Hybrid Seed Corn and/or Corn Silage Margin Protection policy will always be a stand-alone policy, even if a Plan 01, 02, or 03 Corn policy exists for the same State/County. If Seed/Silage is an insurable type for Corn in the State/County under YP (01), RP (02), or RPHPE (03), then the Hybrid Corn Seed/Corn Silage Margin Protection policy can be associated with a base Plan 01, 02, or 03 policy and will be treated as a Margin Protection policy with a base coverage, including application of the premium credit.

Current System functionality allows for Margin Protection policies to be keyed using the new types of Seed and Silage. These coverages can currently be keyed as a stand-alone policy or as a related coverage regardless of whether the Seed/Silage type is insurable under plans YP (01), RP (02), or RPHPE (03) Corn in the state/county. In an effort to prevent users from incorrectly associating coverages that are required to be standalone, a validation was added to the coverage page. With this ticket, a validation was added that will prevent users from selecting the Related Coverage checkbox and selecting a related coverage on Corn Margin Protection coverages if the selected Type is "Seed/Silage" and Seed/Silage is not insurable under a Plan 01, 02, or 03 coverage in the same state/county.

Margin Protection: An issue was reported with Margin Protection detail lines not matching the detail lines on the base policy. By design, if a non-premium AR code is applied to a base coverage detail line, the System will create a zero-acre MP detail line. Non-premium AR codes are applied to each zero acre detail line for the unit. This could mean multiple zero acre non-premium AR lines when BU, OU, or even EP apply. Also by design, if EP or LP is elected and zero acres exist for either an irrigated or non-irrigated practice, a non-premium AR code is set on the practice that has zero acres, as required by RMA. The bug reported was that multiple unnecessary zero acre detail lines were created on the Margin Protection coverage. This issue occurred because, at one point, the unit structure on the base coverage was OU, which meant a non-premium AR code of "X" was applied to all detail lines with different unit numbers, and detail lines for all of these lines were created on the MP coverage. Later the unit structure changed to EU and the System removed the non-premium AR code from all but one line on the base coverage; however, the additional detail lines were not removed.

The logic that creates and updates Margin Protection detail lines for related Margin Protection coverages has been updated. The System will now remove any zero acre Margin Protection detail lines that do not have a non-premium AR code when the unit structure changes.

PRF: Beginning in the 2019 Reinsurance Year (RY), in addition to allowing different Coverage Levels by irrigation practice, which was added in 2016, RMA will also allow different Coverage Levels and/or Productivity Factors by organic practice (no organic practice specified, certified organic, and transitional organic) for PRF with an Intended Use "Haying (030)". PRF with an Intended Use of "Grazing (007)" will still be limited to one Coverage Level. With this ticket, the following changes have been made to 2019+ PRF policies when the selected Intended Use is "Haying":

NOTE: The default selection will be "No Organic Practice Specified".

NOTE: The default selection will be "No Organic Practice Specified".

PRF: Beginning in the 2019 RY, RMA has updated the PRF policy to allow different Coverage Levels and/or Productivity Factors by organic practice. Part of the current System functionality for PRF has some duplicate coverage validations, including a warning on save of the coverage and a mark complete suspension if the System finds more than one PRF coverage for the RY/State/County/Crop/Intended Use/Irrigation Practice. Now that coverages are also allowed by organic practice, this validation logic needed to be updated. With this ticket, the duplicate coverage validation logic was updated to allow multiple PRF coverages for the same RY/State/County/Crop/Intended Use/Irrigation Practice so long as they have different organic practices.

Policy: During internal testing a bug was identified with the functionality on the Add New Policy page that allows users to select a policy from the prior RY to effectively roll to the new RY and create the new coverage using the policy number from the prior RY policy. After the user selected a policy and then selected a plan, the System was wiping out the selected policy. The logic that determines when to display the Select Policy dropdown was updated to only display once a plan code has been selected.

WFRP: A display issue was reported on the View WFRP Coverage page. If the Related Coverage checkbox was selected on the WFRP coverage, the System was displaying a message about related Margin Protection coverages on the View WFRP page. The logic that displays the message applicable to related Margin Protection coverages has been updated to no longer display on the View WFRP Coverage page.

Coverage: During internal testing, a display issue was identified with the Coverages grid on the Coverages tab of an MPCI policy. In one column, the System displays the Coverage Level and Price Election percent in a stacked column, but a display issue was found where the label for "Coverage Level" was no longer displaying—only the "Price Election %" label was showing. This display issue has been resolved, and the Coverage Level label is now displaying in the column header.

APH: A calculation correction was required to accommodate rules outlined in exhibit P11 for Plan Codes 01, 02, and 03. Page 10 of the calculations identifies the calculation for the Current and Prior Year Yield ratio when the CUP (Yield Limitation Code of "03") applied in the prior year and the YC applies in the current year (Yield Limitation Code of "16"). The System was using the Rate Yield rather than the Approved Yield in the calculation of the ratio, which resulted in slight premium differences between the System calculated premium and the RMA expected premium.

The rating engine has been updated to match Exhibit P11-1. A query was run against 2018 to identify all APHs that are Plan 01, 02, 03 and have acres greater than "0" with an associated APH that has a Prior Yield Limitation code of "03" and a Current Yield Limitation code of "16". AIPs with policies in error will be required to resave the detail line to pull in the current rating calculations.

Fast Edit CLU: CLU acreage is allowed to be reported to the hundredth of an acre while the detail line acreage is allowed to be reported to the tenth of an acre. The Fast Edit AR grid, at save, has logic in place to round summed CLU acres to the tenth of an acre when the detail line is updated. It was determined in September that the rounding logic wasn't getting applied as it should have when acres were updated through the Fast Edit CLU page, and the acres were actually being pushed to the detail line from the Fast Edit CLU with acres to the hundredth. A re-save of the 2018 RY detail lines will properly invoke the standard rounding to the tenth.

Fast Edit CLU: Users reported that on the Fast Edit CLU page, the thumbnail images of the fields were not displaying. This issue has been corrected.

NOTE: An image of the field will only display if that field can be found on the current CLU Layer. If the field does not exist on the CLU layer, the System cannot retrieve an image of the field.

Master Yields: In TFS# 74503, a change was implemented for 2018+ APH Yield years where the Production Type record was to become a required selection for the APH. In the validation process for this required selection, Master and PTY Summary Units were not omitted from this validation. Since this validation was not being skipped, it was causing the Approved Yields to not calculate on MY and PTY Summary Units. With this ticket, the validation was updated to skip Summary Units for MY and PTY so that the Approved Yield will calculate. The validation will continue to apply to all underlying units.

Plan 90: A bug was found in the rating logic for Plan Code 90 where, when the TA option applies to the detail line, an incorrect Unit Discount Factor was being applied in the calculation. When completing the lookup for the Unit Discount Factor, if one was not found using a record category code, the lookup needed to search for the factor without a record category code; changes were made to Section 16 of the M13 calculations.

To help identify policies that may be impacted, a query was run of all Plan Code 90 coverages with acres greater than "0" and the TA option on the detail line. AIPs will be required to recalculate the premium line/APH (using the Additional Functions option) post-deployment of this correction. Premium may or may not change, but for those coverages and lines that did change, the system is now matching RMA's expected premium and cost estimator.

Coverage: This is a continuation ticket from TFS #92961. It was found during the final stages of the 7.030 release that the value for the "Coverage Status" was still not being retained in the event of a hard validation, and it appeared an invalid error was being returned. If a hard edit was returned that presented on the save of the page and then the Coverage Status was corrected, the System returned an error about a duplicate coverage.

The scope of this ticket was the final clean up of functionality to ensure that no data values are lost nor invalid errors returned when the Add New Policy or Add New Coverage pages trigger a hard validation error.

WFRP: An issue was found on WFRP policies where the System was displaying calculated Simple Averages, Historic Averages, Indexed Averages, and Expanded Operation Averages for revenue and expenses on the Income/Expense Record when the policies had not been updated or saved in any way in the current RY. The Income Expense logic for WFRP has been updated to no longer display calculated values until the policy has been updated and saved in the current year.

VIP: VIP will be introduced as a new Private Product for Hudson in 2019. This ticket allows for users to create VIP policies and import acres from the associated MPCI policy through the Submit Acreage/Mark Complete process.

It was discovered that the functionality on the Batch Reports page (Reports > Private Product Reporting > Batch Report) that allows a user to Print Zero Acre Premium Lines was not working correctly. Premium lines with zero acres were still printing on the SOI form when this print functionality was NOT selected. The Private Product Batch Printing functionality was updated to only print SOI forms with zero acre premium lines when the "Print Zero Acre Premium Lines" option is selected.

MPowerD: The Confirmation of Coverage for MPowerD policies was not displaying the Protection Factor data correctly when acres were submitted. The COC form was updated to display the same data on the user interface. Data will match regardless of whether acres have or have not been submitted.

Fast Edit: A bug was found where, when duplicating a line in Fast Edit and then saving, all lines but the duplicated line were being selected and saved. The System was updated so that when a user enters information and selects save, the line will have the green checkmark beside it, indicating it was completed.

Roll: An enhancement was done to the Private Products roll process so that, when the user is in a Private Product policy and selects to delete a detail line, the user will now be given the option to keep the detail line for next year. Upon selecting to delete the detail line, a checkbox will display that the user can select in order to have the line roll to the next year (when policies are rolled).

Crop Hail: When using the Batch Add Coverage feature on stand-alone Crop Hail policies, the Application/Effective Date entered through the Batch Add Coverage feature was not holding upon save to the policy page. The Additional Coverage Line was duplicating the Application/Effective Date from the original parent line at all times. If the Batch Add Coverage is using a date that is different from the parent line, the Application/Effective Date will reflect the date entered through the Batch Add Coverage feature.