|
Detail Lines: Enhancements have been made to the Copy Detail Lines, Copy APH, and Copy PAW functions to alleviate time-consuming and complex entries of large perennial PAW records when duplication is allowable and to maintain consistency between the Copy popups:
Copy Detail Lines
|
•
|
A Copy PAW checkbox was added to allow a user to copy a Perennial PAW Block Details grid in its entirety when a Detail Line is copied. |
Copy APH
|
•
|
The order of "Copy To" and "Copy From" was reversed to be consistent with other Copy popups. |
|
•
|
The ability to Copy From a different "Type" Unit than that selected on the "Copy From" Unit was added. |
Copy PAW
|
•
|
The order of "Copy To" and "Copy From" was reversed to be consistent with other Copy popups. |
|
•
|
The ability to select individual blocks of a PAW record or all blocks of a PAW record was added. |
|
•
|
The ability to create a new PAW record or append an existing PAW record was added. |
|
37942
|
|
WFRP: An issue was reported with WFRP policies where the System was not allowing the policy to be marked complete. For WFRP policies, the System was requiring commodity lines, the Income & Expense Record, and Farm Report Signature Dates to be keyed before Mark Complete would run successfully.
Mark Complete logic has been updated to no longer require commodity lines, the Income & Expense Record, and Farm Report Signature Dates to be keyed before mark complete can run successfully. This will allow users to key a WFRP coverage, process Mark Complete, and review any coverage-related suspensions prior to keying commodity lines, the Income & Expense Record, and Farm Report Signature Dates.
|
67010
|
|
WFRP: An enhancement request was received for the ability to key estimated MPCI liability on WFRP policies. The existing MPCI Liability field could not be used to key an estimated value because we have functionality related to this field that ties into the MPCI policy. When acres are keyed to the MPCI policy and the coverages are 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 to key estimated MPCI liability, a new UI and database field for "Estimated MPCI Liability" was added to the Income & Expense Record. If a value is keyed in this field, the System will use it as the MPCI Liability in the premium and liability calculations. Once an actual MPCI Liability value is applied, the System will use the actual MPCI Liability in the premium and liability calculations.
|
67311
|
|
WFRP: A bug was reported where users were not able to change the Agent of Record on WFRP polices. There are two different agents they can apply to a policy, a Servicing Agent and an Agent of Record. The Servicing Agent is the agent that owns the policy while the Agent of Record is the agent that signed the processing forms. The Agent of Record is often the same agent as the Servicing Agent but can be different in certain circumstances.
Users can change the Servicing Agent on the Grower tab of the policy. The Agent of Record on the other hand can only be changed via the Signature Maintenance page or the Signature Maintenance of the Fast Edit page. However, WFRP does not currently have a Signature Maintenance page. Given this, there was previously no place to update the Agent of Record on WFRP policies. With this ticket, a field for Agent of Record was added to the Income & Expense Record to allow users to update the Agent of Record on WFRP policies. In addition, of few display enhancements were implemented on the Income & Expense Record.
The following updates have been made on the Income & Expense Record page for WFRP policies:
|
1.
|
The Insured & Agent Sign Dates have been moved from the banner to the bottom right corner of the page to allow room for the new Agent of Record field. |
|
2.
|
A dropdown for Agent of Record has been added. |
|
3.
|
The Apply Dates button that previously displayed next to the Signature Date fields has been removed. |
|
4.
|
The save logic has been updated to include save of the Signature Dates and Agent of Record since the Apply Dates button has been removed. |
|
68414
|
|
Perennials: The 2018 RY CIH includes new procedures for Perennial acreage that is transitioning to organic the first year. Enhancements have been made to the System to accommodate the new procedures.
The following enhancements have been made for 2018 RY+:
|
1.
|
Added APH Override "Organic-Transitional T-Yld" |
|
•
|
Override only available for Perennial Category C (Plan 47 & 90) and Category D (Plan 41) crops. |
|
•
|
Override not applicable to Organic Certified database (Practice includes "OC"); only applicable to conventional or Organic-Transitional (Practice includes "OT") databases. |
|
•
|
Override will only apply if NO Actual Yields exist in the database. |
|
2.
|
If APH Override is "Organic-Transitional T-Yld", Yield Override field will be available. |
|
•
|
Organic-Transitional T-Yield value must be manually calculated and entered in Yield Override field. |
|
•
|
The System will apply the Override Value to the Current Year T-Yield field and to the most recent four years in the database. |
|
•
|
The System will apply Yield Type of "OF" to the most recent four years in the database. |
|
3.
|
Yield CUP is not applicable the initial year. |
|
4.
|
YE and YA are not applicable to Yield Type "OF". |
|
5.
|
Minimum Production edits are not applicable—this will be a user determination. (Edits are crop specific) |
NOTE: a) ARH (Plan 47): There will be two Override values. The Override Yield will be used to populate the Annual Yield fields in the Production & Revenue History grid, and the Override Revenue will be used to populate the Net Revenue fields in the Production & Revenue History grid. The Override Revenue value will be calculated manually by the user in the same way the Override Yield is calculated. b) SRH (Plan 41 - Pecans): The Override Yield will be used to populate the Gross Sales for the most recent EVEN years in the database being used for Approved Yield calculations.
|
71710
|
|
Perennials: The 2018 RY CIH includes new procedures for Perennial acreage that is transitioning to organic the first year and a question has been added to the PAW to identify those units. Enhancements have been made to the System to accommodate the new procedures. TFS #71710 implements APH Override logic for determining a yield on first year acreage transitioning to organic with or without a plan, and TFS #77824 added logic to the PAW Required Questions. This ticket will add a suspension at Mark Complete if the PAW identifies the acreage as Transitioning to Organic the first year and the corresponding APH does not include the APH Override "Organic-Transitional T-Yld" is not selected.
|
1.
|
Upon MC, the coverage will suspend if |
|
a.
|
If answer to second PAW Required Question, Reduced Crop Production is YES AND "a) Is acreage transitioning from conventional to organic for the first year?" is selected |
|
b.
|
APH Override on associated APH record DOES NOT equal "Transitional-Organic T-Yld" |
|
c.
|
A PAW Signature Date exists |
|
d.
|
An AR Signature Date exists. |
|
2.
|
Suspension message will read: |
"Unit XXXX-XXXX is transitioning to organic the first year. Additional Underwriter review is necessary."
|
3.
|
Suspension will clear when |
|
a.
|
PAW Required Question, "a) Is acreage transitioning from conventional to organic for the first year?" is selected; |
|
b.
|
APH Override on associated APH record that is "Transitional-Organic T-Yld"; |
|
c.
|
Override Yield greater than "0.0" exists |
|
d.
|
Override Yield value is entered (cannot be blank, NULL or "0.0") |
NOTE: If answers to the Required questions have been saved where primary question Reduced Crop Production is "YES" and the subsequent question "transitioning to organic" is selected, if the user wishes to change the primary Reduced Crop Production answer to "NO", the subsequent "transitioning to organic" question must first be de-selected.
|
71714
|
|
Perennials: An enhancement has been made to the Yield Limitation logic for determined yields. Statements within the 2018 CIH clarified that the use of a Yield CUP on databases with a Determined Yields is not allowed.
|
1.
|
2018 CIH: Paragraph 1854. A. Establishing APH Databases for Acreage Transitioning to Certified Organic for the new procedures where perennial determined yields with "OF" Yield Types, paragraph (b) states: "YA, YE, nor CUPS apply to the APH database ." and |
|
2.
|
2018 CIH: Section 7, Paragraph 1873 Yield Limitations, B. CUPS Do Not Apply, item (5) was clarified and now states: "the APH databases/yields are determined using RO UG or Determined Yields." |
The System logic for 2018+ RY Yield Limitation has been updated as follows:
|
•
|
Yield Limitation Flag cannot equal 03 (Yield CUP) if |
|
1.
|
APH Override is "Organic Determined Yield" |
AND, APH database contains one or more Yield Types of "OF"
- OR -
|
2.
|
APH Override is "RO UG Exception, RO Determined Yield or RO Determined Yield - Approved Yield" |
AND, APH database contains one or more Yield Types of "F".
|
71718
|
|
Coverage: Beginning in the 2018 RY, the 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. To allow processing of Plan 17 detail lines with a related coverage, the existing Plan 16 detail line and approved yield functionality for related MP coverages was expanded to include Plan 17. This includes:
|
•
|
The ability to create Plan 17 Margin Protection detail lines and selected related MPCI detail lines; |
|
•
|
The System calculation of the approved yield on the Margin Protection line is based on the selected related MPCI detail lines; |
|
•
|
The addition of a dropdown to allow the manual selection of a Unit Structure Code; and |
|
•
|
The Setting of the associated AIP acreage keys. |
|
77354
|
|
Margin Protection: For the 2018 RY, RMA expanded the Margin Protection (Plan 16) to Margin Protection-HPO (Plan 17). In addition, Margin Protection can be insured as a type level where coverage is allowed at a type level in the actuarial documents. Coverage can be purchased from 70% to 95% of a grower's expected margin and with a productivity factor of 80 to 120%. A bug was identified on 9/26 that resulted in selections of 120% not holding in the System at Save & Exit from the coverage page.
RMA updated the 2018 RY ICE D0007 table to reflect the selection of the coverage level and productivity factors, so an update to the code was required to allow for the selection of higher levels. At save, selections of 120%, for example, will now persist to the database and display properly on the page.
|
79446
|
