1. Grower Management Implementation Guide
  2. Processing

Processing

These processing options control whether a harvest can have multiple suffixes, determine whether the harvest status can change, determine whether the container type and quantity per load are at the harvest level, and control whether certain fields are input capable or displayed.

Multiple Harvest Suffixes

Specify whether the system allows multiple harvest suffix for a block. Values are:

Blank: Allow multiple suffixes.

1: Do not allow multiple suffixes.

Status Change

Specify whether the system allows the harvest status to be changed from this form. Values are:

Blank: Allow a status change.

1: Do not allow a status change.

Container Type and Quantity Per Load

Specify whether the system allows the container type and quantity per load to be changed at the harvest level. Values are:

Blank: Do not allow the container type and quantity per load to be changed at the harvest level.

1: Allow the container type and quantity per load to be changed.

Harvest Period Effective Dates

Specify whether the system displays the harvest period effective dates. Values are:

Blank: Display the dates.

1: Do not display the dates.

Calculated Maturity Date

Specify whether the system enables the calculated maturity date. Values are:

Blank: Enable the calculated maturity date.

1: Disable the calculated maturity date.

Base Price and Default Price

Specify whether the system displays the base price and default price fields. Values are:

Blank: Display the price fields.

1: Do not display the price fields.

Create Purchase Order

Specify whether the system creates a purchase order while creating or modifying a grower harvest. Values are:

Blank: Do not create a purchase order.

1: Create a purchase order.

This processing option drives the Supply and Demand (P4021) functionality and causes the system to create purchase orders during the grower process when you create a harvest, make changes to harvest estimates, or make changes to harvest end dates. When you activate this processing option, the system displays the External Ownership option on the Financial tab of the Add/Edit Grower Harvest form (W40G03C). When you add a harvest, you can select the External Ownership option if you want the system to use the External version of the Purchase Order Entry program (P4310) to create purchase orders. Leave the External Ownership option blank and the system uses the Internal version of the Purchase Order Entry program to create purchase orders. The system updates the External Ownership option value to the Grower Harvest table (F40G03). In addition to using the Grower Harvest Maintenance program, you can also use the following programs to add harvests and write the External Ownership option value to the Grower Harvest table:

  • Generate Harvests (P40G02)

  • Generate Harvests (B40G0560)

  • Harvest Roll / Generate Harvests (R40G0560)

  • Push Block to Harvest (P40G024)

Note: In order to write the External Ownership option value to the Grower Harvest table, each respective program must activate a version of the Grower Harvest Maintenance program, which is set to create purchase orders.

When you make changes to the harvest estimates or harvest end dates the following programs access the Grower Harvest table to validate the External Ownership option value:

  • Continuous Harvest Estimate (P40G23)

  • Grower Harvest Maintenance (P40G03)

  • Harvest Estimate (P40G20)

  • Harvest Estimate - Batch Update (R40G20)

  • Mass update - Harvest (R40G0300)

  • Speed Harvest Update (P40G030)

External Ownership

Specify the version of Purchase Order Creation (P4310), which indicates the line type and A/P interface flag the system uses to create the purchase order when creating a harvest. External ownership exists when the A/P interface flag is set to NO. Values are:

Blank: Internal.

1: External.

Note: This processing option works only when you activate the Create Purchase Order processing option.
Allow Harvest Dates to Overlap

Specify whether the system allows harvest dates to overlap for a block. Values are:

Blank: Do not allow overlap.

1: Allow overlap.

Note: If this field is left blank, the system displays an error message when the harvest dates overlap for a block.