Release Notes 6.040.0

eSign: The 306 Acreage Report has been modified and enabled for use within the eSign Wizard. For this form, the eSign Wizard will:

PAIR: The Pre-Acceptance Inspection Report (PAIR) was updated with the 2018 DSSH requirements and the Agency DBA was added to the form.

PAIR: The Crop Addendum Worksheet (CAW) currently prints with the Pre-Acceptance Inspection Report (PAIR) for 2017 and prior Crop Years (CY). The 2018 DSSH incorporated the individual CAWs into the updated PAIR requirements so CAWs no longer need to print with the PAIR for the 2018+ CYs. With this ticket, no CAWs print with the PAIR for 2018+ CYs.

Perennials: While testing TFS #71580 in the 6.030 Release, a few clean-up items were identified on the HTF / HTT PAW format:

The HTF / HTT PAW format was updated to have the correct Legal Description legend indicator and to remove the main PAW legend from this format.

ProAg's Lexington office moved locations the first week of October 2017. The new location needed to be referenced on their forms and reports. The new address for their Eastern Region Forms is:

2530 Sir Barton Way, Suite 125

Lexington, KY 40509

The phone and fax numbers will remain the same. This update is applicable to all Reinsurance Years.

PRF/Apiculture: It was found during testing TFS #52329 in the 6.035 Release that on the Schedule of Insurance (SOI) for PRF that in the Crop Summary and Premium Summary sections the Irrigation Practice data was being pulled from the Detail Line. If there was no Irrigation Practice data on the coverage line, then no Irrigation Practice should have printed in this scenario in the Crop Summary and Premium Summary sections. The SOI for PRF was updated in the Crop Summary and Premium Summary sections to have the Irrigation Practice data print from the coverage line, and if there is no Irrigation Practice data on the coverage line, then no Irrigation Practice prints in this scenario in the Crop Summary and Premium Summary sections. These changes apply to all Crop Years in all locations the MPCI SOI can be printed.

PRF/Apiculture: Previously, the Schedule of Insurance (SOI) for PRF and API was not always printing the correct acres and colonies. It was discovered that the SOI was doing a sum of each unit's acres instead of pulling the Index Interval's total Insured Acres and, depending on how the unit acres were rounded, it could skew the sum. With this ticket, the SOI for PRF and API were updated to print the Index Interval's total Insured Acres.

A Special Provisions update was made available from the RMA. Four files were downloaded. Special Provisions for 2018 have been downloaded to E:\RMA Import\SPOI\2018: 2018_SPOI_0630.zip, 2018_SPOI_0831.zip, and 2018_SPOI_1031.zip.

A 2013 ICE update has been completed in the System. The following table has been updated for 2013:

A 2014 ICE update has been completed in the System. The following table has been updated for 2014:

A 2016 ICE update has been completed in the System. The following table has been updated for 2016:

A 2017 ICE update has been completed in the System. The following table has been updated for 2017:

A 2018 ICE update has been completed in the System. The following tables have been updated for 2018:

A 2015 ICE update has been completed in the System. The following table has been updated for 2015:

Performance: MCT continues to strive to identify and implement performance optimization changes when possible. With this, a change was made to the manner in which policies load to the UI. Historically, when a policy loaded, the Policies tab (which lists all policies for the grower) and the Detail Lines tab (for the first coverage on the policy) loaded along with the policy searched for. As such, there was a wait time associated with loading all of the data on the page on the initial load of the policy, especially if the user never navigated to the first coverages' Detail Line tab or the Policies tab. So, a change was made to the manner in which a policy loads after a search. Now, only the Coverages tab will be loaded, and the other policy tabs will load when a user makes a selection to view that set of data.

Policy: Previously, on the Maintain Commodity page for Whole Farm Revenue Protection (WFRP) policies, to navigate between commodities, users had to Cancel or Save & Exit from the Maintain Commodity page, return to the Commodities tab, and then select the link to open the next commodity line. A request was received to implement better navigation between commodities on WFRP policies. To maintain System consistency, this navigation will be similar to that used on MPCI policies for detail lines and APHs. This includes Next and Back buttons as well as a dropdown of all commodities to allow users to navigate between commodity lines.

Quotes: A bug was identified with SBI validations when converting a quote to a policy. When converting a quote to a policy, the System checks to see if the policy has the minimum number of SBIs required based on the grower’s Entity Type and Tax ID type. The System uses RMA's ICE Table "Entity Type Primary Producer SBI" (D00020) to determine the minimum number of SBIs based on the grower’s Entity Type and Tax ID type. This ICE table includes a record for each SBI Entity Type and Tax ID type that is valid for the grower’s Entity Type and Tax ID type. In addition, each of these records includes a minimum number of SBIs required.

Prior to 2018, the minimum SBIs required in this ICE table was "0" for all entity types. However, beginning in 2018, RMA updated the minimum SBI count for grower entity types of "J", "P", "R", and "X" from "0" to "1". This update occurred with the July PASS release. Following this update, users began receiving errors when attempting to convert a quote to a policy for growers with entity types of "J", "P", "R", and "X".

The reason for these errors was that the System was looking for at least one SBI record (based on the new minimum SBI required in the ICE Table) that matched the SBI Entity Type and SBI Tax ID type for every single record in ICE D00020 for the grower Entity Type and Tax ID type. The System should have been looking for at least one SBI record total rather than one SBI record for each Entity Type and Tax ID type combination in the ICE table. The SBI validation logic that triggers when converting a quote to a policy has been updated to require at least one SBI record total rather than at least one record for every Entity Type and Tax ID type combination in the ICE table.

WFRP: In the 2018 RY, PRF ADMs added more intervals (practice codes) with the introduction of organic, organic transitional, and other practices to the standard irrigated/non-irrigated practice codes. To aid agents and AIPs processing WFRP, the practice codes were added in parentheses next to the different intervals on the detail line as well as next to the interval on the View Detail Line grid.

WFRP: MCT has received an enhancement request for the ability to key estimated MPCI Liability on WFRP policies. AIPs are requesting this functionality because the Intended Farm Operation Report is keyed on or around the WFRP Sales Closing Date of 2/28 or 3/15 and MPCI acres are not keyed until July. Given this, the final MPCI Liability amount is not known at the time the Intended Farm Operation Report is keyed.

The existing MPCI Liability field cannot be used to key an estimated value since existing functionality related to this field ties into the MPCI policy. When acres are keyed to the MPCI policy and the coverage is marked complete, the System will update the MPCI Liability value on the WFRP policy so long as the value has not been overridden by a user. To key an estimated value in this field, the user would have to apply the override, at which point the System would never push the actual MPCI Liability to the WFRP policy once the MPCI acres are keyed because the override would be applied.

To accommodate this request, a new UI and database field for "Estimated MPCI Liability" was added to the Income & Expense Record with TFS #67311 in the 6.035 Release. If a value is keyed in this field, the System will use it as the MPCI Liability in the premium and liability calculations. When an Estimated MPCI Liability is being used in the premium calculation, the Estimated MPCI Liability entered in the Estimated MPCI Liability field on the Income & Expenses page is printed in the MPCI Liability field on the SOI in the Premium Summary section and "Estimated" prints under that value. Once an actual MPCI Liability value is applied, the System will use the actual MPCI Liability in the premium and liability calculations.

This ticket implemented changes to the Schedule of Insurance (SOI) WFRP format to use the Estimated Liability amount when applicable. All changes apply to the 2018+ RYs only.

Acreage Type: Beginning with the 2018 RY, RMA has added a new procedure that allows growers to select to exclude acreage damaged by an unavoidable uninsured fire (UUF) and/or a third party. When a grower makes this election, the acreage report must be updated to indicate what acreage was damaged by an unavoidable uninsured fire (UUF) and/or a third party.

NOTE: This requirement is waived for 2017 UUF/Third Party Damage acreage. RMA has added a new acreage type of "K – Unavoidable Uninsured Fire or Third Party Damage" to the Acreage Type ICE Table (ICE D00142) to account for reporting of UUF/Third Party Damage acreage.

This new acreage type of "K" is already displaying in the System since the ICE table has been updated; however, a description was not displaying. With this ticket, a description was added to the "K" acreage type that displays on the detail line, detail line drawer, and CLU grid.

Claims: The System does not allow MPCI policies with paid claims to be canceled. If the user attempts to a cancel a coverage with a paid claim, an error message will display. During internal testing, it was found that this error message was displaying as simply “error” and did not provide any additional information to the user. With this ticket, this error message was updated so that it informs the user why the coverage cannot be canceled.

Margin Protection: When standalone Margin Protection functionality was originally implemented, RMA had indicated an APH would apply. However, they later changed this and decided the Trigger Margin would be used in place of an Approved Yield for standalone Margin Protection.

While it wasn't used for anything, a link to the APH pages was previously available on standalone Margin Protection policies, and users could potentially add an APH. With this ticket, the APH link was hidden on the Detail Lines tab to prevent users from creating an APH. This applies to Plan 16 standalone Margin Protection for 2017+ RYs and Plan 17 standalone Margin Protection for 2018+ RYs.

Margin Protection: Beginning in the 2018 RY, RMA is adding a Harvest Price Exclusion plan for Margin Protection. This will be Plan 17, and aside from the Harvest Price Exclusion, will work the same as Plan 16. In order to allow processing of standalone Plan 17 detail lines, the existing standalone Plan 16 detail line functionality will be expanded to include Plan 17. The existing standalone Plan 16 detail line functionality has been expanded to Plan 17. This includes:

Quotes: AIPs have an approved list of states in the AIP preference table based on the Plan of Ops they filed with the RMA. The approved states is leveraged in the State dropdowns on the Add New Policy and Add New Coverage pages. It is not, by design, leveraged on the quote's dropdown for State. The reason for this difference on the quote side of the System is because Private Products (which often must be tied to an MPCI quote if unsupported by an MPCI policy) do not have to follow the same "approved state" guidelines as MPCI. In addition, the System is designed to offer flexibility for AIPs wishing to expand their footprint in the industry by adding new states to their territory. So, the System will allow agents to enter quotes to later convert to a policy while an expansion is being approved.

With this ticket, new validation was added during the "convert quote to a policy" process to ensure no quotes are converted unless they fall within the approved AIP state listing. This prevents the possibility of a policy being created in a state that has not been approved for an AIP.