Release Notes 5.115.0

This ticket implemented some formatting standards to the Raisin Acreage and Tonnage Report to print the Agency DBA and the plan code abbreviation on the detail line and add a signature authorization section. All changes will be rolled out to the Raisin Acreage and Tonnage Report for all Crop Years.

This ticket finished up some clean-up items found during the updates that were done to the Schedule of Insurance (SOI) and the SOI / Production Report in the 5.010.0 Release. Additionally, the Agency DBA now prints, the sort order to was updated to match the Fast Edit pages, and the signature authorization items were updated. All changes will be rolled out to the SOI and the SOI / Production Report for all Crop Years to all AIPs.

This ticket updated the Potential Loss Estimator. These updates are applicable for all Crop Years. The Potential Loss Estimator form is available to print within an individual MPCI policy on the Print tab and via Tools > Batch Printing.

Previously, production was not printing on the Production Report—the production value was displaying as 0.00 even when production had been keyed on the page (Maintain APH > Production History table > Production). The unit’s production will now print in the “Total Production” field for each year in the 10-year APH Database. The column label for Skip Row Corn now displays as “Total Production” and not “Total Production (Gross)”. The label will only display as “Total Production (Gross)” for Skip Row Cotton. These Skip Row Corn updates for the 10 year Production Report are for all Reinsurance Years. The Production Report is available to print from the MPCI Print tab in an individual MPCI policy and via Tools > Batch Printing.

When both TA and PA are applicable, AIPs requested that PA print in the Yield Descriptor field of the 10-year APH Database. Previously, only the TA yield type displayed along with the TA yield in parentheses but the PA yield type indicator also needed to display when applicable. Now, on the forms listed below, if both TA and PA are applicable, the System prints "TA" and the trend-adjusted value in parentheses, then a comma and a space, and then "PA".

The following forms are impacted by this update:

This ticket fixed the red Telerik error that was printing in the Production Report / Acreage Report when the form was being pre-printed for next year. Also, the Year was fixed on the Supplemental Land Page when pre-printed for next year as the year is the current year not next year.

The Pecan Tree pilot program is new for the 2018 Crop Year. With this ticket, Crop Provisions will now print with the MPCI Policy Declaration page when the print option to print provisions with the form is selected. This includes Pecan Tree Crop Provisions(18-pct) for Pecan Trees (0284) and Pecan Tree Crop Insurance Comprehensive Tree Value (CTV) Endorsement (18-pct-a) for Pecan Tress (0284) with the CTV option elected. The MPCI Policy Declaration Page is available to print from the MPCI Print tab in an individual MPCI policy and via Tools > Batch Printing.

This ticket updated the APH Database and Acreage Reporting Form with the following changes for all Crop Years:

The APH Database and Acreage Reporting Form is available to print within an individual MPCI Policy on the Print tab and via Tools > Batch Printing.

This ticket implemented some updates to the Acreage Report. Now, the Agency’s DBA prints in the header on page 1 and in the sub-header on page 2+, with "DBA" preceding the Agency's DBA name with a space separating the DBA label and name. This will print under the Agency's Name and Code. A Signature Authorization section is now available and includes the Authorized Rep, Grantee, and Power of Attorney (POA). The separate POA field was removed. All changes will be rolled out to the Acreage Report for all Crop Years.

An ICE 2013 update was made available by the RMA. The following table has been updated for 2013:

An ICE 2014 update was made available by the RMA. The following table has been updated for 2014:

An ICE 2015 update was made available by the RMA. The following table has been updated for 2015:

An ICE 2016 update was made available by the RMA. The following table has been updated for 2016:

An ICE 2017 update was made available by the RMA. The following tables have been updated for 2017:

An ADM 2018 update was made available by the RMA. The following tables have been updated for 2018:

An ICE 2013 update was made available by the RMA. The following tables have been updated for 2013:

An ICE 2014 update was made available by the RMA. The following tables have been updated for 2014:

An ICE 2016 update was made available by the RMA. The following tables have been updated for 2016:

An ICE 2015 update was made available by the RMA. The following tables have been updated for 2015:

An ADM & ICE 2017 update was made available by the RMA. The following tables have been updated for 2017:

An ICE 2013 update was made available by the RMA. The following table has been updated for 2013:

An ICE 2014 update was made available by the RMA. The following table has been updated for 2014:

An ICE 2015 update was made available by the RMA. The following table has been updated for 2015:

An ICE 2016 update was made available by the RMA. The following table has been updated for 2016:

An ICE 2017 update was made available by the RMA. The following tables have been updated for 2017:

An ICE 2018 update was made available by the RMA. The following table has been updated for 2018:

An ICE 2018 update was made available by the RMA. The following tables have been updated for 2018:

An ICE 2018 update was made available by the RMA. The following table has been updated for 2018:

An ADM 2017 update was made available by the RMA. The following table has been updated for 2017:

An ADM 2018 update was made available by the RMA. The following table has been updated for 2018:

2018 Roll: The CC/SF rule is available for calculating the Summerfallow Approved APH yields when the CC Approved Yield is greater than that calculated for Summerfallow using standard APH procedures. The Crop Insurance Handbook states that once applied to the calculation of an APH, it must be used each year until the Summerfallow database reaches 3 years of actual yields. A gap was identified in the roll logic that resulted in this flag not being rolled on applicable APHs even though the System has always automatically applied the "higher of" yield calculation. This flag will now roll to the new RY as part of the year end processing.

Contracts: The Add New/Maintain Contract page was updated to include all three contract types (acreage, production, acreage and production) in the dropdown as options for the 2017+ RYs for the following crops:

The Warning statement for Corn Seed, Sorghum Seed, and Sweet Corn Seed was updated to read: "Must be a bushel/acre value." The Warning statement for Rice Seed was updated to read: "Must be a pound/acre value."

Detail Lines: When the CLU grid was initially put in place several years ago, it was decided to allow agent users to update CLU acres even after the lockout date but not to push these acres to the detail line. The logic was designed this way initially due to business processes around CLU acres at the time. Now that RMA is requiring 100% CLU reporting for Plans 01, 02, 03, 04, 05, and 06, as well as 40% CLU reporting for all other plans, CLU acres are being keyed during acreage reporting.

Written Agreements: During regression testing of the Fast Edit PR, MCT identified a bug around the display of Practice and Type in the APH drawer if an "XC" written agreement applied to the detail line/Fast Edit PR grid line. This has been corrected.

Coverage: On the Add New and Maintain Coverage page, there is an Is Dual Coverage checkbox. This flag was put in place for when the High Risk Land Exclusion (HR option) is elected. The intention was for the "HR" option to be applied to the buy-up coverage and the Is Dual Coverage checkbox to be applied to the CAT coverage.

It was recently identified that users had set the Is Dual Coverage checkbox on a couple of policies with the High Risk Alternative Coverage Endorsement (HB option). The Is Dual Coverage checkbox was not intended to be set on policies with the HB option, so when it was set, it was causing issues with the transmission.

In order to prevent this flag from being incorrectly set in the future, logic was added to only display the Is Dual Coverage checkbox when the elected coverage level is CAT.

NOTE: There is existing logic in place that only displays the Is Dual Coverage flag when high risk land exists for the State/County/Crop/Type/Practice.

AIPs that had policies with the Is Dual Coverage flag set with the HB option have been sent a list of policies.

APH: A bug was identified with the existing Continuous Cropping/Summerfallow (CC/SF) rule logic. When determining if the CC/SF rule applied, the System was searching for an APH with the CC Practice applied for the same Unit Number and Type as the SF APH. However, the System was not considering Map Area when determining if the CC/SF rule can apply. The CC/SF rule logic has been updated to only apply the CC/SF rule if an APH with the CC Practice exists with the same Unit Number, Type, and Map Area as the SF APH.

NOTE: The CC/SF rule only applies if less than 3 years of history exists in the SF APH, a CC Practice APH exists for the same Unit Number, Type and Map Area and the CC Approved Yield is higher than the SF Approved Yield.

Native Sod: Back in October, RMA released a new rule stating the PF and PT options were not applicable for New Breaking or Native Sod. At that time, with TFS #59990, functionality was implemented to remove the PF and PT options from the detail line if New Breaking or Native Sod was applied to the APH database.

With the April PASS release, RMA updated this rule to allow the PF and PT options on Native Sod so long as it is not the initial year of planting. The existing rule for New Breaking and Native Sod in the initial year of planting will continue to apply. Detail line logic was updated to apply PF and PT options if elected on the coverage for Native Sod detail lines that are not designated as the initial year of planting. Existing logic that does not apply PF or PT for New Breaking and Native Sod in the initial year of planting still applies. This change was applied to 2016+ RYs.

Fast Edit PR: A bug was identified in the Fast Edit PR logic when a "0" Actual Yield was applied to an APH (Actual Yield of "0" and Assigned Yield logic on exit of the Fast Edit PR was bypassed). It was confirmed that the applicable APHs were properly updated with a Total Production of "0" and an Annual Yield of "0" but the System didn't calculate an Approved APH yield for these units as it should have. This has been corrected.

Fast Edit AR: An update was made to the display of the ARD field at the top of the Maintain Signatures page for the Fast Edit AR. Previously, the read-only field displayed a dropdown that appeared to be editable. To eliminate confusion, the field type has been changed. If an ARD is selected on the Fast Edit AR page, the same selection will display in a read-only format without a selection box on the Maintain Signature page. If no ARD date is selected, the field will be blank and the ARD label will not display on the Maintain Signatures page.

Fast Edit AR: In the 2017 Fast Edit AR grid, the System will default a Planting Pattern of "Solid" for all grid lines that reflect a non-Skip Row Practice code (e.g., a NI Practice code that is NOT a NI-Skip Row Practice code). If the Practice code for the Fast Edit AR grid line is changed to a NI-Skip Row code, the Planting Pattern, Row Width, and Skip Row Factor codes will be available for edit.

NOTE: In order to change a grid line Practice code from NI to NI-Skip Row, the user must open the drawer and make the change in the drawer and save the drawer changes. This will open these fields for edit.

Fast Edit PR: During internal testing, it was found that selection of the Process Zero Lines checkbox on a selected coverage is not always triggering the APH calculation of detail lines for that coverage with no Approved Yield and zero planted acres in the prior year. An fix was implemented to the Subsequent Year Reporting functionality. If the Process Zero AR Units checkbox is selected for one or more coverages on the Maintain Signature page, the System will calculate an Approved Yield for each APH database for that selected coverage(s) if the most recent year in the database is the prior year (RY-1, or RY-2 for lag year crops) with Acres is 0.00.

Almonds: An AIP was a P15-4894 error for the Average Yield calculation for Almonds. It was determined that if an Almond APH database had less than 4 years of Actual Yields and one of the yield descriptors within the 4 years was “NQ”, a T-Yield was not being substituted for the NQ when calculating the Average Yield. The Almond Average Yield calculation was updated when there is less than 4 years of history to substitute a T-Yield for the NQ yield.

Pecan Trees: A couple of bugs were identified with the new Pecan Tree functionality:

These bugs have been resolved. Restoration Method will now display on the View Coverage page, the Age and % of Trees are now calculating for Stages IV and V and Stages IV and V are now included in the Tree Count Summary on the PAW.

NOTE: The Stages on the Tree Count Summary are determined by the values selected in the Block-Stage dropdown.

Transmissions: Agency Extracts are available as a Transmission Type and may be provided to agencies as a modified M13 format at the AIP's discretion. In 2017, the Agency Extract format was extended to include Private Products and all record schema was wrapped into a "C" record format. This change adds a C49 delete record to the Private Products Agency Extract to designate cancelled Private Products.

During ECHO testing of the Fast Edit grid, an issue was found with adding an endorsement through the Endorse link in the Fast Edit grid. It was allowing the user to select an Application Date that was prior to the parent line's Effective Date on the policy. The non-optional endorsement line may not have an Application/Effective Date that is prior to the associated parent line on the Hail policy.

An update was made for Production Hail to look for duplicates within the same coverage rather than across. There was a bug where it checked if ANY coverage on the PH policy had identical Coverage Level, Price Election, and Practice and then it would see it as duplicated. This has been addressed with this ticket.