Knowing the Functions of the Field Planning and History App

Objective

After completing this lesson, you will be able to use the functions of the Field Planning and History App

Field Planning and History App Overview

The Field Planning and History app is a tool to plan growing seasons per field. The outcome of that planning process is a crop zone. Crop zones can be viewed and maintained, as well as kept as historical records.

A crop zone is an entity that identifies an area where a specific crop/variety is grown during a specific season. KPIs can be maintained on crop zone level, such as planned and actual yield, which can help keep historical data and enable performance analysis. Having an overview of and full transparency on your crop zones is crucial for the decision-making process. Therefore, historical data on crops, varieties, fields, areas, and seasons can be customized and displayed in a way that users can get a clear perspective of their current, previous, and planned seasons in one view, streamlining crop management.

Screenshot of the SAP Field Planning & History interface displaying details for Crop Zone 2025. The crop is Sugarcane, variety CP 73-1547, for the season 2025. The description states, This is the crop zone in Field 1. The farm is Sugar Cane Farm, located in Field 1, area SugarCane Field 1. The crop purpose is Food Consumption. KPIs listed include Sucrose with an estimated value of 60 t/ha and a predicted value of 75 t/ha. The interface includes options to close, edit, or delete the entry.

Create a Crop Zone

In the initial screen of the Field Planning and History app, select Create Crop Zones to start the seasonal field planning process.

Screenshot of the SAP Field Planning & History interface showing a list of crop zones. The interface includes search and filter options for Crop Zone, Field, Season, Crop, Variety, and Farm. The list displays 16 crop zones with columns for Crop Zone, Description, Season, Crop, Variety, Field, Area, Crop Purpose, Crop Zone Group, Cropping System, and Fallow Fields. A Create Crop Zones button is highlighted in the top right corner. The list includes entries for various crops like Broccoli, Potato, and Strawberry, with details about their respective fields, varieties, and purposes.

There are two options for creating a plan, either using a Cropping System or manually. If a predefined cropping system is selected, some information will already be mapped (for example, crop, variety, and if they were specified, crop purpose and production type). For the manual plan, data will need to be entered manually. The next figures show the two approaches (Use Cropping System and Create Manual Plan).

Screenshot of the SAP Field Planning & History interface showing the Create Crop Zones section. The screen is on step 1, Plan Type, where users can select the type of plan they want to use. There are two options displayed: Use Cropping System on the left, which allows users to select a predefined cropping system, and Create Manual Plan on the right, which allows users to create manual planning for annual, perennial, and fallow crop zones. The interface includes navigation elements at the top and a Cancel button at the bottom right.

If you choose Use Cropping System, the existing cropping system(s) will be available for selection.

Screenshot of the SAP Field Planning & History interface, specifically the Create Crop Zones section. The interface is on step 2, Cropping System, where users can select a cropping system based on its crops and management techniques. Four options are displayed: Rotation with 3 cycles, Potato 1-0-1, and Wheat Rotation. Each option lists its cropping system elements and a brief description. The Rotation with 3 cycles option is highlighted. Navigation buttons for Previous Step, Next Step, and Cancel are at the bottom right. A search bar with the term rotation is at the top right.

When the desired cropping system is selected, you will have the option to configure the different elements by adding details. Click on the arrows on the left to open each element and see the prefilled information, and to make edits. You must specify where the Planned Start Date, and the Farm, Field and Area should be used.

When this is done, choose Configure to move to the next step, or select Configure and Add New to configure the cropping system for another Farm, Field, Area and start date.

The remaining steps in the process are the same as those related to creating the plan manually and will be detailed next.

Screenshot of a Configure a Cropping System interface. The interface includes sections for configuring crop orders and selecting farms and fields. The Crop Order section lists four items: Wheat 1 with a duration of 75 days, Fallow with a duration of 120 days, Wheat 2 with a duration of 60 days, and Wheat 3 with a duration of 15 days. The Wheat 1 section is expanded, showing fields for Crop, Variety, Season, Planned Start Date, Break, Crop Purpose, and Production Type. The Farms and Fields section has fields for Farm, Field, and Area. At the bottom, there are buttons labeled Configure and Add New, Configure, and Close.

If Create ManuaI PIan is selected, you have the option to create different types of crop zones – Annual, Perennial, and Fallow by selecting the + icon.

For each type, you must specify the required information:

Annual Crop Zones
Select the crop, variety and season, as well as Farm, Field and Area from the available drop-down options.
Perennial Crop Zones

Select the perennial and the season. You also have the option to indicate if this is the last season for the perennial. Since the perennial already includes location information (Farm, Field, Area), this information will be populated automatically when the perennial is selected. Perennials will be described in more details in the next lesson.

In both cases, Crop Purpose and Production Type are optional fields.

Fallow Crop Zones
Specify in which season the field should not be used/planted.

More than one of the crops can be added by clicking on the + icon in the upper-right corner of the table. It is also possible to remove crops using the x at the end of each row.

At the bottom of the screen, you can choose to go to the next step or back to the previous step.

Screenshot of the SAP Field Planning & History interface, specifically the Create Crop Zones section. The interface is on step 2 of 3, titled Crops and Farms. The user is prompted to select crops to cultivate during the season. There are three sections: Annual Crop Zones, Perennial Crop Zones, and Fallow Zones. Each section has fields for crop details such as Crop, Variety, Season, Crop Purpose, and Production Type. There are plus (+) icons to add manual planning entries. Navigation buttons at the bottom include Previous Step, Next Step, and Cancel.

Note

From this step on, the cropping system and manual creation processes are the same.

The Crop Zone Name is filled in automatically based on the information entered in the previous step, but can be edited if needed. A description can also be entered, but it’s optional. Assigned KPIs can be added by selecting the penciI icon, or if there are multiple crops zones, by clicking the check box Select All on the top right to assign KPIs to all the selected Crop Zones.

The same process can be followed for the Perennial Crop Zones. Fallow Crop Zones do not have KPIs.

Screenshot of the SAP Field Planning & History interface showing the Create Crop Zones section. The process is divided into three steps: Plan Type, Crops and Farms, and Crop Zones. The current step is 3. Crop Zones, where users review crop zone information and assign KPIs. The Annual Crop Zones tab is selected, displaying details for a crop zone named Broccoli (Waltham) on Red Keep Field 2 in Season 2026. Information includes crop type (Broccoli), variety (Waltham), farm (Red Keep Farm), field (Red Keep Field 2), area (Field 2), and season (2026). There is a section for a description with 1000 characters remaining and an area to assign KPIs. Options to select all and assign KPIs are available. Navigation buttons for Previous Step, Preview, and Cancel are at the bottom.

Available KPIs can be selected.

Screenshot of a user interface for assigning Key Performance Indicators (KPIs) to a crop zone. The selected crop zone is Broccoli (Waltham) on Red Keep Field 2 in Season Season 2026. Below the crop zone selection, there is a list of KPIs with checkboxes next to each KPI name. The KPIs listed include Bio Diversity, CO2 in ton, CPO per hectare (t/ha), Electricity Consumption, FFB per hectare (t/ha), Fruit count (pc.), Fruit count (pc./ac), Fruit count (pc./ha), Fuel Consumption Gallon per Acre, Fuel Consumption US Gallon, Harvested Cases (cases/ac), Prediction: KPI Yield Vista, Soil health, Soil Moisture %, and Sucrose (t). Each KPI has a brief description next to it. At the bottom of the interface, there are OK and Cancel buttons.

When all of the information is entered, select Preview at the bottom of the screen to move to the last step.

The Preview screen gives you an overview of all the details entered and the Crop Zones that will be created. It’s still possible to edit most of this data. Otherwise, save the Plan by selecting Create at the bottom of the screen.

Screenshot of the SAP Field Planning & History interface showing a New Field Plan. The interface is divided into sections: 1. Plan Type; 2. Crops and Farms; 3. Crop Zones. Buttons at the bottom: Previous Step, Create Crop Zones, Cancel. The interface includes options to edit each section and a scrollbar on the right side. The SAP logo is visible at the top left, and user initials AR are shown at the top right.
Screenshot of the SAP Field Planning & History interface showing a New Field Plan. The interface includes sections for Plan Type, Cropping System, Crops, Seasons, and Areas, and Crop Zones and KPIs. The chosen plan type is Cropping System, and the chosen cropping system is Wheat Rotation. The farm is Green Valley Farm, and the field is Green Valley Field 1. The crop plan includes Wheat 1 (T-Compact) in Season 2029, Fallow from Dec 31, 2029, to Apr 29, 2030, Wheat 2 (T-Vulgare) from Apr 30, 2030, to Jun 28, 2030, and Wheat 3 (T-Durum) from Jun 29, 2030, to Jul 13, 2030. Each crop entry includes details such as crop type, season, variety, farm, field, area, crop purpose, production type, and KPIs. There are no KPIs assigned. The interface has options to edit sections and buttons for Previous Step, Create Crop Zones, and Cancel at the bottom.

After receiving a confirmation message that the Crop Zones were created successfully, you will be navigated to the Field Planning and History Overview page, which is where the new crops zone(s) will be listed.

SAP Field Planning & History interface. The top section has search filters for Crop Zone, Field, Season, Crop, Variety, and Farm. The Crop Zones table shows 161 entries with columns for Crop Zone, Description, Season, Crop, Variety, Field, Area, Crop Purpose, Crop Zone Group, Cropping System, and Fallow Field. Four entries are visible: 1) Fallow on Green Valley Field 3, Season Fallow - Dec 31, 2029 - Apr 20, 2030. 2) Wheat 3 (T-Durum) on Green Valley Field 3, Season Wheat 3 - Jul 14, 2030 - Jul 28, 2030. 3) Wheat 2 (T-Vulgare) on Green Valley Field 3, Season Wheat 2 - May 15, 2030 - Jul 13, 2030. 4) Wheat 1 (T-Compact) on Green Valley Field 3, Season 2029. Crop purposes vary from animal feed to food consumption with all part of wheat rotations.

Field Planning and History – Overview of Objects and Key Attributes

The following data is maintained during the creation of the plans:

Note

The ones with an asterisk "*" are mandatory during crop zone creation.

  • Crop zone: A crop zone is an entity that identifies an area where a specific crop/variety is grown during a specific season. Create and/or view and maintain crop zones using the Field Planning and History app.
  • Crop Zone Group: The crop zone group can be selected. This is a group element (Crop Zones can be associated to a Crop Zone Group).
  • Season*: Select a predefined season to start the farm planning. The season is an entity to describe a defined timeframe during which agricultural activities are executed.
  • Crop*: A crop is an entity to identify different categories of plants cultivated by farmers. Crops can be cultivated as annual crops or perennial crops. Crops do not need to strictly follow scientific taxonomies but can be defined based on organizationally established terms. Multiple varieties can be maintained per crop with the associated variety entity.
  • Crop Variety*: Select a predefined crop variety maintained in the system. Crop varieties can be a set of variety characteristics, that describe the specific attributes of a variety - for example, if it is frost resistant, genetically enhanced, and so on.
  • Crop Purpose: Select the predefined crop purpose maintained in the system to associate to the farm planning. A crop purpose defines the purpose of the respective crop in the cropping system.
  • Fallow Crop Zones: This is a check box that can be selected or unselected to indicate the given field will be fallow during the planned season.
  • Description: The user can maintain a detailed description for the crop zone.
  • Production type: Select a predefined production type maintained in the system to associate to the farm planning. A production type distinguishes different general styles of agricultural production (for example, organic).
  • Cropping system*: Required when creating a Crop Zone using a predefined cropping system. A Cropping system represents an abstract sequence of crops or can also be crop combinations like intercropping or mixed cropping.
  • Cropping system element: Select a predefined cropping system element during the creation of a cropping system.
  • Farm*: A farm needs to be associated to the Crop Zone and previously setup in the system.
  • Field*: A field needs to be associated to the Crop Zone and previously setup in the system.
  • Area: An area is already associated to a field, and once the field is selected, the area will be automatically defined. Generic entity to identify an area or terrain based on organizational, environmental attributes or operational needs. Areas can be hierarchical. Area definitions also can be time dependent. Areas can be specified with a geo shape (required for a lot of use cases), or abstractly by giving an absolute area (for example 5 hectares), or a relative area (percentage of another area). Examples of these are as follows: field boundaries, or soil zones.

    Note

    To learn more, consult the following link:API Guide for SAP Intelligent Agriculture - Area

Note

Link to the documentation: Planning your Fields and Tracking History

Log in to track your progress & complete quizzes