As initially configured, the transaction pages within the Financial area of CGI Advantage display most, if not all COA fields, although each implementation may not use them all. In some cases, COA are just not used based on the type of transaction – Requisitions and the Balance Sheet Account fields. While in other cases, a COA may not be used on any transaction. While Configure Page (DESIGNER) can be used to hide or rearrange these different instances of COA, the Transaction COA Display Configuration (COACONF) page exists to hide or rearrange COA across the multiple transaction types with a single update. Use of this page typically happens once, unless a future need requires a previously hidden COA field to be revealed on a wide basis.
After setting the desired configurations, the page extensions are generated in bulk. Please verify the extensions and then add the extensions to the migration queue. Once the generated COACONF page extensions have been added to the migration queue, you will need to run the Designer to XML Synchronization Process and deploy the extensions to complete the configuration. If extensions are synchronized to XML successfully, the system updates the Extension Status on COACONF to Synchronization Complete. If there are problems, the system updates the Extension Status to Error. More complete information can be found in the CGI Advantage - Administration Utilities Run Sheets Guide and the CGI Advantage - Extract Deploy Extension Metadata Guide.
Please Note:
If a user attempts to extend a transaction page using DESIGNER and a COACONF extension for the same transaction page is in progress, a warning will be displayed on DESIGNER stating that the user will not be able to apply, revert, add to or remove from migration queue using DESIGNER until the generated page extensions are synchronized or cancelled.
Conversely, do not attempt to perform configurations using COACONF while actively applying configurations using DESIGNER.
Non-transactional pages that list COA such as the Accounting Template, Chart of Account Crosswalk, and Automatic Transaction Corrections are not updated by this page and must be updated through Configure Page.
Landing View
Detail View
Implementation Considerations:
Grid rank values: In the grid, COA fields usually appear after other fields and before Attachments. You can specify grid rank values starting with the value 500 and using an increment of 10 to make the COA fields appear between the starting fields and Attachments. Below are suggested values covering the fields that can appear on the grid out-of-the-box.
COA Field |
Grid Rank |
Fund |
500 |
Department |
510 |
Unit |
520 |
Object |
530 |
Revenue |
540 |
Activity |
550 |
Scalar rank values: You can specify scalar rank values starting with the value 10 and using an increment of 10. Below are suggested values that can be used as a starting point.
COA Field |
Scalar Rank |
COA Field |
Scalar Rank |
|
Fund |
10 |
Activity |
190 |
|
Sub Fund |
20 |
Sub Activity |
200 |
|
Department |
30 |
Function |
210 |
|
Unit |
40 |
Sub Function |
220 |
|
Sub Unit |
50 |
Location |
230 |
|
Appr Unit |
60 |
Sub Location |
240 |
|
Object |
70 |
Task Order |
250 |
|
Sub Object |
80 |
Task |
260 |
|
Dept Object |
90 |
Sub Task |
270 |
|
Revenue |
100 |
Major Program |
280 |
|
Sub Revenue |
110 |
Program Period |
290 |
|
Dept Revenue |
120 |
Program |
300 |
|
BSA |
130 |
Phase |
310 |
|
Sub BSA |
140 |
Funding Profile |
320 |
|
OBSA |
150 |
Funding Priority |
330 |
|
Sub OBSA |
160 |
Funding Line |
340 |
|
Reporting |
170 |
Internal Fund |
350 |
|
Sub Reporting |
180 |
Internal Sub Fund |
360 |
|
|
Internal Dept |
370 |