Task Order Inference

When the Task Order Chart of Account (COA) is being used to track a task performed as part of a project or not, there are times when certain COA should infer based on the Task Order. The Task Order Inference (TOINF) is the method to define these inferences. The inference may be for the only value that should be used by the Task Order or may be the most common default where users know to change the value when it is an exception. The Streamlined Task Order Billing feature of Cost Accounting is one such case of a single value for Program being inferred. It may also be for the only Phase as well as the most common Phase.

There are four additional COA available for inference that are initially hidden from view but can be made visible with Configure Page (DESIGNER): Activity, Location, Sub Location, and Function. At least one of the six inference fields must be defined. Those Task Orders that do not need the inference or do not desire the inference do not have to be listed on TOINF.

Field InformationField Information

Beyond the chart-of-account fields present (see the Chart of Accounts User Guide) there is one uncommon field:

Field Name	Description
Program Inference Type	The inference behavior of the page is Soft (also known as a weak inference) by default unless changed with a Configurable Formula. Soft results in any value set up on an inference only populates a blank transaction field. This means that a user or interface can supply a different value, and what is set up on the inference is only a default if no other is used. A value to Hard (also known as a powerful inference) results in an inference overwriting any existing transaction value. Furthermore, if the COA field on the inference is blank and Hard is the setting, that means the corresponding transaction field will be cleared. In summary, that COA cannot be used with the program.

Field Name

Description

Program Inference Type

The inference behavior of the page is Soft (also known as a weak inference) by default unless changed with a Configurable Formula. Soft results in any value set up on an inference only populates a blank transaction field. This means that a user or interface can supply a different value, and what is set up on the inference is only a default if no other is used.

A value to Hard (also known as a powerful inference) results in an inference overwriting any existing transaction value. Furthermore, if the COA field on the inference is blank and Hard is the setting, that means the corresponding transaction field will be cleared. In summary, that COA cannot be used with the program.