In this section we will run one of the many jobs that can be
processed through the xTuple Connect Batch Manager. The job we will use
for this scenario is an Actual Cost update. This is a perfect candidate
for a xTuple Connect Batch Manager submission because it is a
resource-intensive operation involving multiple database updates.
Depending on the number of Items in your product catalog, an Actual Cost
update can take up to several hours to complete. As a general rule, these
kinds of jobs are better run after hours when the server is not busy with
production requests from multiple logged-in users.
