ChartField Reporting Requirements Analysis
When planning how to configure your ChartFields to meet your reporting requirements, consider the following questions:
-
How many ChartFields do you need?
-
Can the existing active ChartFields meet your requirements or do you need to activate any of the expansion ChartFields 1, 2, or 3?
-
Do you need to add additional ChartFields beyond the expansion ChartFields? This affects future upgrades and application fixes, making them more complex. Oracle recommends using all of the delivered ChartFields first before considering adding a new one.
-
What should the length of each ChartField be?
-
What descriptive labels (long and short) do you want to appear on pages and reports for each ChartField?
-
In what order do you want the ChartFields to be displayed?
-
Do you use alternate account functionality? If so, the alternate account must be active.
-
Have you implemented PeopleSoft Project Costing, Expenses, Resource Management, or Services Procurement? If so, PC Business Unit & Activity must be active.
-
Have you implemented PeopleSoft Expenses, Asset Management, or Resource Management? If so, the Department ChartField must be active.
-
Are you using the InterUnit functionality? If so, Affiliate must be active.
-
Are you using the IntraUnit functionality? If so, one or both IntraUnit Affiliate ChartFields must be active.
-
How many intraunit balancing ChartFields do you require, if any, and what are their related ChartFields?
-
Do you want to rename any of the delivered ChartFields? Oracle strongly discourages this because it makes applying future upgrades and application fixes more complex. Instead, Oracle recommends that you relabel the ChartField.
-
Do you want to delete any of the delivered ChartFields? Oracle strongly discourages this because it makes applying future upgrades and application fixes more complex. Instead, Oracle recommends that you inactivate the ChartField.
-
Do you want to reduce the field length of any of the delivered ChartFields? Oracle strongly discourages this because it makes applying future upgrades and application fixes more complex. Instead, Oracle recommends that you reduce the display length of the ChartField.