Disclaimer: This page was translated using automation resources in order to provide content in your language more quickly. As a result, it may contain grammatical errors and similar issues. If the content is not useful in this state, you can access the original content in Brazilian Portuguese at the bottom of the page, as well as provide feedback on this translation.

This manual is under construction. Therefore, some links may direct to pages with content under development.

Harvest Type

Harvest is the process of removing cultivated products from the land, which can involve various types of crops, such as grains, legumes, seeds, fruits, seedlings and even vegetables. This process is a crucial moment in agriculture, as it is the result of everything that was worked on during the cultivation process.

Harvest Type

The harvest work order is the last one to be executed, as it indicates the expected time for this process to be executed. Therefore, it will be possible to open a work order only when all previous processes Plantio and Lançamento de Estimativa, at a minimum, have been completed and, in fact, finalized, that is, when the status da cultura no talhão is Scheduled for Harvest.

Work orders of Standard Type Harvest, as registered on the Tipo de Ordem de Serviço (AGR0046) screen, do not have specific tabs, only specific fields when the standard crop on the Cultura (AGR0035) screen is Sugarcane.

Register in the Work Order Graphic Panel
  1. Access the menu Agricultural > Work Order > Work Order Graphic Panel (AGR0090);
  2. Click on Add ;
  3. To execute the registrations it will be necessary to fill in:
    • Location Type : mandatory field. Retrieves the values Agricultural, Others and Water Resources , and aims to direct to which type of location the services as a whole will be executed;
    • Production Unit : mandatory field. Retrieves the Unidade Produtora (ADM0012) registrations, used as a filter in the selection of Locations;
    • Project : mandatory field. Retrieves the Projeto (AGR0013) registrations, used as a filter in the selection of Locations;
    • Period : mandatory field. Retrieves the Safra (AGR0014) registrations, used as a filter in the selection of Locations;
    • Code : field locked for editing, depending on the parameterization executed on the Configurações do Modelo de Código (ADM0013) screen - Code Model Settings. The field has the standard functionality of generating a sequential code automatically, however, if necessary, when the field is available for editing, the user will be able to insert a manual code for the WO. When saving the record, when the field is empty, a unique and sequential code will be assigned for identification of this Work Order, following the code parameterizations executed on the Configurações do Modelo de Código (ADM0013) screen;
    • Opening : mandatory field, automatically filled in with the record creation date and time, and can be changed. Represents the start date of the Work Order, used in validations of work logs for the WO;
    • Closure : field locked for editing. Represents the closure date of the Work Order. This field will be automatically filled in when the user executes the Closure of the WO, informing the appropriate date and time in the closure modal;
    • Expected Start : informational field, represents the forecast for initialization of work on the Work Order;
    • Expected Completion : informational field, represents the forecast for completion of work on the Work Order;
    • Status : field locked for editing. Retrieves the values Registration in Progress, Awaiting Approval, Open, Canceled and Closed, and aims to inform the state in which the respective Work Order is;
    • Validate Third Party Contract : selection box that, when active, enables in the Operations tab the column to inform the Third Party Service Contracts that must execute the appropriate Operation of the Work Order. This information will be retrieved later in Work Logs and Routines of the Payments module - Third Party Services;
    • Work Order Type : mandatory field. Retrieves the Tipo de Ordem de Serviço (AGR0046) registrations, and aims to classify the Work Order among the standard types, which define rules and fields displayed in the appropriate WO registration.
    • Responsible for the WO : mandatory field. Retrieves the Employee Funcionário (ADM0025) registrations. This field aims to identify, for the respective Work Order, who will be the person responsible for the activities executed;
    • Team : mandatory field. Retrieves the Equipe (ADM0048) registrations. This field aims to identify, for the respective Work Order, which will be the team responsible for the activities executed;
    • Crop : mandatory field. Retrieves the Cultura (AGR0035) registrations. This field aims to identify which crop will be the target of the harvest activity that will be executed in the Work Order. The information in this field will be used as a filter in the selection of Work Order Locations and to define the fields that must be filled in the harvest grid.
Insert Harvest data
  • Purpose : mandatory field. Retrieves the Finalidade (AGR0047) registrations. This field aims to classify the destination of crops after harvest. The purpose information must be in accordance with the estimate entry executed for the location to be inserted in the work order, as the field will also serve as a filter to search for locations;
  • Variety : field becomes available for filling in when the seed category parameters are active Unidade Produtora (ADM0012) and Cultura (AGR0035);
  • Harvest Type : mandatory field. This field will only be available if the crop field is Mechanized or Manual;
  • Characteristic : mandatory field. This field will only be available if the crop field is filled in with a crop that has Sugarcane as the standard, on the Culturas (AGR0035) screen. The options are fixed and the user will be able to select if the harvested crop will be Raw or Burned.
  • Harvest Forecast Information:
    • Logged Area: should bring the total area of Locations informed in the appropriate work log of the WO. This field should bring the area measurement unit of the Pole, linked to the WO Production Unit;
    • Estimated Production: should follow the same rule as the Estimated Production field on the WO Creation/Editing screen, but in this case using the area informed in the appropriate work log for calculation. This field should also bring the default Measurement Unit of the Crop informed in its description.
    • Estimated Productivity: should follow the same rule as the Estimated Productivity field of the WO Creation/Editing screen, but considering the values of the Logged Area and Estimated Production fields of the appropriate work log. Should bring the mass and area Measurement Units in the description, as described in the same field of the WO Creation screen.
Harvest Planned vs Actual Data
  • Total Area: field locked for editing. This field is automatically filled in after saving the work order with the location area that was planned at opening.
  • Production : field locked for editing.
  • Harvest Forecast:
    • Planned Area;
    • Estimated Production ;
    • Estimated Productivity ;
  • Harvest Actual:
    • Actual Area ;
    • Actual Production ;
    • Actual Productivity ;
  • On the Motivo de Quebra de Produtividade screen, justifications will be informed when the Work Order is validated and presents a drop in productivity in relation to the planned.
Insert Location

Location : in the location grid, the user must select the map icon so that a modal is opened and, thus, it is possible to choose the locations that will be worked on. The selection occurs through filters applied field by field. For example: when selecting an associate (first division of locations), the other fields will be filtered, displaying only the farm, sector and plot linked to the selected associate.

An important observation is that the user does not need to follow a cascade selection he can, for example, select a plot directly, if desired. Even before the user starts the selection, the system already executes an automatic filter, displaying only the locations that have a registered estimate. Thus, it will not be necessary to execute subsequent validations, as the data presented already meet the required criteria.

  • When inserting a location in the WO that does not have area balance and/or does not have an estimate, the system displays an alert pointing out the inconsistencies. The system needs to validate what the inconsistency is and the message displayed must be exactly the error pointed out for error correction. Types of messages:
    • “Harvest location without area balance for harvest.”
    • “Harvest location without estimate entry posted for this purpose.”
    • “Harvest location without estimate entry posted for this purpose and without harvest area balance.”

In the scenario where Quota Control is performed, the AGR00550 – Cadastro de Equipe de Corte x Fornecedor x Propriedade Rural screen can be used to check the harvest Work Order (WO). This screen allows you to verify if there is a team available to perform the harvest.

Currently, when registering or editing a harvest WO, the system performs a validation when the parameter QuoValidateFieldsWorkOrder | Team validation in the Quota system, located on the Parâmetros (ADM0088) screen, is enabled. This validation verifies if the team informed in the WO is registered on the Cadastro de Equipe (AGR0550) screen for the Production Unit x Project combination. If so, the system also verifies if the Locations informed in the WO are linked to the same team.

Insert Basic Information
  1. After saving the work order creation, some additional buttons are made available, which perform distinct roles and have considerable impact on the Work Order:
    • Cancel Work Order : will be used when there is a need to discontinue the Work Order. After cancellation, the Work Order will be completely blocked for editing, remaining in the system only for history and checking purposes. This cancellation maneuver will only be allowed when the Work Order does not have any type of link or movement, such as Work Logs, Mechanization Reports, Weighings, Labor and Third-Party Service Work Logs or Integrations;
    • Work Order Posting : this button will be used when the creation of the Work Order is completely finished. From this moment on, Work Logs will be made, that is, the entries of everything that was actually performed/consumed by the Work Order;
    • Close Work Order : will be used when the work order logs are completely finished. From this moment on, the Work Order will be officially closed, keeping a history of everything that was planned (opening of the W.O.) and everything that was executed (W.O. logs);
    • History : this button will be used to perform a query of the information that was included, edited or deleted in the Work Order. Thus, it performs a function of displaying the change history;
  2. Click Save to register the record.
Insert Location data

The locations will be filtered based on the fields defined in the basic information, in addition to the crop status of the plot must be as Scheduled for Harvest and have the Lançamento de Estimativa (AGR0058) performed.

At this stage, the system validates the remaining area balance for the harvest operation, that is, if the total area of the plot has already been harvested, a red alert will appear.

Insert Operation data

In the Operation tab, the operations that are part of the harvest process must be selected. An important point is that, for the area to be counted as harvested, the operation needs to be properly parameterized to perform the harvest area posting on the Operação (ADM0041) screen.

The harvest can happen in a total or partial way, thus differentiating the plot statuses as Partial Harvest and Closed.

  • Partial Harvest : in this case, only part of the crop is harvested at a given time, with a difference between the area that was planted and the harvested area. This can be done when part of the fruits or grains reach a certain stage of maturation;
  • Closed Harvest : in this method, all the crop that was planted is, in fact, harvested;
  • Total Harvest : in this method, all the crop that was planted is, in fact, harvested;
Insert Resource data

The resource tab is intended for selecting products and/or services that will be consumed by the Work Order. At this moment, for each operation of the Work Order, the user has the possibility to include the resources that will be consumed by the respective operation.

For it to be possible to include resources in the Work Order, the operation must be parameterized to allow such action. This parameterization is performed on the Operação (ADM0041) registration page, from the Agricultural inputs Application selection field, which needs to be active for this to be possible.

Cultural Treatment work orders do not necessarily have resources linked to it, but the use is common for this type of WO.

The inclusion of Resources to the Work Order is commonly linked to the process of reserving Items in ERP systems, for later consumption of these through the WO Work Log.

  1. This reservation process occurs after the inclusion of the Resource through the fields:
Product Selection
  • Product : mandatory filling. This option aims to classify the resource that will be consumed as a product. Once selected, the entire tab layout will be changed to accommodate the inclusion of a product;
  • Item : mandatory filling. Retrieves the Item (ADM0034) records. In this field, only records classified as Product and parameterized for Agricultural inputs Application are retrieved;
  • Dose : mandatory filling. When selecting this option, the Dose field will be enabled for editing and the Quantity field will be calculated (blocked for editing). This field aims to show the dose for application of the respective product;
  • Dose per Pump ;
  • Stock Location : automatic filling field according to the Item x Stock Location selected previously. This refers to the information from the ADM0050 screen.
  • Branch : automatic filling field according to the Branch linked to the Stock Location presented previously. According to the system parameterization, there may be more than one Branch linked to the same Stock Location, for this scenario, this field may be released to change the value, according to the need. This information will be used in integration routines to inform the Branch of the Product write-off.
  • Unit Price : automatic filling field, the information comes via integration routine, which retrieves this value from the Resource control ERP systems.
  • Total (value): automatic filling field. Presents the expected total value of the Resource use in the WO. Retrieves the information from the Unit Price and the Quantity informed.
Service Selection
  • Service : mandatory field. This option aims to classify the resource that will be consumed as a service. After selected, the entire tab layout will be changed to accommodate the inclusion of a service;
  • Item : mandatory field. Retrieves the records from Item (ADM0034). In this field, only the records classified as Service and parameterized for Agricultural inputs Application are retrieved;
  • Supplier : mandatory field. Retrieves the records from Cliente/Fornecedor (ADM0007);
  • Quantity :mandatory field. This field aims to show the total quantity of the service that will be consumed in the Service Order;
  • Unit Price : manual field, informs the value of the service per unit logged.
  • Total (value) : automatic field. Presents the total expected value of the Resource usage in the SO. Retrieves the information from the Unit Price and the Quantity informed.

Este artigo ajudou você?