ChartField Values

If you use the ChartFields as delivered by PeopleSoft, sample ChartField values are already set up and in many cases are populated with sample amounts. All PeopleSoft sample or model values are entered with the 01/01/1900 effective date. To distinguish your data avoid using this date and instead use another early date, such as 01/01/1901.

You can enter an unlimited number of values for each ChartField. You can enter values using the online ChartField Values page, but because of the volume of entries needed to populate some ChartFields, you might use a batch import process or the Microsoft Excel spreadsheet for the PeopleSoft Component Interface process to initially load values to ChartField tables.

The project ChartFields component interfaces mentioned in the previous ChartField listing are more fully described in the Project Costing documentation.

See Loading ChartField Values Using the Excel Spreadsheet to Component Interface Process.

Note:

PeopleSoft recommends that you not use special characters and embedded blanks in ChartField values. Use the generally accepted alphanumeric characters and the underscore. In general avoid special characters such as apostrophes and do not include embedded blanks when defining ChartField values. Special characters and embedded blanks can be problematic and in particular can cause problems in some batch processes, such as those in allocations, combination editing and open item accounting. (This caveat also applies to such things as business units, ledgers and journal IDs.)

Because changes to the definition of most ChartField value are effective-dated, you can establish when you want to activate a department, introduce a product line, or close an account. Use effective dating with activation and inactivation functionality to maintain a full history of all changes or additions, to provide a complete audit trail and to make possible historical comparisons with past, present, or future conditions. When you no longer use a certain ChartField value, add a row to create an effective-dated inactive entry, instead of inactivating the original row. If you simply make the existing row inactive, you will have no history of its time as an active ChartField value.

Project ChartField values can be made active or inactive, but the values cannot be effective-dated for status.

However, the project status of a project can be effective dated for these statuses: budgeted, closed, hold, open, and proposed if Project Costing is not installed. These statuses are memo data only and do not provide control functionality.