5.105.0 Release Notes

The Online Help Site has been updated with changes and additions from the 5.045.0, 5.050.0, and 5.065.0 releases. For those AIPs who receive Mapping, the Mapping layout was revised for better navigation.

In the 5.080 release with TFS #64301, the Written Agreement logic was updated to no longer exclude pilot crops and to only exclude crops from the Written Agreement functionality for which the crop provisions state Written Agreements are not applicable. Following the release of this change, a few additional crops were found for which the crop provisions state Written Agreements do not apply that had not been included in the new logic. With this ticket, the Written Agreement logic was updated to no longer allow Written Agreements on FL Fruit Trees or Pecan Trees. Affected crops include:

A small theming issue was found on the Add New Detail Line, Maintain Detail Line, Add New APH, and Maintain APH pages. On the Detail Line page, the unit number fields were elongated, causing the Use BU checkbox to wrap to the next line. On the APH pages, the year fields in the APH grid were elongated. This issue was affecting ARPI plans 04, 05, and 06 detail lines/APHs only. These issues have been resolved. The unit number fields on the detail line and the years in the APH grid are now displaying correctly.

It was found that the System was not importing the fields necessary for rating STAX (Plans 35 & 36) from the WA Area Risk Rate table.

For the 2015 and 2016 RYs only, an update was made to the WA ADM_ICE file import of the AreaRiskRate ADM Table (A01005) to include the start and end percent values. An update was also made to the rating code for STAX (Plans 35 & 36) to rate using these fields.

For the 2017 RY, RMA made a change to WFRP to allow multiple commodity lines for the same commodity code. Previously, only one line per commodity code was allowed. When multiple commodity lines for the same commodity code are keyed, the System should treat all lines with the same commodity code as one commodity. A bug was identified in the calculation of the Total Weighted Farm Rate and the Diversity Factor. This has been resolved.

APH: A bug existed that resulted in an established Master Yield being overwritten if the user accessed Fast Edit PR and saved AFTER the initial entry of production. For example, if production was entered through Fast Edit PR, then the Master Yield was applied, and then the user re-accessed Fast Edit PR and saved, the Master Yield was being overwritten with standard APH calculations. This bug has been resolved. Established and applied Master Yield values are no longer overwritten.

Coverage: A bug was identified on the Add New County page that was causing the County dropdown to display incorrect values for the selected state if an error message was received. The County dropdown on the Add New County page has been updated to always display the correct counties for the selected state.

Detail Lines: On the Detail Lines tab, a Total Acres field displays at the top of the page and displays the Total Acres for the coverage. Any acres from detail lines created for an option (CH, CL, CV, OX, MB, SE, SCO, or DC) should not be included in this Total Acres calculation since the acres are duplicates of the related line's acres. A bug was found where the System was including DC option lines in the total acres calculation when it should not have been. The Total Acres calculation was updated to no longer include any detail lines (child or not) with the DC option applied.

Detail Lines: Related to the entry of CLU acres, a bug was identified with crops that do not allow prevented plant (PP). When entering CLU acres, if the user did not enter a Plant Date, at save, the System displayed an error stating prevented plant procedures did not apply since PP was not applicable. However, when the user returned to the CLU grid and attempted to enter a Plant Date, at save, the System once again displayed the error. In addition, if a detail line was set to PP and the user then tried to enter a Plant Date through the CLU grid, the System did not allow the Plant Date to be saved or remove the PP status.

The logic that determines when to display the error message has been updated. This error will no longer display once a Plant Date has been entered. In addition, new logic has been added to the CLU grid to allow users to enter a Plant Date through the CLU grid even when a PP status was previously applied. In this scenario, the System will display a warning: "Warning: A Plant Date cannot be entered when the Prevented Planting designation is used." If the user selects OK, the System will apply the Plant Date and remove the PP status.

Fast Edit PR: An issue was found with the Final Production and Final Revenue fields in Fast Edit PR for WFRP policies. According to the P26 record, Final Production and Final Revenue should be a max of 11 characters including 10 numbers and a decimal place. For example, "99,999,999.99". The issue found was that the System was only allowing a total of 10 characters, including the decimal place. The Final Production and Final Revenue fields in Fast Edit PR for WFRP policies have been updated to allow a total of 11 characters including the decimal place.

Livestock: Due to issues of legality, the interactive map on the LRP Quick Estimate page needed to be removed. With this ticket, the map was removed from the page.

NOTE: TFS #67452 has been set up to make additional changes to the current LRP Quick Estimate pages with a redesign project.

Nursery: Nursery policies were in error at RMA when the premium line was "$1" in premium and a Conservation Compliance reduction was applied. RMA expected to see a $0 subsidy applied, but the System was incorrectly transmitting $1 for the subsidy. This error has been corrected.

Policy: RMA implemented some changes for the 2016+ RYs in their production release in October 2016. The rating changes applied to Plan 90 Dry Beans and Dry Peas when TA and YE were applied. The correction impacted very specific policies. RMA provided each AIP with a list of policies they should correct, and only those policies were impacted by this change. AIPs will need to resave the detail lines in error at RMA to pull in the new rating logic for calculation of premium and transmission.

Policy: TFS #39394 implemented a surcharge flag if the Yield Limitation Flag (YLF) is "12" or "13" for the 2015+ RYs. That ticket did not, however, implement the 5% surcharge in the premium calculation. 2015 policies with reported premium errors triggered a need for further review. It was determined that the policies were in error because the surcharge flag was being sent (policies were touched after TFS #39394 was implemented, so the flag is now being set) but the premium calculations do not match what RMA is expecting with a surcharge flag. This will continue to happen as any AIP touches a 2015 or 2016 APH on a cleared policy if the YLF is "12" or "13" and will result in new P11 premium errors rejected.

With the clarification, it was confirmed that 2015 and 2016 policies are clearing PASS with a YLF of "12" and no surcharge flag/surcharge calculation. Given this late date, the scope of this ticket was to remove the surcharge flag for a YLF of "12" and "13" that was applied under TFS #39394. It has been verified that 2015 and 2016 RY policies with a YLF "12" or "13" and NO surcharge flag are currently clearing RMA edits; no adjustments will be made to premium calculations for years prior to the 2017 RY.

For 2017+ only, a surcharge flag will bet set and the 5% surcharge will apply to the premium calculation if the YLF is "12" or "13" to comply with RMA's intended calculations; the surcharge flag and 5% surcharge will not apply to 2016 and prior RYs.

Quotes: Quotes are often created and populated with yields and acres on the MPCI side to accompany unsupported Private Product policies. A bug was identified that resulted in MPCI premium on a quote being populated on the Policy Balance tab. Although accounting transactions were created, the System did NOT include these quotes in Billing or Commissions batches, so this was just a UI display issue. The System was modified to ensure accounting transactions are not created when a policy's status is "quote".