Release Notes 7.015.0

A request was received to add a new field to allow users to enter the State of Incorporation for Growers with an Entity Type of "Corporation" or "LLC". This new field was added to the System with TFS #86854 in the 6.100 release. The request also asked for the State of Incorporation data to print on the MPCI Applications if a state has been entered. The following forms were updates for the 2018+ Crop Years:

The following updates were made to the above forms for the 2018+ Crop Years:

An issue was reported where the MPCI Application / Cancel / Transfer / Production Report / Acreage Report / PAW / Policy Change Combination Form (i.e., Perennial Combo Form) was not able to be batch scanned. It was found that this was due to the left side of the QR Code being cut off by the Acreage Type Legend on the last page of the Perennial Combo Form. The location of the QR Code on the Perennial Combo Form has been updated so the left side of the QR Code is no longer getting cut off. This update was made for all years.

The MPCI Application has been updated for all Crop Years to print the Practice that is selected with the EP Unit Structure on the MPCI Application:

Irrigation format example: EP (IRR)

Non-irrigated format example: EP (NIRR)

Both format example: EP (Both)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

APH: In 2018, RMA added a new field to the P15A record for Production Record Type. This field was optional in 2018, but beginning in 2019, RMA will require a Production Record Type for APH years 2018+. A validation has been added to require a Production Record Type on the APH for yield years 2018+. This validation will trigger when a Yield Type of "A", "AY", "BF", "DA", "FA", "NA", "PA", "PW", or "WY" exists for APH years 2018+ and the user has not selected a Production Record Type Code. This validation applies to the following pages:

WFRP: A request was received to update the sort order of commodities on WFRP policies. The Commodities grid on the Commodities tab and the Commodities grid on the Fast Edit PR page have been updated to sort alphabetically by Commodity Name.

WFRP: A request was received to add the Commodity Description to the Fast Edit PR for WFRP. The Commodity Description field has been added to the Fast Edit PR for WFRP.

SCO: The current Supplemental Coverage Endorsement (SCO) procedures provide an insurance guarantee based on the gap between 86% of the expected area yield/revenue and the coverage level of the underlying policy. Beginning in the 2019 Reinsurance Year (RY), RMA is adding a Coverage Percentage election to the SCO endorsement. Growers will have the ability to choose a Coverage Percentage between 50 and 100 percent. The elected coverage percentage will be multiplied by the total guarantee to determine liability. This will effectively allow growers to elect to reduce the liability on the SCO endorsement and customize their coverage.

With this ticket, a new SCO Coverage Percentage field was added to the Coverage page. This field will only display if the SCO option has been applied to the coverage and will allow users to select a value between 50% and 100%, with 100% being the default value. In addition, the rating logic was updated to account for the new SCO Coverage Percentage. Finally, a script was run to populate the SCO Coverage Percentage to 100% for any existing 2019 SCO coverages.

NOTE: This ticket accounts for populating the new SCO Coverage Percentage field on any existing and new 2019 coverages; however, the value on coverages that have yet to roll to 2019 still needs to be populated. TFS #92308 has been set up to update the 2019 roll only to account for setting the SCO Coverage Percentage value on SCO coverages.

WFRP: RMA has modified the format for the P19A record and the scope of this ticket is to match their new layout that deployed to production on 7/11/18. The precision will change on the Intended and Revised Expected Value Amount, the new value will be 99999.999 (former format was 9999.999). See P19A document on RMA's M13 page. With this ticket, the Intended and Revised Expected Value Amount fields on the user interface were updated to allow a value up to, but not exceeding, 99999.999.

Detail Lines: An issue was reported to the help desk where parent/child lines were not maintaining the same complete/incomplete detail line statuses. The re-save of the parent line actually caused the parent line to flip to "incomplete" but the related child line retained a complete status. The bug identified by the developer was very random but was caused by the parent line not "seeing" the Land ID that existed on the detail line. The System thought the parent line was incomplete due to a missing Land ID even though the required records existed. This has been corrected through a small code change.

Cotton: An issue was reported through the help desk that dealt with inconsistencies in the display of the price on Cotton premium lines. Some of the premium lines displayed a correct price of ".76" while other premium lines displayed a price of "1.00". Re-saving the premium line did not clear the incorrect price. The correct value was used in all premium calculations, so there were no premium errors that resulted from the bug. However, the SOI picked up the incorrect "1.00" price on the lines where it existed. It was found there was a bug in the option checking on the View Detail Line page. This has been corrected, and premium lines are now reflecting a correct ADM price of ".76".

Production Hail: A correction made so that, when the user is in a Production Hail policy and all the optional endorsements have been added to the parent line, the user is no longer able to add a child line that would increase the liability on the policy. Also, the user must select an optional endorsement to save an endorsement on a Production Hail policy.

Occasionally, when the user was setting up a linked Private Product policy, the placeholder lines were not matching the order of the associated MPCI policy coverages. An enhancement was done to the setup of linked Private Products, so the placeholder lines on the Private Product policy will now match the order of the coverages as shown on the MPCI side.

NOTE: This does not affect existing policies. Only policies where a submit acres/mark complete is done will be re-ordered. Also, any placeholders that are retained because no lines qualified will be sorted to the bottom of the list. A spinoff, TFS #92680, was created to include the sorting of unfinalized lines.