The posting of product application to Field History is a user-initiated function. This may be done for all fields or for a specific field.
See here for the process of using the Transfer to Field History utility.
How to Post History for All Fields at Once
To post history for all fields for a specified range of transactions, go to Hub / Utilities / Transfer to Field History.
Any transaction posted to Field History is marked in such a way that it cannot be posted to Field History again or edited. Voids of Invoices previously posted to Field History display a message informing the user to manually delete the field history entry. The Rate/Acre saved for Delivery Tickets that post are calculated using Field Acres = 1. Invoices use the acres saved on the Additional Info tab and use 1 if those acres have not been set.
This function posts all loaded Blend Tickets, loaded, by field Delivery Tickets and by field Invoices that didn’t originate with Delivery or Blend Tickets and reversals of these transactions. To skip non-invoiced Blend Tickets or Delivery Tickets, do not place a check in the Include Non-Invoiced box. These skipped tickets will transfer after they are invoiced and the utility is run again.
How to Post History to a Specific Field
To post to a specific field, edit the field and on the History tab select Import New History. The Transfer to Field History screen appears allowing selection of the types of transactions to be transferred.
Unposted Transactions at End of Year
There is a notification before proceeding at End of Periods / Fiscal Month (when it’s the 12th month) and at Blending / Utilities / Purge Blend Tickets if transactions exist that are not yet posted to the field history (Blend Tickets, when using the Purge Blend Tickets function, direct Invoices and Delivery Tickets when ending the fiscal year).
