Banner Finance Plain and Simple – Rule Classes and Process Codes
created (edited ) in Banner Finance
Previously we shared information about creating custom rule classes. (Banner Finance Plain and Simple – Custom Rule Classes and Edits) This article will focus on general information about Rule Classes, and in particular the process codes.
What are rule classes?
Rule classes (sometimes referred to as rule codes or journal types) drive all transactions in Banner. They tell the system where and how transactions should be processed and allow limitations on how transactions can be entered. Rule classes (particularly journal based ones) can be customized to meet your institutional needs.
How do I use rule classes?
When you create a journal entry, the Journal Type is actually a rule class (for example JE16.) Rule classes are also hidden behind the scenes and create entries when you transact with purchase orders, invoices, fixed assets, etc. If you are interested in looking at rule classes, you can view the details on FTMRUCL form.
What are the components of a rule class?
Rule classes are comprised three parts:
- A header that tells the system how the rule class works.
- Edits that tell the system what is or isn’t allowable for particular fields
- Process codes that tell the system what actions to take and where to post the transaction information
How do the process codes work?
Process codes tell the system what actions to take with the information provided in the transaction form in Banner. There are four key types of process codes in Banner:
|
Process Code
|
Prefix
|
Example
|
Explanation
|
|
Initiator
|
I
|
I061
|
Must be the first Process Code on all Rule Classes
Determines whether debits and credits or +/- are used and how they are interpreted
|
|
Operating Ledger
|
O
|
O030
|
Used to post entries to the operating ledger (budget, year-to-date, reservation and/or encumbrance fields)
|
|
General Ledger
|
G
|
G010
|
Used to post entries to the general ledger
|
|
Encumbrance Ledger
|
E
|
E010
|
Used to post encumbrance and reservation entries
|
Different process codes will create different types of postings, and to different fields depending on the codes used. A series of process codes are strung together to create all of the individual postings that hit the Banner ledgers.
Below is an example of the process codes for a journal voucher that allows posting of operating and general ledger accounts:
|
Code
|
Explanation
|
|
I061
|
Allows input of a debit/credit
|
|
O030
|
Post to the year to date actual in the operating ledger
|
|
G010
|
Post to the general ledger
|
|
G030
|
Post inter-fund due to/due from
|
If you have access to the FTMRUCL screen, you can see all the process codes available by clicking on the drill down beside the Process code field on the Process Code Details block.
Hopefully this goes a little way in making the rule classes, and the process codes in particular a little less mysterious.