Release Notes 8.000.0

SOI: The format of the Schedule of Insurance (SOI) was updated to implement that same format for the eZ-Hail and Production Hail Detail Lines and Premium Summary Section(s) that print when those products are linked to an MPCI policy. As such, the vertical borders and bolding were removed, and the Product, Policy Form, Est. Acres, and Net Premium font was made larger to help those important items stand out on the SOI. Additionally, the borders and shading were removed from around the Premium Summary section title. These changes apply to all Reinsurance Years.

RMA released updated Annual Forage crop provisions for the 2020 and succeeding Crop Years (CYs). These have been updated 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.

SOI: The Schedule of Insurance (SOI) has been updated with this ticket to make it easier on the eyes for scanning/reading and to have four important data items stand out for the Grower: Crop, Unit, Acres or Tree Count, and Insured's Premium. There are currently 10 11 different formats of the SOI (see below). Formats 1, 2, 3, and 1011 were not updated. Formats 4, 7, 8, 9, and 10 4, 7, 8, and 9 will be using this new SOI format.

The following updates were made to the SOI for all years:

VFR Application: The Veteran Farmer Rancher Application (VFR App) was added as a new form with TFS #101657 in the 7.110 release. With this ticket, a new MPCI Policy Attachment Type, "VFR Application", has been added. This Attachment Type should be used when the VFR App is attached via an individual MPCI policy as well as when the form is Batch Scanned.

SOI: MCT was notified that STAX related coverage acres were being included in acre totals in the Crop Summary and Premium Summary on the Schedule of Insurance (SOI). The following changes have been made to this form for all Crop Years:

No version date was updated with this ticket, as this was only a data update.

An enhancement request was received to update the Increased Coverage Election (ICE) Confirmation of Coverage form. The column header labeled "Percent of Available Price" was updated to read "Liability Factor".

An issue was reported where, when a user was printing the Private Products Policy Register (Reports > Private Products Reporting > Policy Register), a red error message was being received. A correction was made to the Private Products Policy Register so that once a user prints the report, they no longer receive the red error message.

Rx Warranty: Rx Warranty is a new product offered by the AIP. This ticket implemented the Confirmation of Coverage form to accommodate Rx Warranty policies. This form is available on the Print Forms tab within an Rx Warranty policy and when Batch Printing or printing from the Print Private Product Blank Forms menu.

An issue was found internally while testing the 2020 RY changes for LRP (Plan 81). One of the changes introduced for the 2020 RY is to now include all 50 states for the LRP coverage. During testing it was found that the Entity State dropdown was not populating with all 50 states, but the Policy State dropdown was. Due to the layout of the fields on the Add New Livestock Policy page, the user was not selecting the RY until after they had selected the Entity State. As the RY had not been selected, the System did not know how to populate that dropdown. Since the Policy State field was after the RY selection, the System was populating that dropdown correctly with all 50 states.

With this ticket, the field layout on the Add New Livestock Policy and Add New Livestock Quote pages has been updated so that the user must first select the RY. This will ensure the state dropdowns are populating as they should be. This change will only affect the Add New Livestock Policy and Add New Livestock Quote pages but not the Add Livestock Coverage page as the RY is already set on that page based off of the RY of the policy. The state list dropdown logic was also updated to now only call the db once to populate both the Entity State and the Policy State fields to increase System performance when loading the page.

DRP: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 83 – Dairy Revenue Protection (DRP) with PM-19-022. The following items have changed for DRP for the 2020+ RYs:

NOTE: Changes called out in this ticket are specific to Plan 83 – Dairy Revenue Protection (DRP) only.

LGM: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 82 – Livestock Gross Margin (LGM) with PM-19-023.

For 2019 and prior RYs, regulations were in place on the amounts of insurance insureds could have on the various LGM commodities. For the 2020+ RYs, the following limitations have been removed:

With this ticket, limitations have also been added to the monthly Target Marketing fields as follows to prevent "Sorry..." errors from being thrown now that limitations by RMA have been removed:

NOTE: Changes called out in this ticket are specific to Plan 82 – Livestock Gross Margin (LGM) only.

LRP: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 81 – Livestock Risk Protection (LRP) with PM-19-024. The following changes have been made to system logic for the 2020+ RYs for Plan 81 – Livestock Risk Protection (LRP):

NOTE: Changes called out in this ticket are specific to Plan 81 – Livestock Risk Protection (LRP) only.

An issue was found internally while doing regression testing on a Dairy Revenue Protection (DRP) ticket. If an SBI was set to Out of Compliance on a DRP policy, the Subsidy Reduction value was not being calculated. After doing research, it was found that LGM and LRP policies have a field on the SBI pages called "Livestock SBI Share". This field was being used in the Subsidy Reduction calculation when SBIs were set to Out of Compliance. The field that should have been used in the Subsidy Reduction calculation logic was the "SBI Share" field as it is called out to be used when SBIs are Ineligible or Out of Compliance. Since the SBI pages on DRP policies do not have the "Livestock SBI Share" field, there was no way to get the Subsidy Reduction calculation to be applied.

With this ticket, the Subsidy Reduction Factor calculation when Out of Compliance SBIs exist on Livestock policies has been updated. The calculation logic will now use the "SBI Share" field and not the "Livestock SBI Share" field. This will also maintain consistency with MPCI logic. This change is applicable for all three Livestock plans (81, 82, & 83).

NOTE: LGM and LRP policies will still need the "Livestock SBI Share" field populated as that field gets transmitted to eDas. If an LGM or LRP policy has an Out of Compliance SBI, both the "SBI Share" field and the "Livestock SBI Share" field will need to be populated with the SBI's applicable share.

Annual Forage: Beginning in the 2020 Reinsurance Year (RY), RMA has made a number of changes to the Annual Forage (0332) policy. These changes include:

With this ticket, the coverage pages for Annual Forage have been updated to allow selection of the DU option on Growing Season 1 coverages only, if it is available for the RY/State/County/Crop. In addition, the Annual Forage detail lines pages have been updated to allow selection of the DU option if it is elected on the coverage. Finally, the detail line page has been updated to allow an intended use of Grazing when the coverage level is CAT.

NOTE: When the DU option is elected and applied to a detail line, a reduced County Base Value (CBV) applies to the premium calculation. TFS #103939 will address the necessary rating changes in a future release.

Enterprise Units: In December 2018, RMA issued a Q&A that included a question around prevented planting (PP) acres and how the acres are counted in relation to the 20/20% rule for Enterprise Units. The 20/20% rule requires the lesser of 20 acres or 20% of total acres exist in two or more unique land IDs or multiple land IDs that can be aggregated together to meet this 20/20% rule. Previously, Enterprise Unit procedures required only planted acres could be used to determine if the 20/20% rule was met and to determine the EU discount factor. Through the December 2018 Q&A, RMA clarified that total planted acres for purposes of the 20/20% rule should be determined using all acres, planted and PP. Previously, the System was using planted acres only to determine total acres for purposes for the 20/20% rule.

With this ticket, the Enterprise Unit validation logic was updated to include both planted and prevented planting acres when determining total acres for the coverage for the purposes of the 20/20% rule. The System will continue to use planted acres only when determining the number of acres in each unique land ID for the purposes of the 20/20% rule as well as when determining the Unit Discount Factor. This change has been implemented for the 2019+ RYs.

NOTE: A query was provided to each AIP with a list of policies where EU/EP is elected on the coverage and one or more detail lines reflect a prevented planting status. These policies will need to be marked complete following the 8.000 release.

RMA announced a change to the premium calculation for Plans 01, 02, 03, and 90 for the 2018+ RYs in mid April. CR 16778 modified the premium calculation for both RYs when the prior year and current year yields had a CUP applied. RMA deployed this change to production in their May production release.

This change has been discussed in detail on the All AIP calls as well as in the PASS Status Report from RMA. For the 2018 RY, recalculation of premium will be required (and possibly corrected claims) to refund overpaid premium. For the 2019 RY, the recalculation of premium will occur prior to any billing or claim processing.

Companion Policy: Logic is needed at the premium line level with the Companion Policy functionality to account for claims processing. There will be times that the System will need to temporarily block the established link without breaking the permanent link, which rolls from Reinsurance Year to Reinsurance Year. The Claims Team will be updating the existing MPCI Claims functionality to account for the temporary companion link blocks when claims are processed on either the Source Policy or Companion Policy when acreage report revisions apply. They will set new database codes within the CompanionLink database field of the MpciPremiumLine DB table with TFS #102190. This ticket will be adding the two new CompanionLink database field codes for the MpciPremiumLine DB table as well as updating the current companion policy syncing logic to be used once the codes are set in the database tables by the claims logic.

NOTE: The changes listed below will only take place when the Source Unit and/or Companion Unit(s) have a claim processed during the applicable RY and acreage report revisions are applied. If the Source Unit and/or Companion Unit(s) have a claim but no acreage report revisions are applied, no changes will be made to the existing companion links. MPCI Claims logic will set these new values at a premium line level when claims with acreage report revisions are being processed.

Allow the following Companion Flags to be applied in the MpciPremiumLine.CompanionFlag field:

Before establishing any new companion links, the System should first determine if the Source Unit already has a BS value set in the MpciPremiumLine.CompanionFlag field.

NOTE: TFS #102741 has been created to update the MPCI Policy Roll logic to convert the temporary companion link blocks put in place with the new BS and BC database values so standard companion policy syncing will resume for the new Reinsurance Year.

Enterprise Units: During internal testing of enterprise unit functionality, a bug was identified with the Malt Barley Endorsement (ME Option). Previously, when the ME option was applied to the detail line, the System didn't apply EU or EP unit structure. Per RMA, EU/EP are valid unit structure options under the ME option. Given this, the System should allow the EU or EP unit structure codes when the ME option applies. The System has been updated to allow EU or EP unit structure when the ME option applies.

Fast Edit AR: With TFS #98646 in the 7.100 release, logic was added to only allow a contract price to be selected in Fast Edit AR if the CP option was on the detail line. Since there are certain crops, including Contract Seed Peas and Contract Seed Beans that allow or require a contract price but the CP option is not available in the ADMs, this change resulted in users no longer being able to apply a contract price through Fast Edit AR for these crops that the CP option is not available on. Currently, there is a warning in place within Fast Edit AR for crops that require a contract, like Contract Seed Beans and Contract Seed Peas, but for which the CP option was not available. This warning helps to identify these crops but does not identify the crops that require the CP option.

Due to the CP option not being available for certain crops that require a contract price, the logic previously implemented with TFS #98646 that prevented the display of the contract price in the contract info dropdown if the CP option was not selected was removed. Now, a hard edit requires the CP option to be selected if it's elected on the coverage and the user has selected a contract price but not the CP option in Fast Edit AR.

With TFS #69353, validations were implemented for the Maintain Detail Line page as well as Fast Edit AR to ensure that an NI Practice always reflected a Solid Pattern and an NI-SR Practice always reflected a Plant Pattern of something other than Solid if the reported acres value for the detail line was greater than zero and insurable.

An enhancement was requested on the Maintain Detail Line page so that when the crop practice equals Non-Irrigated, the Plant Pattern can ONLY equal Solid. Previously on this page, the user was able to pick a Planting Pattern other than Solid, and upon Save and Exit, the System did not throw an error that this was incorrect. It appeared as if the data was saved; however, when the user re-entered the Maintain Detail Line page, the System had correctly set the Planting Pattern to Solid and Skip Row Factor equal to 1.00. If a user within the Maintain Detail line selected Save, the System corrected the Plant Pattern to equal Solid. In Fast Edit AR, if the crop Practice was equal to Non-Irrigated, then the System had already set the Plant Pattern to equal 1.00 and this was read-only; the user was not able to change this information. Also, if the crop Practice was equal to Non-Irrigated Skip Row, if the user tried to select a Solid plant pattern, a hard edit was received and the user had to correct it before being able to continue.

With this ticket, a hard edit was implemented within the Maintain Detail Line page so that if the crop practice is Non-Irrigated, then the Plant Pattern can only be equal to Solid. If anything other than Solid is selected upon Save or Save and Exit, the user will receive a hard edit stating "A planting Pattern of Solid is required for Non-Irrigated Cotton".

Companion Policy: An issue was identified internally while testing the Companion Policy Claim Logic related to a different ticket. If the APH had not been updated on the companion policy's detail line prior to the acres being added on the source policy's detail line, the child line(s) on the companion policy was not updating as expected—no APH was linking, even after manually updating the parent line's APH. With this ticket, Companion Policy functionality was updated to ensure that both the parent and the child detail lines are getting updated if the APH is updated and/or changed when companion links exist. This will happen if the APH is updated on either the source policy or the companion policy.

Companion Policy: An issue was identified where manually-created child lines on companion policies were getting set to "Uninsurable". This was happening when acres were added to a source policy and data was then synced to the companion policy. The acres on the manually-created child line on the source policy were being changed to Uninsurable. The APH OID on those new companion child lines was missing and premium line calculation did not happen. With this fix, those child lines will now get the APH OID of the parent line and the calculation will occur.

NOTE: TFS #104497 has been created for an issue found when the APH on the companion policy was not updated prior to the acres being added on the source policy and the data sync occurring.

MCEU: During internal testing, a bug was identified with MCEU functionality. MCEU procedures require that the primary county qualify for the EU/EP election on the coverage and the secondary county NOT qualify for the EU/EP unit structure election on the coverage. The bug identified occured when EP unit structure was elected on both irrigation practices. If acres were keyed in such a way that the secondary county could have qualified for a single enterprise unit (EU unit structure), the System was determining MCEU did not apply. However, since EP was elected on both practices, the secondary county could not qualify for EP on both irrigation practices in order for MCEU to apply. Because the secondary county would have qualified for a single enterprise unit (EU unit structure), that did not disqualify the coverages from receiving MCEU since EP was originally elected on both practices. MCEU logic has been updated so that the System will apply MCEU in the scenario described above.

Skip Row: Users reported an incorrect message when trying to key a 2x1 Narrow Skip premium line for Skip Row Cotton when using a Table 1 state (State Code of 01, 05, 12, 13, 22, 28, 29, 37, 45, 27, or 51). This has been resolved.

STAX: In the 7.105 release, an issue was found with TFS #98856 where the System was requiring SE to be applied to the STAX coverage in order for the detail lines to be set to Uninsurable; this shouldn’t have happened. The user should only have to select the "Enrolled in ARC or PLC" and have the STAX detail lines set to Uninsurable along with STAX SE IF SE is applied to the STAX coverage.

An AIP reported an issue where once a Private Product policy was canceled and the user was back in the MPCI policy on the Add/View Available Products page, if they selected the Edit Coverage link, they were able to add more coverage to the canceled policy. A change was made to the Add/View Available Private Products popup that is accessed from the MPCI side so that once a Private Product policy has been canceled, the Edit Coverage hyperlink will no longer display.

It was previously found that if the MPCI premium line was deleted and the associated Private Policy premium line was canceled, it was not showing in the grid if the user selected to show canceled lines. This issue was found while testing another ticket for ICE but could have affected any linked policy that displays the Crop Name with the Type in the premium line details grid. An update was made to correct the issue with canceled lines not showing up in the grid if the user has selected Show Canceled Lines.

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

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

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

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

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

A 2020 Special Provisions Update that was made available from RMA on 4/23/2019. The following Special Provisions for 2020 have been downloaded (2020_SPOI_0430.zip):

A 2020 RY Special Provisions Update was made available from RMA on 4/29/2019. The following Special Provisions for 2020 have been downloaded (2020_SPOI_0430.zip):

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

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

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

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

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

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