The City’s new financial and procurement system is implemented through Oracle PeopleSoft, which has some unique terms, including “Chartfield.”

In This Article:

  • What is a ChartField?
  • Translation from FAMIS
  • Where did Index Codes go?

The term “ChartField” is best understood as a code that specifies organizational category, such as Account, Department, Fund, Authority, Project/Activity. A ChartField “ID” is a specific numeric entry which identifies a specific record within the ChartField category. Most importantly, a ChartField "String" is a combination of Chartfield values together (kind of what Index codes used to do). 

For example, Department is a ChartField, and AIR would be a ChartField value plain English description, and that would have a specific ID number associated with that Department. 

This link will bring you to the crosswalk files that translate index codes, and the above FAMIS elements into their new PeopleSoft values:

The following diagram translates the organizational categories used in the previous financial system into the categories the City will use with the current financial system. For users that are new to the City and County of San Francisco, the following illustration will not be necessary (or helpful).

In addition to a slight modification in categories and naming, the new system eliminates Index Codes (and removes Smart Coding everywhere except for Account). While every Chartfield value will have a unique numeric ID, the plain English Chartfield String can be used to identify values without memorizing numeric codes. Additionally, partial terms and phrases can be used to search for intended Chartfield values, allowing for reference look ups by ID number, or by English phrasing.  

There will not be any shortcut keys in PeopleSoft, however values established in a submodule carry over to other documents. For example, Purchase Order information will carry to invoice payments, or contract info would copy over to an accounts receivable transaction. 

Users must enter all ChartFields associated when posting a transaction in the General Ledger or Commitment control module. ChartFields will not self-populate,

which safeguards against transactions posting against incorrect accounts or to incorrect projects, etc.