This chapter discusses:
JD Edwards EnterpriseOne Grower Management overview.
JD Edwards EnterpriseOne Grower Management integrations.
JD Edwards EnterpriseOne Grower Management implementation.
JD Edwards EnterpriseOne Grower Management Overview
Companies in the Agri-business industry can try and duplicate successful harvests by refining their growing processes to include identifying and repeating successful techniques. Techniques that are tracked and duplicated might include the sequence and types of operations performed, when each operation occurs, amount of agrochemicals that are applied to a crop, subsequent activities, and so forth. The need to track the estimated harvest and compare the estimates to the actual harvested amount is also a requirement.
Within the JD Edwards EnterpriseOne Grower Management system from Oracle, you can create, maintain, plan, and analyze grower information. For example, you can:
Manage attributes across blocks of land to provide increased productivity by quickly accessing critical data.
Track the anticipated harvest estimate for each block of land.
Roll up each activity cost into the total operational cost of the crop.
Receive crops into internal processing facilities from internal or external farms and capture weight, grade, and quality results.
Integrate crop contracts that are entered in JD Edwards EnterpriseOne Grower Pricing and Payments to secure accurate crop pricing and adjustments.
Farm, Blocks, and Harvests
The hierarchy for maintaining the grower tracking attributes includes farms, blocks, and harvests. You can optionally create farm records and have the attributes be supplied by default to the block and harvest records. Block and harvest records are required, and you can override attributes that are specific to a block or harvest. If you need to track information on a smaller part of a block, you can create a subharvest record using the harvest suffix. This enables you to differentiate between an experimental crop and the regular crop.
Harvest Period Patterns
Harvest records are created based on the harvest period pattern that is assigned to a block. Each harvest record is a representation of an individual block for the period of a growing cycle. Each period pattern record has specific start and end dates.
End Use Reservation
In an effort to satisfy market demand for a specific product, you can specify a particular end use for the harvest. When you receive the harvest, you can track the quantity being received for each end use.
Ownership
You can enter the legal ownership, by percentage, of the crop through the various operations.
Harvest Workbench
The Harvest Workbench provides a single entry point into the majority of applications that are used to manage harvest records and activities.
Harvest Estimates
When a crop is harvested over a specific period of time, you can estimate harvests by pick date range. These detail harvest records are then rolled up into an overall harvest estimate. You can freeze the initial harvest estimate and then capture estimates throughout the growing cycle. Historical reference of each estimate can be stored to understand variability.
Base Operations and Configured Operations
To perform the various harvest activities, you use operations. When you enter an operation, you use a configured operation that you have previously set up in the system. Configured operations, in turn, are based on base operations that are preconfigured in the system and cannot be changed. Base operations determine details about the operation. The system provides an application where you can review all the preconfigured base operations.
You can set up multiple configured operations for each base operation. In each configured operation, you provide additional details, for example, the additives that are used in a spray operation. Some of the values that you set up for configured operations are default values that you can override when you enter the actual operation.
Harvest Activities
When you enter grower operations, you are required to define certain types of information based on the operation configuration. The system guides data entry by displaying only those areas of the application where you need to add data. For example, if the operation requires equipment, then the system displays the equipment tab for data entry. Activity costs are tracked within the system.
Crop Receipt Using Weigh Tags
The crop receipt is part of a weigh tag as the vehicle crosses a weighbridge. When you enter a receipt operation, the system calculates the new receipt weight. You can also manually enter this information. When you close the weigh tag operation, the system creates a purchase order and a receipt in the Enterprise Requirements Planning (ERP) system and updates the on-hand quantity.
JD Edwards EnterpriseOne Grower Management Integrations
The JD Edwards Grower Management system integrates with these JD Edwards EnterpriseOne systems:
JD Edwards EnterpriseOne Inventory Management
JD Edwards EnterpriseOne Advanced Pricing
JD Edwards EnterpriseOne Procurement
JD Edwards EnterpriseOne General Ledger
JD Edwards EnterpriseOne Product Data Management
JD Edwards EnterpriseOne Quality Management
JD Edwards EnterpriseOne Blend Management
You must activate the JD Edwards EnterpriseOne Quality Management system before using the JD Edwards EnterpriseOne Grower Management system.
The JD Edwards EnterpriseOne Grower Management system works with other JD Edwards EnterpriseOne systems to ensure that all information is fully integrated. We discuss integration considerations in the implementation chapters in this implementation guide. Supplemental information about third-party application integrations is located on the Customer Connection website.
JD Edwards EnterpriseOne Inventory Management
The Inventory Management system tracks consumables and equipment. You also use Inventory Management to set up spray master records. When you close a weigh tag operation, the system updates the on-hand inventory with the received quantity.
JD Edwards EnterpriseOne Advanced Pricing
The system integrates with the Advanced Pricing system to adjust pricing based on the entry of quality test results at weigh tag close.
JD Edwards EnterpriseOne Procurement
The system creates a purchase order and receipt when you close a weigh tag operation.
JD Edwards EnterpriseOne General Ledger
The General Ledger creates journal entries for Grower Management transactions.
JD Edwards EnterpriseOne Product Data Management
You attach active ingredients to a spray item using the bill of material.
JD Edwards EnterpriseOne Quality Management
When receiving a crop, you can record quality results based on variety code, growing district, and test result name. You use the JD Edwards EnterpriseOne Quality Management system to set up test definitions, test result names to group similar tests with different test definitions, and test panels to group tests that are performed together.
You can also set up equipment and consumable material that are needed to perform tests. Quality tests are also available to track on any farming operation.
JD Edwards EnterpriseOne Blend Management
Many of the user-defined codes (UDCs) and other programs are shared with the JD Edwards EnterpriseOne Blend Management system. When the weigh tag is closed, an option is available to push attributes to Blend Management as the first operation to initiate in that system.
JD Edwards EnterpriseOne Grower Management Implementation
This section provides an overview of the steps that are required to implement the JD Edwards EnterpriseOne Grower Management system.
In the planning phase of your implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About This Documentation, with information about where to find the most current version of each.
When determining which electronic software updates (ESUs) to install for JD Edwards EnterpriseOne Grower Management, use the EnterpriseOne and World Change Assistant. EnterpriseOne and World Change Assistant, a Java-based tool, reduces the time required to search and download ESUs by 75 percent or more and enables you to install multiple ESUs at one time.
See JD Edwards EnterpriseOne Tool 8.98 Software Update Guide

Global Implementation Steps
This table lists the suggested global implementation steps for JD Edwards EnterpriseOne Grower Management.
|
Step |
Reference |
|
1. Set up global user-defined codes. |
See JD Edwards EnterpriseOne Tools 8.98 System Administration Guide |
|
2. Set up companies, fiscal date patterns, and business units. |
|
|
3. Set up accounts and chart of accounts. |
|
|
4. Set up General Accounting constants. |
|
|
5. Set up multicurrency processing, including currency codes and exchange rates. |
|
|
6. Set up ledger type rules. |
|
|
7. Enter address book records. |
|
|
8. Set up inventory information such as branch/plant constants, default locations and printers, manufacturing and distribution automatic account instructions (AAIs), and document types. |

Implementation Steps for Grower Management
This table lists the implementation steps for the JD Edwards EnterpriseOne Grower Management system:
|
Step |
Reference |
|
1. Set up items for type of crop, spray items, consumables, and additives. |
|
|
2. Set up system information such as constants, grower cost center defaults, maturity calculations, winery constants, and user-defined codes. |
|
|
3. Set up information such as harvest owner, material type, geographical areas, variety code, brand master, and EURs. |
|
|
4. Set up operation information such as configured operations. |
|
|
5. Set up costing information such as cost components, cost groups, and AAIs. |
|
|
6. Set up quality management information, such as test definitions, test results, and test panels. |