Examples of Delivered COA Inferences

It is a good idea to check Configure Page (DESIGNER) to determine if there are any hidden fields on any of these pages that could provide the inferences desired.

  • Program Inference (PINF) - When a single value, or most common value, should infer for a Program, this page can be used to establish that default for at least one or more of Activity, Function, Location and Fund.  The inference type, powerful or weak, is defined on the Department Fiscal Year (DEPTFY) page.

  • Activity Inference (ACTINF) - When a single value, or most common value, should infer for an Activity and Function, this page can be used to establish that default for at least one or both Fund and Program.  

  • Appropriation and BFY Inference (APBYINF) - This inference page is one loaded by the creation of budget lines on certain budget structures and levels, with matching key fields, so that users do not have to enter the one Appropriation that exists for those keys as well as the special multi-year value for Budget Fiscal Year - 9999.  While it could infer a normal year, that is not the intention of the page nor what is created automatically with new budget lines.

  • Appropriation and BFY Inference with Activity (APBYINF2) - This inference page is one loaded by the creation of budget lines on certain budget structures and levels, with matching key fields, so that users do not have to enter the one Appropriation that exists for those keys as well as the special multi-year value for Budget Fiscal Year - 9999.  While it could infer a normal year, that is not the intention of the page nor what is created automatically with new budget lines.

  • Appropriation Inference (APPRINF) - This inference page is one loaded by the creation of a budget line on certain budgets structure and levels so that the powerful inference happens.

  • Appropriation Inference with Activity (APPRINF2) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that the powerful inference happens.

  • Appropriation Inference with Function (APPRINF3) - This inference page is one loaded by the creation of a budget line on certain budget structures and levels so that the powerful inference happens.

  • Appropriation Unit Inference (APPRUINF) - This page allows you to define an Appropriation to infer and is not populated with the creation of a budget line. 

  • Revenue Source Appropriation Inference (RSAPRINF) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that the powerful inference happens.

  • Unit Sub Unit Appropriation Inference (USAPPINF) - This inference page allows the inference of the Appropriation based on the combination of Department, Unit, and Sub Unit. This inference will only populate a blank field as it is not a powerful one.

  • Budget Fiscal Year Inference (BFYINF) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that a powerful inference happens. While it could infer any Budget Fiscal Year, the intention (and automatic population) is to infer only the special year of 9999.

  • Revenue BFY Inference (BFYINFRV) - This inference page is one loaded by the creation of a budget line on certain budget structures and levels so that a powerful inference happens with BFY 9999 so that users do not have to enter the year to match a revenue budget line. While it could infer any Budget Fiscal Year, the intention (and automatic population) is to infer only the special year of 9999.

  • Budget Fiscal Year Inference by Fund and Sub Fund (BFYINFSF) - This inference page allows the inference of the multi-year BFY value of 9999 when one of the inferences pages created through budget line creation is not used.

  • Object Appropriation Inference (APOBJINF) - This inference page allows the inference of Appropriation from Object when one of the inferences pages created through budget line creation is not used.

  • Revenue Appropriation Inference (APREVINF) - This inference page allows the inference of Appropriation from Revenue when one of the inferences pages created through budget line creation is not used.

  • Sub Fund Revenue Source Appropriation Inference (SFRAPINF) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that the powerful inference happens.

  • Sub Fund Object Appropriation Inference (SFOAPINF) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that the powerful inference happens.

  • Sub Fund Object Appropriation and BFY Inference (SFOABINF) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that the powerful inference happens. While it could infer any Budget Fiscal Year, the intention (and automatic population) is to infer only the special year of 9999.

  • District/Location Unit Inference (DILOUINF) - This page allows you to define a Unit to infer.

  • Infer Department and Unit (INFDU) - This inference page is not read by all types of transactions and is used solely in the Treasury Accounting area of CGI Advantage to supply organizational chart of accounts for the Pool Fund Investment Earnings (PFIE) transaction and the journal voucher transactions created by the Cash Sweep and Income Allocation system processes.

  • Object Inference (OBJINF) - This inference page allows for the powerful inference of Object based on a department object when there is a 1:1 or 1:n relationship between an object and department object.

  • Department Object Inference (DOBJINF) - This inference page allows for the weak inference of Department Object based on a system-wide object when there is a 1:1 or 1:n relationship between a department object and object. The travel transactions are a common area for use of this page as there is only the inference of an Object from an Expense Type.

  • Revenue Source Inference (RSRCINF) - This inference page allows for the powerful inference of  Revenue Source based on a department revenue source when there is a 1:1 or 1:n relationship between revenue source and department revenue source.

  • Organizational Inference (ORGINF) - This inference page allows for a weak inference of one or more chart of account fields based on organizational information and the type of transaction.

  • Organizational Inference 2 (ORGINF2) - This inference page allows a weak inference of one or more chart of account fields based on organizational information, without respect to the Transaction Category as with Organizational Inference (ORGINF). The system reads ORGINF before it reads ORGINF2, meaning that if the same COA fields are used on matching records on both pages, the value to be inferred from ORGINF will be placed on a transaction.

  • Organizational Appropriation Inference (ORGAPINF) - This inference page allows for a powerful inference of Appropriation based on a combination of department, unit, and fund. This inference page is one loaded by the creation of a budget line on certain budget structures and levels.

  • Function Inference (FUNCINF) - This inference page allows the inference of one or more chart of account fields based on function. Of note, a field for Function Type is available and inferred to define Configurable Rules stating what fields should be completed to provide controls when needed that vary by ‘type of function’.

  • Fund Sub Fund Inference (FSFINF) - This inference page is one loaded by the creation of a budget line on certain budget structure and levels so that the powerful inference happens.

  • Sub Fund Inference (SFUNDINF) - This inference page allows the weak inference of Sub Fund based on the combination of Fiscal Year and Fund.

  • Accounting Template (ACTPL) - This page is used to create templates of mutliple chart of account elements. Unlike other smaller more targeted inferences, this one has all chart of accounts plus Debt ID, Fiscal Year, and Budget Fiscal Year. The Accounting Template is the very last inference done on a transaction and is a weak inference. Budget Fiscal Year and Fiscal Year are exceptions in that they are powerful inferences and happen only on a new transaction line and only happen if there is no reference to another line.

Please be aware that templates with a year defined to them where the year is not part of the Template ID, changing that year to the following year means that users must manually make updates on transactions to match the prior year for accruals that have no reference.  A year worked into the Template ID enables two different records with different COA.  With this latter method, interfaces must be updated with the new value and know to use the old value when impacting the prior year.

Accounting templates are also found on other reference data pages to facilitate data entry such as Internal Vendor Accounting (IVAD) and Procurement User (USER) to name a few.

The first Department field is not a key field, so that the same Accounting Template ID can be used with multiple Departments.  This first Department exists for row-level security and row filtering.

The page contains additional fields that are initially hidden but can be made visible:

  • A set of fields tracking who and when a template was created by and created on as well as a pair of fields tracking last modification.

  • There are five flags available to classify templates as needed for interfaces.

  • Two active dates are available to define a date range when interfacing templates to a 3rd party system such as a payroll system. The dates can also be used to track any event necessary with a template and not an active range. Because the dates are open to any use, there are no edits other than a valid date, so if used as active dates, a Configurable Validation should be added to ensure the ‘to’ is after the ‘from’. Furthermore, the application will view a template as invalid if used out of those dates.

One or more accounting templates can be combined into an accounting profile to generate accounting lines on many different transaction types. For more information on the accounting profile, see the “Accounting Templates and Accounting Profiles” topic in the Transactions User Guide.

There are other inference pages available, but they are tied directly into Cost Accounting and more information on them can be found in the CGI Advantage - Cost Accounting User Guide.

  • BFY Funding Profile Inference (FPIBFY)

  • Funding Profile Inferences 1 (FP1)

  • Funding Profile Inference 2 (FP2)

  • Funding Profile Inference 3 (FP3)

  • Funding Profile Inference 4 (FP4)

  • Funding Profile Inference 5 (FP5)

  • Funding Profile Inference 6 (FP6)

  • Funding Profile Inference by Object (FPIO)

  • Funding Profile Inference by Activity and Location (FPIAL)

  • Funding Profile Inference by Program Period and Task (FPIPPT)

  • Funding Profile Inference by Program Period and Appropriation (FPPPAPPR)

  • Funding Profile Inference by Reporting (FPIR)

  • Task Order Funding Profile Inference (TOFPI)