3305 Main Street Ste 019 Vancouver, WA 98663

Why does Integrator indicate that a contract's rules don't allow overbilling even though its contract rules show it as "Uncontrolled total"?


When Integrator is attempting to send Contract Invoices from Job Cost to Prolog, it checks to make sure that Prolog business rules will not be violated. In doing so, it first looks at the contract rules. If the rules indicate "Controlled Totals" are being used, it will check to see if the addition of the new contract invoice would exceed the contract value for a any given line item. If so, the cost is rejected.


The contract rules selection for each contract is stored in two fields in the Prolog database (specifically in the Contracts table). One field (RulesCode) stores the rules selection as a number (where 1 represents "Controlled" and 2 represents "Uncontrolled"). The second field (Rules) stores the text representation ("Controlled" or "Uncontrolled"). It is the value of this field that is seen when viewing the contract within Prolog however the field containing the code number is what is used when applying business rules. On rare occasion these two fields become out of sync. This may make it appear that an "Uncontrolled totals" contract is behaving as if it is a "Controlled totals" contract.

If you posses the ability to run simple SQL queries off your Prolog database, you can check for instances of this issue by executing the following query:

  [Projects].[Number] AS [ProjectNumber],
FROM [Contracts]
  LEFT OUTER JOIN [Projects] ON [Projects].[ProjectID] = [Contracts].[ProjectID]
  ([RulesCode]=1 AND [Rules]<>'Controlled Total')
  OR ([RulesCode]=2 AND [Rules]<>'Uncontrolled Total')

Since this issue is due to an inconsistency in your data, please contact either your Event 1 Software or Trimble Prolog technical support representative to resolve the issue.