Finance 80500 U

BANNER FINANCE USER GUIDE
Release 8.5 November 2010
Trademark, Publishing Statement and Copyright Notice

SunGard or its subsidiaries in the U.S. and other countries is the owner of numerous marks, including SunGard, the SunGard logo, Banner, PowerCAMPUS, Advance, Luminis, DegreeWorks, fsaATLAS, Course Signals, and Open Digital Campus. Other names and marks used in this material are owned by third parties. 1991-2010 SunGard. All rights reserved. Contains confidential and proprietary information of SunGard and its subsidiaries. Use of these materials is limited to SunGard Higher Education licensees, and is subject to the terms and conditions of one or more written license agreements between SunGard Higher Education and the licensee in question. This PDF is certified for use with Adobe Reader, version 6.x and higher. Some elements of this PDF may not render properly when viewed using earlier versions of the Acrobat Reader or with other PDF viewing applications. In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organizations own choosing.
Prepared by: SunGard Higher Education

4 Country View Road Malvern, Pennsylvania 19355 United States of America
Customer Support Center Website

http://connect.sungardhe.com
Documentation Feedback
http://education.sungardhe.com/survey/documentation.html
Distribution Services E-mail Address

distserv@sungardhe.com
Revision History Log Publication Date

November 2010
Summary
New version that supports Banner Finance 8.5 software.
Banner Finance 8.5 User Guide
Contents
Chapter 1 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Banner Finance System Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . 1-2 Major Features of Banner Finance . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Module Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 General Ledger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Finance Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Stores Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Purchasing and Procurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Accounts Payable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Budget and Position Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Fixed Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Cost Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Endowment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Accounts Receivable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Research Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Process Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 General Ledger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Stores Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Purchasing and Procurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Accounts Payable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Budget and Position Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Fixed Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Cost Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
November 2010
Banner Finance 8.5 User Guide Contents
iii
Endowment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Accounts Receivable

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Research Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Chapter 2
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Oracle Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Banner Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Banner Finance System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Elements of the FOAPAL String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Recommended Order for Chart of Accounts Setup . . . . . . . . . . . . . . . . . . 2-12 Creating a Chart of Accounts Record. . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Alternatives for Cash Accounts and Bank Funds . . . . . . . . . . . . . . . . . . . 2-15 Cash Accounts In Foreign Currency . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 Budget Entries Only to Pool Accounts . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 Multiple Fund Balance Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 General Ledger Consolidated Postings . . . . . . . . . . . . . . . . . . . . . . . . 2-20 General Ledger Summary Postings . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 Transaction Interface Process (FGRTRNI) . . . . . . . . . . . . . . . . . . . . . . 2-23 Available Balance Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 Effective Date Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32 Pro-Rata Cost Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33 Governmental Accounting Standards Board (GASB) Reports Processing . . 2-39 GASB 35 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 GASB 34 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40 GASB Extract Process (FGPGEXT) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40 GASB Reclassification Entry Form (FGARCLE) . . . . . . . . . . . . . . . . . . . 2-41 Transaction Reclassification Query Form (FGIRCLE) . . . . . . . . . . . . . . . . 2-42 GASB Parameter Form (FGAGASB) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42 Changing Attribute Types and Values . . . . . . . . . . . . . . . . . . . . . . . . . 2-44 Associating FOAPAL Elements to Attributes . . . . . . . . . . . . . . . . . . . . . . 2-45 Setting up Program / Account Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46 Setting up GASB 35 Public Institution Business-type Activity Statements . . . . . 2-46
iv
November 2010
Setting up GASB 34 Governmental Funds Statements . . . . . . . . . . . . . . . . 2-48 Setting up GASB 34 Government Wide Statements . . . . . . . . . . . . . . . . . 2-50 Producing GASB Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52 General Accounting Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54 Creating a Journal Voucher Entry Transaction . . . . . . . . . . . . . . . . . . . . 2-54 Automatic Journal Voucher Process . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57 Rule Code Balancing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59 Processing a Cash Receipt From a Vendor . . . . . . . . . . . . . . . . . . . . . . 2-60 Defaulting Feature in General Accounting Transaction Forms . . . . . . . . . . . 2-64 Redefaulting FOAPAL Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65 Making Adjustments to an Existing Encumbrance . . . . . . . . . . . . . . . . . . 2-68 Net Total Fields on General Accounting Query Forms . . . . . . . . . . . . . . . . 2-70 Year-End Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71 Rolling an Encumbrance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74 Concurrent Year Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80 Posting of Liquidations in the Prior Fiscal Year . . . . . . . . . . . . . . . . . . . . 2-82 Creating an Original 1099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-85 Creating a Correction 1099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86 Querying Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87 Performing a Query for Specific Date . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88 Formatting Preferences on Query Forms . . . . . . . . . . . . . . . . . . . . . . 2-89 Research Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90 Proposal Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90 Grant Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93 Grant Billing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96 Trail-in and Trail-out Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-98 Cost Share Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-98 Indirect Cost (F & A) Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99 T Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101 Online vs. Deferred Grant Accounting Process . . . . . . . . . . . . . . . . . . . . 2-103 Grant Budgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104 Proposal and Grant Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104 Agency Funding Information for Grants and Proposals . . . . . . . . . . . . . . . 2-107 Setting up Banner Finance Forms for Effort Certification . . . . . . . . . . . . . . 2-108 Grant Billing Detail Table (FRRBDET) . . . . . . . . . . . . . . . . . . . . . . . . . 2-108
November 2010
Generating Bills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-110 Reversing a Bill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-118 Bill Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-119 Prior Period Reversals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-123 Payments Received From a Sponsoring Agency . . . . . . . . . . . . . . . . . . . 2-125 Reversal of Applied Payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-129 Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-129 Interfacing Grant Information From an External System to Banner . . . . . . . . . 2-130 Finance Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157 Currency Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157 Identifying Persons and Entities in Banner Finance . . . . . . . . . . . . . . . . . 2-161 Adding Vendors to Banner Finance . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-164 Adding Financial Managers to Banner Finance . . . . . . . . . . . . . . . . . . . . 2-166 Adding Agencies to Banner Finance . . . . . . . . . . . . . . . . . . . . . . . . . . 2-169 Adding Customers to Banner Finance . . . . . . . . . . . . . . . . . . . . . . . . . 2-171 Adding Employees to Banner Finance . . . . . . . . . . . . . . . . . . . . . . . . . 2-171 ID Definition Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-172 ID and PIDM Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-173 Receiving/Matching Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-173 Receiving/Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-173 Document Level Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-176 Internal Vendor Order Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 2-184 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-184 Internal Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-184 Things to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-185 Internal Vendor Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-185 Internal Vendor Order Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-187 Approvals Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-191 Required Forms and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192 Approvals Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-193 Cancelling a Document After Final Approval . . . . . . . . . . . . . . . . . . . . . 2-196 Cancelling a Requisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-196 Approval Queue Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-197 Queue Routing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-199
vi
November 2010
Direct Cash Receipt Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-200 Document Level Accounting and Commodity Level Accounting . . . . . . . 2-201 Document Level Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-201 Commodity Level Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202 Commodity Level vs. Document Level Accounting . . . . . . . . . . . . . . . . . . 2-204 Automatic Accounting Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . 2-206 Automatic Accounting Reallocation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-207 Request Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-209 Creating a Requisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-209 Entering Currency Conversion Information on a Requisition . . . . . . . . . . . . 2-209 Purchase Order Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212 Creating a Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212 Creating a Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-214 Querying a Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-221 Processing a Blanket Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-221 Commodity Level Accounting With a Purchase Order . . . . . . . . . . . . . . . . 2-224 Assigning Requisitions to a Purchase Order . . . . . . . . . . . . . . . . . . . . . 2-224 Opening and Closing Items on a Purchase Order or Requisition . . . . . . . . . . 2-225 Procurement Card (PCard) Processing . . . . . . . . . . . . . . . . . . . . . . . 2-226 Considerations Before Using PCard Processing . . . . . . . . . . . . . . . . . . . 2-226 PCard Setup Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-227 Initializing PCard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-228 PCard Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-239 Bid Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-241 Receiving Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-242 Creating a Receipt of Goods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-242 Entering Packing Slip Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-243 Entering Purchase Order Information. . . . . . . . . . . . . . . . . . . . . . . . . . 2-243 Accounts Payable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-246 Running Banner Bank Reconciliation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-246 Creating a New Vendor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-248
November 2010
vii
Establishing Tax Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-251 Specifying a Default Rebate Accounting Distribution . . . . . . . . . . . . . . . . . 2-253 Establishing Multiple Rebate Percentages . . . . . . . . . . . . . . . . . . . . . . . 2-253 Creating Tax Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-255 Associating Tax Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-256 Invoice Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-256 Selecting the Invoice Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-256 Choosing Document or Commodity Level Accounting . . . . . . . . . . . . . . . . 2-257 Using the Invoice/Credit Memo Form (FAAINVE) . . . . . . . . . . . . . . . . . . . 2-257 Invoices for Purchase Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-265 Bank Code Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-265 One-time Vendors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-266 Viewing Vendor Invoice Detail Information . . . . . . . . . . . . . . . . . . . . . . . 2-267 Viewing Vendor Invoice Information . . . . . . . . . . . . . . . . . . . . . . . . . . 2-267 Recurring Payables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-268 Creating a Zero Amount Payable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-269 Stores Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-269 Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-270 Returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-270 Entering Cost Adjustments to Physical Inventory . . . . . . . . . . . . . . . . . . . 2-270 Determining Inventory Adjustment Status . . . . . . . . . . . . . . . . . . . . . . . 2-271 Using Stores Issues and Returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-273 Entering ABC Classification Tolerances . . . . . . . . . . . . . . . . . . . . . . . . 2-274 Using the Valuation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-274 Posting Processes for Stores Inventory . . . . . . . . . . . . . . . . . . . . . . . . 2-275 Budget Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-282 Maintaining a Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-283 Budget Maintenance Form (FBABDMN) . . . . . . . . . . . . . . . . . . . . . . . . 2-283 Budget Development Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-287 Budget Development and Maintenance Time Line Example. . . . . . . . . . . . . 2-290 Establishing Initial Budget Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-291 Establishing Subsequent Fiscal Year Budget Phases . . . . . . . . . . . . . . . . 2-291 Rolling Phase to Phase Within Budget IDs . . . . . . . . . . . . . . . . . . . . . . 2-292 Changing Line Item Within a Phase . . . . . . . . . . . . . . . . . . . . . . . . . . 2-292 Mass Change Budgets Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-293
viii
November 2010
Merging Budgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-294 Rolling Approved Budget Phase to OPAL . . . . . . . . . . . . . . . . . . . . . . . 2-295 Deleting a Phase by Account Type and Fund Type . . . . . . . . . . . . . . . . . . 2-296 Fixed Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-297 Establishing Commodity and Accounting Structure . . . . . . . . . . . . . . . . . . 2-297 Integrating Fixed Assets With Procurement and Payable Processes . . . . . . . . 2-303 Attachments and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-308 Depreciation in the Fixed Assets Module . . . . . . . . . . . . . . . . . . . . . . . 2-309 Transfers in the Fixed Assets Module . . . . . . . . . . . . . . . . . . . . . . . . . 2-312 Adjustments in the Fixed Assets Module . . . . . . . . . . . . . . . . . . . . . . . . 2-312 Fixed Asset DTAG Processing Form (FFADTGP) . . . . . . . . . . . . . . . . . . 2-325 Querying Adjustment Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-327 Capitalizing Non-Invoice Fixed Asset Expense Accounting Entries . . . . . . . . . 2-327 Cost Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-329 Cost Accounting Billing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-329 Setting up Rates for Cost Accounting . . . . . . . . . . . . . . . . . . . . . . . . . 2-332 Defining Project/Work Orders and Entering Costs . . . . . . . . . . . . . . . . . . 2-337 Establishing Rate Codes for an Organization . . . . . . . . . . . . . . . . . . . . . 2-343 Establishing Cost Types for an Organization . . . . . . . . . . . . . . . . . . . . . 2-345 Entering Charges From Invoices With Internal Rate Codes . . . . . . . . . . . . . 2-347 Creating Direct and Indirect Labor Rate Codes . . . . . . . . . . . . . . . . . . . . 2-347 Automatic Rate Calculations for Inventory Process . . . . . . . . . . . . . . . . . . 2-348 Automatic Rate Calculations for Equipment Process . . . . . . . . . . . . . . . . . 2-349 Automatic Rate Calculations for Material Management Process . . . . . . . . . . 2-350 Archive/Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-352 Restore Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-352 Purge Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-353 Automated Clearing House . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-353 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-354 Processing Payments by Check Only . . . . . . . . . . . . . . . . . . . . . . . . . 2-354 Processing Payments by Direct Deposit Only . . . . . . . . . . . . . . . . . . . . . 2-355 Processing Payments by Check and Direct Deposit . . . . . . . . . . . . . . . . . 2-356
November 2010
ix
Chapter 3
Interfaces
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Banner Human Resources/Finance Interface Flow Summary . . . . . . . . . 3-2 HR/Finance Set up Rules Form (NTRFINI) . . . . . . . . . . . . . . . . . . . . . 3-3 Distribution Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Fringe Chargeback Rules Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Establishing and Feeding Original Budgets . . . . . . . . . . . . . . . . . . . . 3-6 Rule Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Application Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Budget Maintenance Checklist: Establishing and Feeding Original Budgets . . . 3-13 Budget Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 Rule Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 Application Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 Budget Maintenance Checklist: Budget Modeling. . . . . . . . . . . . . . . . . . . 3-28 Processing Wage/Salary Adjustments . . . . . . . . . . . . . . . . . . . . . . . 3-30 Rule Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 Application Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34 Budget Maintenance Checklist: Processing Wage/Salary Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 Approving Working Budgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38 Application Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39 Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43 Budget Maintenance Checklist: Approving a Working Budget . . . . . . . . . . . . 3-44 Feeding Payroll Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48 Rule Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
November 2010
Application Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52 Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53 Payroll Feed Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54 Processing COBRA Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56 Rule Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56 Batch Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59 COBRA Feed Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60 Installments/Feed to Banner Finance . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Chapter 4
Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Job Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Special Print Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Accounts Payable Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 1099 Forms Print . . . . . . . . . . . . . . . . . . . . . (FAB1099) . . . . . . . 4-6 Batch Check Accounting Process . . . . . . . . . . . . (FABCHKA) . . . . . . . 4-9 Disbursement Check Report . . . . . . . . . . . . . . . (FABCHKD) . . . . . . 4-12 Check Print Process . . . . . . . . . . . . . . . . . . . (FABCHKP) . . . . . . . 4-15 Batch Disbursement Register Process . . . . . . . . . . (FABCHKR) . . . . . . 4-16 Batch Check Process . . . . . . . . . . . . . . . . . . (FABCHKS) . . . . . . . 4-18 Receiving Matching Process . . . . . . . . . . . . . . . (FABMATC) . . . . . . . 4-20 1099 File Build Process . . . . . . . . . . . . . . . . . (FAM1099) . . . . . . . 4-24 Purchase Card Transactions Process . . . . . . . . . . (FAPCARD) . . . . . . 4-27 Canadian Direct Deposit Tape Process . . . . . . . . . (FAPCDIR) . . . . . . . 4-30 Direct Deposit File Creation Process . . . . . . . . . . . (FAPDIRD) . . . . . . . 4-31 Invoice Feed Process . . . . . . . . . . . . . . . . . . (FAPINVT) . . . . . . . 4-37 Direct Deposit Transmittal Register Process . . . . . . . (FAPTREG) . . . . . . . 4-40 Bank Reconciliation - Activity Aging Report . . . . . . . (FARAAGE) . . . . . . 4-41 Bank Reconciliation Balance Report . . . . . . . . . . . (FARBBAL) . . . . . . . 4-42 Bank Reconciliation Report . . . . . . . . . . . . . . . (FARBREC) . . . . . . 4-43
November 2010
xi
Check Register Report . . . . . . . . . . . . . . . . . . (FARCHKR) . . . . . . 4-44 Cash Requirements Report . . . . . . . . . . . . . . . (FARCSHR) . . . . . . 4-47 Batch Direct Deposit Advice Print Process . . . . . . . . (FARDIRD) . . . . . . . 4-49 Invoice Aging Report . . . . . . . . . . . . . . . . . . . (FARIAGE) . . . . . . . 4-50 Invoice Activity Report . . . . . . . . . . . . . . . . . . (FARINVA) . . . . . . . 4-51 Invoice Selection Report . . . . . . . . . . . . . . . . . (FARINVS) . . . . . . . 4-53 Invoices Awaiting Receiver Report . . . . . . . . . . . . (FARIREC) . . . . . . . 4-55 Open Invoice Report . . . . . . . . . . . . . . . . . . . (FAROINV) . . . . . . . 4-57 Vendor Alphabetical Listing Report . . . . . . . . . . . (FARVALP) . . . . . . . 4-61 Vendor History Report . . . . . . . . . . . . . . . . . . (FARVHST) . . . . . . . 4-63 Vendor Numerical Listing Report . . . . . . . . . . . . . (FARVNUM) . . . . . . 4-65 1099 Reporting/Withholding Status Report . . . . . . . . (FARWHLD) . . . . . . 4-67 1099 Reporting/Withholding Audit Report . . . . . . . . (FARWHLY) . . . . . . 4-69 1099 Forms Test Patterns . . . . . . . . . . . . . . . . (FAT1099) . . . . . . . 4-71 Budget Development Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72 Budget Defaults SS Mass Update . . . . . . . . . . . . (FBPBDEF) . . . . . . . 4-73 Approved Distributed Budget Report . . . . . . . . . . . (FBRAPPD) . . . . . . 4-75 Approved Budget Report . . . . . . . . . . . . . . . . . (FBRAPPR) . . . . . . 4-79 Budget Build Process . . . . . . . . . . . . . . . . . . (FBRBDBB) . . . . . . 4-83 Distribution Process Summary . . . . . . . . . . . . . . (FBRBDDS) . . . . . . 4-84 Budget Roll to General Ledger . . . . . . . . . . . . . . (FBRBDRL) . . . . . . . 4-85 Finance Budget Feed Process . . . . . . . . . . . . . . (FBRFEED) . . . . . . . 4-86 Budget Mass Change Process . . . . . . . . . . . . . . (FBRMCHG) . . . . . . 4-88 Budget Worksheet Report . . . . . . . . . . . . . . . . (FBRWKSH) . . . . . . 4-89 Cost Accounting Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92 Cost Accounting Billing Process . . . . . . . . . . . . . (FCBBILL) . . . . . . . 4-93 Equipment Rental Rate Calculation Report . . . . . . . (FCBEQPT). . . . . . . 4-96 Inventory Handling Rate Calculation Report . . . . . . . (FCBINVT) . . . . . . . 4-99 Labor Rate Calculation Report . . . . . . . . . . . . . . (FCBLABR) . . . . . . . 4-101 Material Management Rate Calculation Report . . . . . (FCBMATL) . . . . . . . 4-102 Cost Accounting Billing Detail Report . . . . . . . . . . (FCRBDTR) . . . . . . 4-104 C/A Rate Schedule Report . . . . . . . . . . . . . . . . (FCRSCHD) . . . . . . 4-106 C/A Variance Analysis Report . . . . . . . . . . . . . . (FCRVARA) . . . . . . . 4-108 Fixed Assets Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109 Depreciation Process . . . . . . . . . . . . . . . . . . (FFPDEPR) . . . . . . . 4-110
xii
November 2010
Fixed Asset Origination Tag Extraction Process . . . . . (FFPOEXT) . . . . . . . 4-114 Fixed Asset/Asset Group Report . . . . . . . . . . . . . (FFRAGRP) . . . . . . 4-117 Fixed Asset DTAG Aging Report . . . . . . . . . . . . . (FFRDTGA) . . . . . . 4-121 Fixed Asset DTAG Transaction Report . . . . . . . . . . (FFRDTGT) . . . . . . . 4-123 Fixed Asset Master Record Report . . . . . . . . . . . . (FFRMAST) . . . . . . 4-127 Fixed Asset Procurement Report . . . . . . . . . . . . (FFRPROC) . . . . . . 4-131 Fixed Asset Property Report . . . . . . . . . . . . . . . (FFRPROP) . . . . . . 4-136 General Ledger Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-141 Data Extract Process . . . . . . . . . . . . . . . . . . . (FGPGEXT) . . . . . . 4-142 Account Index Report . . . . . . . . . . . . . . . . . . (FGRACCI) . . . . . . . 4-144 Posting Process . . . . . . . . . . . . . . . . . . . . . (FGRACTG) . . . . . . 4-145 Account Hierarchy Report . . . . . . . . . . . . . . . . (FGRACTH) . . . . . . 4-147 Activity Codes Report . . . . . . . . . . . . . . . . . . (FGRACTV) . . . . . . 4-149 Available Balance Rebuild Process . . . . . . . . . . . (FGRBAVL) . . . . . . . 4-151 Cash Receipts Report . . . . . . . . . . . . . . . . . . (FGRCSRP) . . . . . . 4-153 Grant Rebuild Process . . . . . . . . . . . . . . . . . . (FGRGRBD) . . . . . . 4-155 End-of-Year Budget Carry Forward Report . . . . . . . (FGRBDRL) . . . . . . 4-158 Budget Status (Current Period) Report . . . . . . . . . . (FGRBDSC) . . . . . . 4-159 Balance Sheet Report . . . . . . . . . . . . . . . . . . (FGRBLSH) . . . . . . 4-162 Bank Cash Interfund Account Balance Exception Report (FGRBIEX) . . . . . . . 4-164 Bank Interfund Account Control Report . . . . . . . . . (FGRCASH) . . . . . . 4-167 Comprehensive Annual Financial Reports - Overview . . . . . . . . . . . . . . . . 4-169 Combined Balance Sheet - All Fund Types and Account Groups . . . . . . . . . . . . . . . . . . . . . . . . . (FGRCOBS) . . . . . . 4-171 Combined Statement of Revenues, Expenditures, and Changes in Fund Balances . . . . . . . . . . . . . . . (FGRCREF) . . . . . . 4-175 Combined Statement of Revenues, Expenditures, and Changes in Fund Balance Budget and Actual . . . . . (FGRCSBA) . . . . . . 4-179 Combined Statement of Revenues, Expenses, and Changes in Retained Earnings/Fund Balances . . . . (FGRCSRE) . . . . . . 4-182 Combining Balance Sheets Report . . . . . . . . . . . . (FGRCBSR) . . . . . . 4-184 Comparative Balance Sheets Report . . . . . . . . . . (FGRCGBS) . . . . . . 4-186 Combining Statement of Revenues, Expenditures and Changes in Fund Balance . . . . . . . . . . . . . . . (FGRCSSR) . . . . . . 4-188 Comparative Statements of Revenues, Expenditures and Changes in Fund Balances . . . . . . . . . . . . . . . (FGRCSCF) . . . . . . 4-190 Comparative Statements of Revenues, Expenditures, and Changes in Fund Balances - Budget and Actual . (FGRCGBA) . . . . . . 4-192
November 2010
xiii
Statement of Changes in Fund Balance Report . . . . . (FGRCHFB) . . . . . . 4-194 Statement of Changes in Net Assets Report . . . . . . . (FGRCHNA) . . . . . . 4-197 Close Operating Accounts Report . . . . . . . . . . . . (FGRCLOP) . . . . . . 4-200 GL/Subsidiary Ledger Control Report . . . . . . . . . . (FGRCTRL) . . . . . . 4-203 Changes in Unrestricted Net Assets Report Statement of Revenues, Expenses, and Other Changes . . . . . (FGRCUNA) . . . . . . 4-207 End-of-Year Encumbrance Carry Forward Report . . . . (FGRENRL) . . . . . . 4-211 Fund/Account Activity Report . . . . . . . . . . . . . . (FGRFAAC) . . . . . . 4-213 Fund Balance Account Report . . . . . . . . . . . . . . (FGRFBAL) . . . . . . . 4-215 Inception to Date Activity Report . . . . . . . . . . . . . (FGRFITD) . . . . . . . 4-216 Fund Hierarchy Report . . . . . . . . . . . . . . . . . . (FGRFNDH) . . . . . . 4-218 Statement of Financial Position Report . . . . . . . . . . (FGRFPSN) . . . . . . 4-220 Balance Forward Processing Report . . . . . . . . . . . (FGRGLRL) . . . . . . 4-222 G/L Transaction Activity Report . . . . . . . . . . . . . (FGRGLTA) . . . . . . . 4-225 Incomplete Document Report . . . . . . . . . . . . . . . (FGRIDOC) . . . . . . . 4-228 Journal Voucher Listing Report . . . . . . . . . . . . . (FGRJVLR) . . . . . . . 4-230 Roll Open Labor Encumbrances Process . . . . . . . . (FGRLENC) . . . . . . 4-234 Organization Detail Activity Report . . . . . . . . . . . . (FGRODTA) . . . . . . 4-244 Open Encumbrance Report . . . . . . . . . . . . . . . (FGROPNE) . . . . . . 4-247 Organization Hierarchy Report . . . . . . . . . . . . . . (FGRORGH) . . . . . . 4-252 Program Detail Activity Report . . . . . . . . . . . . . . (FGRPDTA). . . . . . . 4-254 Pro Rata Allocation Process . . . . . . . . . . . . . . . (FGRPRAP) . . . . . . 4-257 Pro Rata Allocation Report . . . . . . . . . . . . . . . . (FGRPRAR) . . . . . . 4-265 Program Hierarchy Report . . . . . . . . . . . . . . . . (FGRPRGH) . . . . . . 4-272 Statement of Revenues, Expenditures, Other Changes . (FGRREOB) . . . . . . 4-274 Statement of Revenues, Expenditures, Other Changes . (FGRREOC) . . . . . . 4-278 Statement of Taxes and Rebates Report . . . . . . . . . (FGRTAXR) . . . . . . . 4-282 Trial Balance Report . . . . . . . . . . . . . . . . . . . (FGRTBAL) . . . . . . . 4-288 Trial Balance Exception Report . . . . . . . . . . . . . (FGRTBEX). . . . . . . 4-294 Due To/Due From Control Report . . . . . . . . . . . . (FGRTOFR) . . . . . . 4-296 Daily Transaction Control Report . . . . . . . . . . . . . (FGRTRNH) . . . . . . 4-298 Transaction Interface Process . . . . . . . . . . . . . . (FGRTRNI) . . . . . . . 4-301 Transaction Error Report . . . . . . . . . . . . . . . . . (FGRTRNR) . . . . . . 4-302 Approval Process . . . . . . . . . . . . . . . . . . . . (FORAPPL) . . . . . . . 4-303
Purchasing and Procurement Module . . . . . . . . . . . . . . . . . . . . . . . 4-304 Bid Form Print . . . . . . . . . . . . . . . . . . . . . . (FPABIDD) . . . . . . . 4-305
xiv
November 2010
Change Order Form Print Purchase Order Form Print
. . . . . . . . . . . . . . . . (FPACORD) . . . . . . 4-306 . . . . . . . . . . . . . . . (FPAPORD) . . . . . . 4-311
Requisition Form Print . . . . . . . . . . . . . . . . . . (FPARQST) . . . . . . . 4-313 PO Batch Close Process . . . . . . . . . . . . . . . . . (FPPPOBC) . . . . . . 4-314 Bid Evaluation Report . . . . . . . . . . . . . . . . . . (FPRBEVL) . . . . . . . 4-318 Delivery Log . . . . . . . . . . . . . . . . . . . . . . . (FPRDELV) . . . . . . . 4-320 Open Purchase Orders Report . . . . . . . . . . . . . . (FPROPNP) . . . . . . 4-321 Open Requisitions Report . . . . . . . . . . . . . . . . (FPROPNR) . . . . . . 4-326 Purchase Order Activity Report . . . . . . . . . . . . . (FPRPURA) . . . . . . 4-328 Receiving & Delivery Report . . . . . . . . . . . . . . . (FPRRCDL) . . . . . . 4-330 PO Receiving Status Report . . . . . . . . . . . . . . . (FPRRCST) . . . . . . 4-332 Vendor Products Catalog Report . . . . . . . . . . . . . (FPRVCAT) . . . . . . . 4-334 Vendor Volumes Report . . . . . . . . . . . . . . . . . (FPRVVOL) . . . . . . . 4-336 Stores Inventory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-338 Stores Daily Transaction Listing Report . . . . . . . . . (FSRDTLG) . . . . . . . 4-339 Inventory Listing Report . . . . . . . . . . . . . . . . . (FSRINVL) . . . . . . . 4-342 Issue Ticket Report . . . . . . . . . . . . . . . . . . . . (FSRISST) . . . . . . . 4-345 Stores Low Stock Report . . . . . . . . . . . . . . . . . (FSRLWSR) . . . . . . 4-348 Open Stores Requisitions Report . . . . . . . . . . . . (FSROPNR) . . . . . . 4-350 Stores Outstanding Purchases Report . . . . . . . . . . (FSROUTP) . . . . . . 4-352 Physical Inventory Process Report . . . . . . . . . . . . (FSRPHYR) . . . . . . 4-354 Pick List Report . . . . . . . . . . . . . . . . . . . . . (FSRPICK) . . . . . . . 4-356 Physical Inventory Discrepancy Report . . . . . . . . . (FSRPIDR) . . . . . . . 4-359 Physical Inventory Worksheet . . . . . . . . . . . . . . (FSRPIWS) . . . . . . . 4-362 Put List Report . . . . . . . . . . . . . . . . . . . . . . (FSRPUTL) . . . . . . . 4-364 Dock to Stock Exceptions Report . . . . . . . . . . . . (FSRSTEX) . . . . . . . 4-367 Supply Catalog Report . . . . . . . . . . . . . . . . . . (FSRSUPC) . . . . . . 4-369 Research Accounting Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-371 Grant Rebuild Process . . . . . . . . . . . . . . . . . . (FGRGRBD) . . . . . . 4-372 Grant Budget Interface Process . . . . . . . . . . . . . (FRPBINF) . . . . . . . 4-373 Grant Interface Process . . . . . . . . . . . . . . . . . (FRPGINF) . . . . . . . 4-375 Research Accounting Billing Process . . . . . . . . . . (FRRBILL) . . . . . . . 4-377 Research Accounting Billing Reversal Process . . . . . (FRRBREV) . . . . . . 4-383 Deferred Grant Process . . . . . . . . . . . . . . . . . (FRRGRNT) . . . . . . 4-385 Deferred Grant Purge Process . . . . . . . . . . . . . . (FRRGRNP) . . . . . . 4-389
November 2010
xv
Research Accounting Report Process . . . . . . . . . . (FRRGRPT) . . . . . . 4-390 Application of Payment Process . . . . . . . . . . . . . (TRRAPPL) . . . . . . . 4-393 Unapplication of Payments Process . . . . . . . . . . . (TRRUNAP) . . . . . . 4-394 Grant Ledger Exception Report . . . . . . . . . . . . . (FGRGLEX) . . . . . . 4-396 Standard 1034 Billing Form . . . . . . . . . . . . . . . (FRR134B) . . . . . . . 4-398 Standard 269 Report Form . . . . . . . . . . . . . . . . (FRR269R) . . . . . . . 4-402 Standard 270 Billing Form . . . . . . . . . . . . . . . . (FRR270B) . . . . . . . 4-406 Standard 272 Billing Form . . . . . . . . . . . . . . . . (FRR272B) . . . . . . . 4-410 Standard 272 Report Form . . . . . . . . . . . . . . . . (FRR272R) . . . . . . . 4-414 Agency Budget Report . . . . . . . . . . . . . . . . . . (FRRABUD) . . . . . . 4-418 Billing Detail Exception Report . . . . . . . . . . . . . . (FRRBDEX) . . . . . . 4-420 Billing Exception Report . . . . . . . . . . . . . . . . . (FRRBEXC) . . . . . . 4-422 Grant Budget Report . . . . . . . . . . . . . . . . . . . (FRRBUDG) . . . . . . 4-425 Canadian Standard Report Form . . . . . . . . . . . . . (FRRCNSF) . . . . . . 4-427 Research Accounting Conversion Report . . . . . . . . (FRRCONV) . . . . . . 4-430 Grant Events Report . . . . . . . . . . . . . . . . . . . (FRREVNG) . . . . . . 4-432 Proposal Events Report . . . . . . . . . . . . . . . . . (FRREVNP) . . . . . . 4-436 Fund Exception Report . . . . . . . . . . . . . . . . . . (FRRFEXC) . . . . . . 4-440 Federal Financial Report . . . . . . . . . . . . . . . . (FRRFFRR) . . . . . . 4-442 Grant Budget Status Report . . . . . . . . . . . . . . . (FRRGBFY) . . . . . . 4-452 Generic Bill Form . . . . . . . . . . . . . . . . . . . . . (FRRGENB) . . . . . . 4-455 Generic Report Form . . . . . . . . . . . . . . . . . . . (FRRGENR) . . . . . . 4-459 Grant Inception to Date Report . . . . . . . . . . . . . . (FRRGITD) . . . . . . . 4-463 Grant Expenditures Report . . . . . . . . . . . . . . . . (FRRINDC) . . . . . . . 4-466 Grant Billing Preview Report . . . . . . . . . . . . . . . (FRRINVS) . . . . . . . 4-469 Grant/Budget Error Printing . . . . . . . . . . . . . . . (FRRTRNR) . . . . . . 4-471 Grants Aging Analysis Report . . . . . . . . . . . . . . (TRRAGES) . . . . . . 4-472 Collections Report . . . . . . . . . . . . . . . . . . . . (TRRCOLL) . . . . . . . 4-475 Grant Reconciliation Report . . . . . . . . . . . . . . . (TRRRCON) . . . . . . 4-479 Unapplied Payments Listing . . . . . . . . . . . . . . . (TRRUNPL) . . . . . . 4-483 Utilities Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-485 Finance Upload to GURFEED Process . . . . . . . . . (FUPLOAD) . . . . . . 4-486 Student Refund Interface Process . . . . . . . . . . . . (FURAPAY) . . . . . . . 4-493 Finance Feed Sweep Process . . . . . . . . . . . . . . (FURFEED) . . . . . . 4-494 Position Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-495
xvi
November 2010
Budget Roll Process Report . . . . . . . . . . . . . . . (NBPBROL) . . . . . . 4-496 Budget Maintenance Process . . . . . . . . . . . . . . (NBPBUDM) . . . . . . 4-499 Mass Salary Table Update Report . . . . . . . . . . . . (NBPMASS) . . . . . . 4-504 Budget Worksheet Report . . . . . . . . . . . . . . . . (NBRBWRK) . . . . . . 4-515 Position Class Listing Report . . . . . . . . . . . . . . . (NBRPCLS) . . . . . . 4-520 Position Class Incumbent Report Position Status Exception Report . . . . . . . . . . . . (NBRPINC) . . . . . . . 4-522 . . . . . . . . . . . . (NBRPSTA) . . . . . . . 4-527 Position Report . . . . . . . . . . . . . . . . . . . . . . (NBRPOSN) . . . . . . 4-524 Budget Data Finance Extract . . . . . . . . . . . . . . . (NHPFIN1) . . . . . . . 4-530 Finance Interface Report . . . . . . . . . . . . . . . . . (NHPFIN2) . . . . . . . 4-532 Budget Distribution Report . . . . . . . . . . . . . . . . (NHRBDST) . . . . . . 4-537 Organization Payroll Distribution . . . . . . . . . . . . . (NHRDIST) . . . . . . . 4-557 Effort Certification Report . . . . . . . . . . . . . . . . (NHRECRT) . . . . . . 4-578 . . . . . . (NHRSDST) . . . . . . 4-604 Employee Distributions Report . . . . . . . . . . . . . . (NHREDST) . . . . . . 4-595 Employee Payroll Summary by Organization
Archive/Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-627 Archive/Purge Process . . . . . . . . . . . . . . . . . . (FOPARCP) . . . . . . 4-628 Restore Process . . . . . . . . . . . . . . . . . . . . . (FOPARCR) . . . . . . 4-636 GASB Report Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-643 Statement of Net Assets - Workbook . . . . . . . . . . . . . . . . . . . . . . . . . . 4-644 Statement of Net Assets - Expanded Workbook . . . . . . . . . . . . . . . . . . . 4-645 Statement of Net Assets - Camera-ready Report . . . . . . . . . . . . . . . . . . . 4-646 Statement of Revenue, Expenses, and Changes in Net Assets . . . . . . . . . . . 4-647 Attributes for Statement of Net Assets . . . . . . . . . . . . . . . . . . . . . . . . . 4-649 Government Wide Statement of Net Assets . . . . . . . . . . . . . . . . . . . . . . 4-650 Government Wide Statement of Activities . . . . . . . . . . . . . . . . . . . . . . . 4-651 Governmental Funds Balance Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . 4-652 Governmental Funds Statement of Revenues Expenditures and Changes in Fund Balances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-653 GASB Extract Process Attribute Errors reports . . . . . . . . . . . . . . . . . . . . 4-654
Glossary Index
November 2010
xvii
xviii
November 2010
System Overview
As a processor of financial information at your installation, you are certain to have diverse needs that vary widely. To understand the term financial information, you need to do more than maintain your books and financial statements. Although these activities remain critical to the financial condition and stability of your installation, the demand for strategic and operational financial information by executive management, budget analysts, and departmental endusers is equally important. The Banner Finance System is a system that has both the functionality and flexibility to serve multiple users through a common database of financial information. Banner Finance not only responds to accounting requirements, but also addresses your need for strategic and operational information. Banner and Oracle give you the advantage of an easy-to-use query language and report writer and also provide direct access to strategic decision-support information. You can easily accomplish Financial Manager ad hoc reporting requirements with the Oracle SQL*Plus Utility and through the optional FOCUS Express for the Banner product. Overall, the Banner Finance system provides a comprehensive, integrated financial management system that enables you to track, maintain, and process all of your relevant financial data.
November 2010
Banner Finance 8.5 User Guide System Overview
1-1
Banner Finance System Flow Diagram
Purchasing and Procurement

Requisitions 4
Blanket Orders and POs POs (Capital Accounts) 2 Invoices (Capital Accounts)
Accounts Payable
Fixed Assets
Requisitions
5 Invoices, Checks, and Direct Deposits Charges and Payments
Customers and Refunds
Stores Inventory
Requisitions and Valuation
Depreciation 6
Accounts Receivable
General Accounting
Salary Encumbrances
Banner AR Position Budgeting and Control
10
Endowment Management
Project Charges and Encumbrances
Original and Adjusted Budget
Salary and Adjustments
Banner HR
9 8
Cost Accounting
11
Budget Development
Research Accounting
Major Features of Banner Finance

The Banner Finance System is an online product which utilizes the Oracle Relational Database Management System (RDBMS). The Banner Finance System can function as a stand-alone system or integrate with the Banner Human Resources System, the Banner
1-2
November 2010
Financial Aid System, and the Banner Advancement System. This capability enables you to access information that already exists on any of the other systems. The Banner Finance System is a complete financial information and management system. It delivers the strategic financial data that executives and business officers need in order to make the right fiscal decisions. It meets GAAP requirements and addresses the latest FASB and GASB positions on depreciation accounting and financial reporting. The system distributes purchasing functions to the Purchasing Department and accounts payable and check processing functions to the Accounts Payable Department. Each module is designed for the department it is to serve. SunGard Higher Education delivers full batch and online reporting into your hands. The Banner Finance system includes the following major features: Comprehensive Reporting You can access numerous standard hard copy reports and online inquiry forms. Menu and Help Forms Menu and help forms are available to assist you with online documentation, and menus are available to assist infrequent users. Frequent users can navigate throughout the system in Direct Access which allows you to navigate to any form you choose simply by typing in the form name. Online Data Entry When you enter data in a field, the system checks it for accuracy (that is, the system subjects the data to the appropriate validation test) before the cursor continues to the next field for update. If the system finds an error, an appropriate error message displays and no database update occurs. After you correct the error, the cursor moves to the next field. Validation Forms Validation forms exist to standardize the contents of certain fields and control data input. This feature gives your installation the flexibility to enter values that meet your specific requirements. You do not need to make any coding changes. Maintenance Forms Maintenance forms allow you to enter data with ease and assurance. Use these forms to maintain entity data and related information for specific purposes. Complete Audit Trail The system provides for tracking data from point of entry through archiving. Processing Rules You can format the processing rules for your system. This feature requires some coding. User-defined Security The online security system ensures that only authorized users can view and/or update certain (user-specified) data. The security feature accommodates both centralized and decentralized operations.
November 2010
1-3
Module Descriptions
The Banner Finance System meets the complete system requirements of your installation with the following integrated modules. For Process Flows for select modules, refer to Process Flows on page 1-8. General Ledger Finance Operations Stores Inventory Purchasing and Procurement Accounts Payable Budget and Position Control Fixed Assets Cost Accounting Endowment Management Accounts Receivable Research Accounting
General Ledger
The General Ledger is the core module of the Banner Finance System. It is fully integrated with each of the other subsystems that comprise the Banner Finance System, and maintains both general and subsidiary ledgers to support comprehensive query and reporting capabilities. General Ledger encompasses fund accounting, chart of accounts, system table maintenance and update, and grants and contract accounting.
Finance Operations
The Finance Operations module contains a series of forms that help you to manage your Banner Finance System. The functions in this module enable you to specify select global parameters, as well as Access/Approval/Security definitions.
Stores Inventory
The forms in the Stores Inventory module enable you to manage consumable inventory warehouses. Use this module to maintain one stockroom that issues simple office supplies to departmental users or to maintain multiple warehouse facilities which supply the installation as well as external customers.
1-4
November 2010

The Purchasing and Procurement module recognizes that purchasing agents face both ondemand and long term buying decisions. The subsystem provides timely and meaningful information to facilitate both decisions. This module also assists in the control of requests and the receipt of goods. The module consists of the following processes: Requests for goods and services Ordering/buying Receiving Bids/contracts
Accounts Payable
Using the Accounts Payable module, you can significantly contribute to the financial wellbeing of your installation. The timely payment of vendor invoices enables you to accurately monitor cash-flow, increase investment earnings, and establish good relationships with vendors. The Accounts Payable subsystem is designed to help you achieve each of these goals.
Budget and Position Control

The Budget and Position Control module facilitates the budget preparation process through integration of human resources information with accounting data. This module includes the following features: Position authorization and monitoring Enables you to budget by position, create single and pooled positions, control hiring by established, authorized, and funded positions, budget support of unlimited concurrent jobs/assignments, and highlight vacant, canceled, and over-budgeted positions. Position budgeting and expenditure control Enables you to budget by dollar, define full-time position equivalency, budget positions with start and end dates, validate labor distribution against chart of accounts, interface optional monthly/pay period of labor dollars, and budget fringe benefits. Personnel services budgeting Enables you to budget interactive and batch posting of position dollars, budget active and working year definitions, generate multiple methods of an initial budget for the following year, and budget preparation worksheets. Position History Presents online position history for multiple fiscal years, incumbent history, incumbent name, ID, status, and begin and end dates. Reporting Enables you to produce reports for staffing of budget summary, roster of approved positions, staff appointments, position status exceptions, and position control budget.
November 2010
1-5
Fixed Assets
The Fixed Assets module enables you to establish and maintain a record of your fixed and moveable assets. This module is closely integrated with the Payable and Procurement processes to allow you to create intermediate Origination Tag records automatically. The Procurement interface also includes an automatic capitalization feature that works in conjunction with the system-wide Minimum Asset Value. Another feature of the Fixed Assets module enables you to assign your own property tag by converting an Origination Tag record into a Permanent Tag record. An optional feature of this module allows you to create and maintain depreciation records; you can select from a variety of generally accepted depreciation methods and choose one of several first-year options. Individual financial adjustments can be made to Permanent Tag or Depreciation records; these adjustments originate in the Fixed Assets module and are synchronized between the Fixed Asset Subsidiary Ledger and the General Ledger. This module also includes transfer, history, and reporting capabilities to maintain an accurate inventory of the custody and location of your fixed and moveable assets.
Cost Accounting
The Cost Accounting module enables you to track, identify, and assign costs that the General Ledger, Purchasing, and Accounts Payable modules generate. This function is useful for responsible accounting purposes as well as for maintaining an internal customer service function. The maintenance/facilities staff can also use the Cost Accounting module to track various jobs and projects.
The Endowment Management module (EMS) in Banner Finance enables you to create and maintain unitized pools of endowment or similar funds. These funds consist of monetary gifts received by an institution and/or internal transfers of resources within an institution. On a periodic basis, you can convert gifts and internal transfers into units, or shares, in a pool. You can also link endowment funds to spendable income funds and record donor-imposed restrictions on spendable income. Then, on a periodic basis, you can distribute the following. Spendable income Realized gains and losses (trading activity) Unrealized gains and losses (market fluctuations) Spending formula variance (the difference between total income earned by a unitized pool and distributed spendable income)
1-6
November 2010
For detailed information about Endowment Management, refer to the Banner Endowment Management Handbook.
Accounts Receivable
For detailed information about Accounts Receivable, refer to the Banner Accounts Receivable User Guide.
Research Accounting
The Research Accounting module includes the maintenance and validation forms which enable you to create values used in cost sharing and indirect cost calculations. These forms also permit you to enter sponsor account codes to cross reference to institution accounts for budget display purposes. The Research Accounting module also includes a Proposals component which is primarily used by researchers and research administrators as a maintenance and tracking tool. Users can enter specific information such as key personnel, agency contact and address, budgets, and indirect cost and cost sharing elements. Research Accounting Proposals is designed to interrelate with the Grants module so that valuable information may be brought forward to a grant if the proposal is awarded.
Procedures
This manual contains a Processing chapter (Chapter 2) detailing the steps you must take to run the valid processes in each of the modules.
Forms
Detailed forms information is provided in online help.
November 2010
1-7
Process Flows
General Ledger
Journal Document
Encumbrance Document
No
Standard/ User Edits
No
Unapproved Documents
Yes No Yes
Fund Availability Check

No
Completed/ Approved Document

Yes
Overrride Fund Availability
Yes
Encumbrance Ledger
Update
General/ Operating Ledger
Update
Post Document
Update
Transaction History Files
1-8
November 2010
Stores Inventory
Commodity Master Create Inventory Master Stock Locations Dock to Stock Exceptions Detail
Procurement Requisition for Stock Approved
Purchase Order for Stock Approved
Receipt of Stock into Dock for Warehouse Locs
Is Stock Invoiced Yet?
No
Value Stock Cost with PO Cost
Decrease Stock Not Invoiced Qty
No
Is Inv cost different from PO?
Invoice Stock Purchase Order and Approve
Create Transfer Document
Yes
Revalue Stock Cost with difference
Yes
Post documents
Value Stock Cost with INV Cost
Update Stock not Invoiced Qty
Create Stores Request Document & Approve
Pick List Detail
Encumbrance Ledger
Update Stock Reserved Quantity
Issue Ticket Detail
Transaction History Ledger
General Ledger
Operating Account Ledger
Create Adjustments to Quantity or Cost Document
Create Stores Issue Document
Create Low Stock Record
Yes
Is Stock below reorder?
November 2010
1-9

Purchase Request Assign Buyer
Agreements
Is this Purchase to be Bid?

No
Yes
Create Bids
Bid Header Information
Vendor Products
Assign Purchase Order
Assign Bidders
Rush Order
Create Purchase Information
Bid Entry
Change Purchase Order

Yes
Are there changes to make to the PO?
Bid Award
No
Receiving
Delivery
1-10
November 2010
Accounts Payable
Purchase Order Create Invoice Document Vendor
Receiving
Currency Conversion
No
Yes
Approval Process
Fund Availability Check
Unapproved documents
Yes
Are there other approvers?
No
Vendor History
General/ Operating Ledgers
Update Update
Post Document
Update
Post Checks
Transaction History files
Open Invoice Document
Encumbrance Ledger
1099 Ledger
Online/Batch Checks
Special Methods
November 2010
1-11
Budget and Position Control

Operating Budget Maintenance Budget Phase Records Apply Mass Changes
Load/Roll Budgets from Operating/Phases

No
Distribute Budgets
Create Budget Requests
No Yes
Phase Closed Roll Budgets to Operating Ledger Available Balance Ledger
Post Documents
Yes

Yes
No
Budget Maintenance Document
Complete Approve Document
No
Unapproved Documents
1-12
November 2010
Fixed Assets
Documents: Receiving
Invoices, JVs, Direct Cash Receipts, Stores Issues
Depreciation Method
Posting
(Transaction History Ledger, General Ledger, Operating Ledger)
Create Depreciation Data
Creation of Origination /Document Tags
Depreciation Process
Transfer Asset
Convert/ Maintain Asset Master
Posting
Adjustments to Asset Master
General Ledger
Operating Ledger
November 2010
1-13
Cost Accounting
Project Data Customers Labor Rates
Inventory Rates
Create Project Cost Data
Material Rates
Cost Types Standard Edits Equipment Rates
Batch Rate Development
Update Rates as above
Project Billing
Billing Detail
1-14
November 2010
Setup User Defined Endowment Data FNVSDAT Journal Voucher (FGAJVCD)/Gifts from Alumni Posting
Create Pool Code FNMPOOL
Create Endowment Fund Codes FNMENDW
Setup Market Value (FNMUCTR)
Gifts to be Unitized FNBUNTD table
Unitization FNPUNTZ
Temporary table FNTUNTZ
Report
Endowment Unitization History FNBUNTH table
Endowment Funds Units FNRUNIT table
Setup Spendable Income Rates FNMUCTR
Distribution Processes FNPSPND /FNPGAIN
Report
Distribution History FNBDSTH table
FGRTRNI & Posting
Operating Ledger FGBOPAL Reports
General Ledger FGBGENL
Principal Fund Activity Report FNRPRNC
Spendable Endowment Fund Summary Report FNRSPNC
Endowment Fund History Report FNRHIST
November 2010
1-15
Accounts Receivable
Person/Account Maintenance Calculate Credits
Charges
Update Account
Currency Conversion
Payments
Cashiering
Miscellaneous Transactions
Application of Payments
Accounting Feed
Produce Invoice/Bill
Aging Analysis
Billing Messages
1-16
November 2010
Research Accounting
FRAPROP
(O)
Event Info. FRVEVNT
Agency Info. FTMAGCY
(O)
Grant Info. FRAGRNT
(O)
Personnel Info. FOAIDEN
(O)
Basis Codes FTMBASI
(O)
Grant Budget Info. FRABUDG

(O)
(O)
CFDA FRVCFDA
Indirect Cost Codes FTMINDR FTMINDA FTMINDD Roll to Ledgers Cost Share Codes FTMCSTR FTMCSTA FTMCSTD
Proposal Tracking Elements FTMSDAT
Grant Budget Totals FRIBUDG
(R) = Required (O) = Optional
Sponsor Account Code Creation FRVSACT
Institution/Sponsor Account Maintenance FRVISAC
November 2010
1-17
1-18
November 2010
Processing
This chapter contains procedures and processing information for the Banner Finance System. Follow these procedures to run the Banner Finance System and to process your financial data. The procedures are divided into sections according to their respective module and/or component. For instance, the Entering Receipt of Goods procedure appears under the Receiving Processing heading. This chapter also contains Banner Finance feature overviews which summarize important conceptual information. Read these sections for a general understanding of the respective Banner Finance modules and the functions you can control within them.
Security
One of the initial procedural tasks you perform in Banner Finance should be to set up your security parameters for your system. This section offers an overview on the security capabilities that your system offers. The system provides security on three levels: Oracle Security provides database security features and auditing capabilities. Banner Security provides form, report, and process level security across Banner applications. Banner Finance System Security enables you to establish security by user IDs, rule groups and rule classes, forms and process for rule groups, fund and fund types, and organizations.
Oracle Security
There are three principal aspects of the Oracle security system: Password Security The database administrator (DBA) identifies each Oracle user to the system. The DBA also assigns an initial password to each user. Oracle provides further protection for user passwords by providing an optional non-display field for password entry during logon. This prevents unauthorized users from reading your password on the screen as you log on. Data Access Security Oracle's security facilities enable the DBA or data creator to define other users' access rights to the data.
November 2010
Banner Finance 8.5 User Guide Processing
2-1
Security Auditing The Oracle auditing facility monitors the use of tables and views. This facility also tracks a variety of other user activities. Refer to your Oracle manuals for more information about these functions.
Banner Security
When setting up security at your site, use the Security Maintenance Form (GSASECR).
User IDs and Processing Security

Before establishing security in the Banner Finance System, you need to establish security for your users in the Banner General System.
1. Navigate to the Security Maintenance Form (GSASECR). Use GSASECR to define
processing level security for User IDs.

2. To begin establishing security, enter the current user ID in the Key Information.
Select Next Block. You must specify every form, report, process, and executable job when you establish security for a user ID. Use the Include and Exclude fields in copy mode.
3. Forms, reports, processes, executable job identifiers, and type indicators display in
the Process Information. Change the Type indicator to Q (Query), M (Maintenance), or E (Execute) for forms. Change the Type indicator to E (Executable), F (Form), R (Report), or P (Process) for reports, processes, and executable jobs.
4. Change the Access indicator to Q (Query), M (Maintenance), or E (Execute) for
forms, reports, processes, or executable jobs. Click or select Save.
Copy to User Feature

Use GSASECR to copy process level security definitions from one user ID to another user ID.
1. Enter the user ID whose security definition you wish to copy in the Current User
field. Select Next Item.

2. Specify processes this user may access in the Include field. Copy mode enables you
to enter FG% to include all Banner Finance General Ledger module processes, executable jobs, and reports.
3. Populate the Type field to support the include data. Valid entries are A (All), E
(Executable), F (Form), R (Report), and P (Process).

4. Enter the user ID you wish to update in the Copy to User field.
2-2
November 2010
5. Specify processes this user ID should not access by populating the Exclude field.
Select Insert Record. Select Next Block.

6. Forms, reports, processes, executable job identifiers, and type indicators display in
the Process Information. Change the Type indicator to Q (Query), M (Maintenance), or E (Execute) for forms. Change the Type indicator to E (Executable), F (Form), R (Report), or P (Process) for reports, processes, and executable jobs.
7. Change the Access indicator to Q (Query), M (Maintenance), or E (Execute) for
forms, reports, processes, or executable jobs. Click or select Save.
Delete Processes
Use the Include and Exclude fields on GSASECR to delete processes from user IDs defined to the database. To do this, perform the following steps:
1. Enter the user ID in the Current User field. 2. Select Next Item. 3. Populate the Include field with those processes you wish to delete. 4. Populate the Exclude field with those processes you wish to keep. 5. Delete the record. 6. Select Save.
To delete single records, populate the Current User and Include fields and select Remove. Select Insert Record (copy mode) in the Copy to User feature. For additional information about GSASECR, refer to the Banner General Security Administration Handbook.
Banner Finance System Security

When setting up security at your site, use the following Banner Finance System Security forms: System Control Maintenance Form (FOASYSC) User Profile Maintenance Form (FOMPROF) Rule Group/Rule Class Security Maintenance Form (FOMRGRC) Rule Group Security Maintenance Form (FOMUSRG) Form/Process To Rule Group Maintenance Form (FOMPRRG)
November 2010
2-3
Fund/Fund Type Security Maintenance Form (FOMUSFN) Organization Security Maintenance Form (FOMUSOR) Populate the following required indicators according to site specifications.
1. Open the System Control Maintenance Form (FOASYSC). 2. Check the Rule Class Security indicator and the Fund and Organization Security
indicator on this form to invoke security at the Rule Class level and the Fund/Org level.
3. Select the check box labelled Self Service Budget Development to enable the
Self-Service Budget Development pages and the Fund/Organization security for these pages.
4. Select the Self Service Budget Development History check box to enable creation
of Budget Development History records that include deleted rows. For additional information, refer to the Banner Finance Self-Service User Guide. There is no check box to turn off self-service budget development fund/org security. To effectively disable it, you can elect to give all users master access in the Self Service Budget Access window on FOMPROF.
Fund/Organization Security
Once you have completed assigning User ID and processing level security, open the User Profile Maintenance Form (FOMPROF). FOMPROF enables you to establish fund/ organization security for user IDs.
1. Enter a valid User ID in the Key Information and select Next Block. The descriptive
user name displays. The ID you enter must already exist in the database. Select Next Block.
2. Enter the users primary chart of accounts for which security is being established in
the COA field. This is a required field.

3. Use the drop-down lists to populate the Master Fund and Master Organization
fields for this user ID. Establish the user ID as having no authority, query only authority, posting authority, or both posting and query authority for the Master Fund and Master Organization. If you populate the Master Fund and Master Orgn fields, you do not have to define Funds and Organizations on the Fund/Ftyp Security Maintenance Form (FOMUSFN) and the Organization Security Maintenance Form (FOMUSOR) since this user ID has access to every fund and organization. You do not have to populate the Master Fund and Master Orgn fields if you uncheck the Fund/Orgn Security Indicator on FOASYSC.
2-4
November 2010
4. Enter a Budget ID to associate this user ID with a budget. This field is optional but is
useful in establishing budget processing security.

5. Check the NSF Override check box to give the user ID the authority to override in
situations where funds are insufficient for a document or transaction. Uncheck the check box to withhold this authority.
6. To enable user access to Self-Service Budget Development, select the Self Service
Access check box. When Budget Development is selected, two other drop-down lists become active. Use the Budget Master Fund drop-down list to specify user access to funds and the Budget Master Organization drop-down list to establish user access to organizations. Choices include No Authority (default value), Query Authority, and Both-Query & Posting. The Invoice and Receiving fields on this form are optional for security purposes but are very useful for transaction processing. For additional information about this form, please refer to the online help.
Rule Group Security

Open the Rule Group/Rule Class Security Maintenance Form (FOMRGRC). Use this form to associate rule classes to rule groups.
1. Select Enter Query when this form displays. Enter the Rule Group code. You may
click the Rule Group button or select List to access a rule group list window. Execute the query. The descriptive name displays. Select Next Block.
2. Use the Rule Classes Information to enter rule classes associated with the rule group.
The rule classes must exist in the database before you enter them on this form. Use the Rules Maintenance Form (FTMRUCL) to enter rule classes into the system.
3. Click or select Save to add the rule class to the rule group.
New Rule Group Feature

1. Select FOMRGRC from the Financial System Security Menu (*FINSECR). 2. Enter a rule group in the Rule Group field. Select Next Item. 3. Enter the rule group from which you want to copy rule classes in the Copy From
Rule Group field.

4. Select Next Block copy the rule classes into the new rule group.
November 2010
2-5
5. Enter the descriptive name of the new rule group in the Description field and select
Next Block.
6. Associate the desired rule classes with the rule group being established. Click the
Rule Class button or select List to access a list of rule classes. Enter additional rule classes for this rule group if required. Select Save. To delete single records from FOMRGRC, populate the Rule Group field and select Next Block to display the rule classes. Go to the desired record and select Remove.
User ID / Rule Group Security

1. Open the Rule Group Security Maintenance Form (FOMUSRG). Enter the User ID
for which you are establishing rule group security. Select Next Block. The data that appears in the Security Information identifies rule groups associated with the current user ID. Use this information to associate rule groups to the user ID.
2. Enter the desired rule groups in the Rule Group field. Click the Rule Group button
or select List to access a rule group list window. From this window you may select the rule group code you wish to display on FOMUSRG. Rule groups must exist in the system before they are entered on this form. Select Save.
Note Use the Rule Group/Rule Class Security Maintenance Form (FOMRGRC) to associate rule classes with rule groups.
To delete single records from FOMUSRG, populate the User ID field and select Next Block to display the rule groups. Go to the desired record and select Remove Record. Click or select Save.
New User ID Feature

1. Enter the user ID from which you want to copy rule groups in the User ID field. A
button and List are available.

2. Select Next Item to go to the Copy User ID field. Enter the user ID to which you
want to copy the rule groups. Select Insert Record. Select Next Block. Rule groups associated with the current user display in the Security Information. The user ID you entered in the Copy User ID field now displays in the User ID field.
3. Add or delete rule groups according to site policy. Click or select Save.
2-6
November 2010
Form and Process Level Security

Use the Form/Process to Rule Group Maintenance Form (FOMPRRG) to establish a security link from forms, reports, and processes to rule groups.
1. Enter the form, report, process, or executable job name for which you are establishing
security in the Form/Process field. Select Next Block.

2. The rule groups display in the Security Information supporting form or process level
processing. Use the Security Information to associate rule groups with forms, reports, and processes. Rule groups must exist in the system before entry on this form. List is available from the Rule Group field if you want to select a rule group from a list window. Select Next Item to display the rule group title in the Title field. Click or select Save.
Warning The system disables you from posting transactions if you do not associate the required rule groups with forms and processes, so delete records with care.
Use the Rule Group/Rule Class Security Maintenance Form (FOMRGRC) to enter rule groups into the Banner Finance System.
3. To delete single records, populate the Form/Process field and select Next Block to
display the rule groups. Go to the desired record and select Remove Record. Click or select Save.
Form and Process Copy Feature

1. Enter the name of the form or process from which you want to copy rule groups in the
Form/Process field. Select Next Item.

2. Enter the form or process name to which you want to copy the rule groups in the New
Form/Process field. Click or select Copy to copy the rule groups into the new form or process.
3. Select Next Block to add more rule groups to the form or process. A button and List
are available in the Rule Group field. Add or delete rule groups according to site policy. Click or select Save.
November 2010
2-7
Fund and Fund Type Level Security

Use the Fund/Fund Type Security Maintenance Form (FOMUSFN) to establish a security link between funds and fund types accessible to user IDs.
1. Enter the User ID for which you are establishing fund and fund type security. Select
Next Block.
2. Enter the charts of accounts, fund types, and funds to which this user has access. A
button and List is available in the COA, Fund Type, and Fund fields. Do not populate fund and fund type to the same record. Use multiple records. If Self-Service Budget Development is enabled, enter the highest-level Fund Type or Fund code for this user and select the allowable level of access from the Self Service Budget Access drop-down list. Options include None (default value), Query (view), and Query&Posting.
Note For you to have query access in Budget Development Self-Service, you must have at least query access in Banner Finance fund/org security. 3. Use the drop-down list to populate the Access field. This field establishes the user ID
entered in the Key Information as having posting, query, or both posting and query access. Click or select Save.
Copy From Existing User Feature

1. Enter the User ID to which you want to copy fund and fund types. User IDs must
exist in the system before entry on this form. Enter user IDs on the User Profile Maintenance Form (FOMPROF).
2. Enter the established user ID from which you want to copy fund/fund type
designations in the Copy from User ID field

3. Use the Include fields (Include COA Code, Include Fund Type, and Include
Fund) to designate funds and fund types that you want the system to copy to the new user. Use the Exclude fields (Exclude COA Code, Exclude Fund Type, and Exclude Fund) to designate funds and fund types that you do not want the system to copy to the new user. You may use wildcard characters along with partial values to include or exclude data when you execute the copy function for a user ID. For example, enter 1% in the Include Fund Type field to copy all fund types that begin with 1.
4. Select Insert Record to copy the charts of accounts, fund types, and funds into the
new user ID.
2-8
November 2010
5. The charts of accounts, fund types, funds, and fund titles associated with the user ID
appear in the Security Information. Select Next Block to add more charts of accounts, funds, and fund types to the user ID.
6. Use the drop-down list to populate the Access field. This field establishes the user ID
as having posting, query, or both posting and query access. Click or select Save.
Remove Record Functionality

You may select Remove Record from the Security Information. To remove records using the Include and Exclude fields, enter data in the following manner: Enter data in the Include fields that you wish to include in the delete function (delete these records). Enter data in the Exclude fields that you wish to exclude from the delete function (keep these records).
Organization Level Security

Use the Organization Security Maintenance Form (FOMUSOR) to establish a security link between organizations accessible to user IDs.
1. Enter the User ID for which you wish to establish organization security. Select Next
Block.
2. Enter the chart of accounts and organization codes to which this user has access. A
button and List are available from the COA and Organization fields. If Self-Service Budget Development is enabled, enter the highest-level organization code for this user and select the level of access from the Self Service Budget Access drop-down list. The access level you select here applies to all children (also referred to as successors) in the hierarchy of this organization. Options include: None (default value), Query; and Query&Posting. For you to have access in Budget Development Self-Service, you must have at least query access in Banner Finance fund/org security.
November 2010
2-9
New User Feature

Enter a user ID in the User ID field and another established user ID in the Copy from User ID field to which you want to copy organizations.
1. Enter the User ID to which you want to copy organization codes. User IDs must exist
in the system before entry on this form. Enter user IDs on the User Profile Maintenance Form (FOMPROF).
2. Enter the established user ID from which you want to copy organization codes in the
Copy from User ID field

3. Use the Include fields (Include COA Code and Include Organization) to designate
chart of accounts and organization codes that you want the system to copy to the new user. Use the Exclude fields (Exclude COA Code and Exclude Organization) to designate chart of accounts and organization codes that you do not want the system to copy to the new user. You may use wildcard characters along with partial values to include or exclude data when you execute the copy function for a user ID. For example, enter 1% in the Include Organization field to copy all organizations that begin with 1.
4. Select Insert Record to copy the charts of accounts and organizations into the new
user ID.
5. The charts of accounts, organizations, and organization titles associated with the user
ID appear in the Security Information. Select Next Block to add more organizations to the user ID.
Remove Record Functionality

You may select Remove Record from the Security Information. To remove records using the Include and Exclude fields, enter data in the following manner: Enter data in the Include fields that you wish to include in the delete function (delete these records). Enter data in the Exclude fields that you wish to exclude from the delete function (keep these records).
2-10
November 2010
General Ledger
Elements of the FOAPAL String
The FOAPAL is made up of the Fund (F), Organization (O), Account (A), Program (P), Activity (A), and Location (L) codes. The Fund, Organization, Account and Program codes are the primary chart of accounts elements used for classification, budgeting, recording, and/or reporting. The Activity and Location codes are used to provide more specific performance-related detail for transactions. These codes are not designed to accommodate budgeting purposes. A detailed description of each FOAPAL element follows: The Fund Code is the user-assigned alphabetic/numeric designation for a fiscal and accounting entity with a self-balancing set of accounts in which transactions are recorded and segregated to carry on specific activities or attain certain objectives in accordance with the prevailing regulations, restrictions, or limitations. Examples of Fund Codes are: 1001 - Current Unrestricted Fund, 4010 - Sponsored Student Loan Fund, 6101 - Fuller Architecture Program Endowment Fund, etc. The Organization Code is the user-assigned alphabetic/numeric designation for departmental/budgetary subdivisions within the larger entity, taken as a whole. Examples of Organization Codes are: 1101 - Dean of Behavioral Sciences, 2500 School of Engineering, 12105B - Business Office, etc. The Account Code is the user-assigned alphabetic/numeric designation for individual asset, liability, equity, revenue, expenditure and/or transfer account classifications. Examples of Account Codes are: 11001 - Demand Cash, 2101 - Accounts Payable, 3501 - Fund Balance, 51003 - Tuition, 6010 - Regular Full Time Salaries, etc. The Program Code is the user-assigned alphabetic/numeric designation for group activities, operations or other units directed to attaining specific purposes or objectives. Examples of Program Codes are 101 - Academic Support, 2700 - Student Services, 8100 - Research, etc. The Activity Code is the user-assigned alphabetic/numeric designation for temporary units of work, subsidiary functional classifications, or short duration projects. Examples of Activity Codes are: 3215 - Repair to Student Union Lobby Floor, A117 - Bookstore Van # 17, 5432 - Computer Lab Printer Ribbon Recycling, etc.
November 2010
2-11
The Location Code is the user-assigned alphabetic/numeric designation for physical places or sites. This is primarily used with, but not limited to, the Fixed Asset module. Examples of Location Codes are: 7651A - Controllers Office, 4100 - Athletic Department Offices, 1100 - Sciences Building, etc.
Recommended Order for Chart of Accounts Setup

This is the recommended order of forms for setting up a chart of accounts.
1. Chart of Accounts Maintenance Form (FTMCOAS) 2. System Control Fiscal Year Set-Up Form (FTMFSYR) 3. System Data Maintenance Form (FTMSDAT) 4. Account Type Code Maintenance Form (FTMATYP) 5. Account Code Maintenance Form (FTMACCT) 6. Currency Code Maintenance Form (GUACURR) 7. Installation Control Form (GUAINST) 8. Control Account Maintenance Form (FTMACTL) 9. Fund Type Maintenance Form (FTMFTYP) 10. Fund Code Maintenance Form (FTMFUND) 11. Identification Form (FOAIDEN) 12. Bank Code Rule Form (GXRBANK) 13. Program Code Maintenance Form (FTMPROG) 14. Activity Code Maintenance Form (FTMACTV) 15. Location Code Maintenance Form (FTMLOCN) 16. Organization Code Maintenance Form (FTMORGN) 17. Agency Code Maintenance Form (FTMAGCY) 18. Account Index Code Maintenance Form (FTMACCI) 19. Financial Manager Maintenance Form (FTMFMGR)
2-12
November 2010
Creating a Chart of Accounts Record

Establish a separate Chart of Accounts record for each installation requiring a set of financial reports. The following areas are important to understand when you are working with the Chart of Accounts Code Maintenance Form (FTMCOAS).
Main Window
Use a future Effective Date. Some accounts must be set up after you establish the Chart of Accounts record. Once you establish the accounts, enter them into the Chart of Accounts record. The Interfund Due To Account and the Interfund Due From Account can be the same account. When performing interfund accounting transactions, the system will look for these values on the Chart of Accounts record. Therefore, these accounts should be set up prior to the Effective Date (as defined in Step 1) and added to this record. The Require Sets of Attribute Types check boxes enable you to associate Attribute Sets rather than individual Attribute Values with a specific type of FOAPAL element (fund, organization, account, program, activity, or location) in this chart of accounts. For each FOAPAL type checked, the FOAPAL Attribute Association Form (FTMFATA) will link attribute sets to codes of that type. If unchecked, FTMFATA will link individual attribute values to codes of that type. The Budget Control Information manages available balance checking when performing accounting transactions. Non-sufficient funds checking can be performed on any combination of Fund, Organization, Account, or Program. Control Severity refers to the system response to an NSF condition. A severity of E (Error) will stop the transaction from progressing. When this condition occurs, an authorized user must either override the budget checking or establish sufficient budget. A severity of W (Warning) notifies the user of the NSF condition but allows the transaction. These values can be altered at the fund type or fund code level, thereby permitting different budget checking policies to be enforced at different levels.
November 2010
2-13
Parameters Window
You can alter these parameters at the fund type level. The Fund Balance Account is used for the closing entries. As with the interfund accounts, it must be established prior to the Chart Effective Date and added back in. The Accounts Payable Accrual Account is used if cash is disbursed in the accrual period against a prior period expense account. Cash in the current fiscal year will be credited and offset by a debit to current year A/P accrual. The prior year expenses will be debited and offset by a credit to prior year A/P accrual. As with Steps 2 and 4, this account must be established prior to the Chart Effective Date and added back in. The Accounts Payable Accrual Account is used for cash receipts against prior year revenue during the accrual period. Cash in the current fiscal year will be debited and offset by a credit to current year A/R accrual. The prior year revenue will be credited and offset by a debit to prior year A/R accrual. As with Steps 2, 4, and 5, this account must be established prior to the Chart Effective Date and added back in. The Close OP Ledger Code is J001. The Encumbrance parameters define the budget policy for those encumbrances which are rolled forward into the next fiscal year. The Encumbrance Parameters Rule Code is E090, Year End Encumbrance Roll. An entry of C (Committed) in the Commit Type field indicates that the encumbrance will be treated in a separate line having been rolled from the prior year. Its balance is reflected in the Prior Year Encumbrance Control account in the current year. An entry of U (Uncommitted) in the Commit Type field indicates that the encumbrance rolls into the current year with no distinction to indicate that it rolled from the prior year. The Encumbrance Control account in the current year reflects the balance. The Budget Roll field allows you to specify whether and how to roll the budget associated with the encumbrance. If the Commit Type is C, this value must be Y (Yes). That is, if the encumbrance is being distinguished as rolling from the prior year, it must come into the current year with its own budget. If the Commit Type is U, the Budget Roll parameter may equal Y (Yes) or N (No), depending on site policies. Budget Disposition specifies what happens to remaining budget if the site liquidates a rolled encumbrance in the current year for less than the encumbrance amount. If the Commit Type is U (Uncommitted), the Budget Disposition field must be U (Unrestricted). When an Uncommitted encumbrance rolls from the
2-14
November 2010
prior year and the site liquidates it for less than the encumbered amount, the remaining budget is available for use in the current year. If the Commit Type is C (Committed), the Budget Disposition can be U (Unrestricted), R (Restricted), or N (No Action). The U (Unrestricted) option works the same for a C (Committed) encumbrance as for an encumbrance that is U (Uncommitted). If the Budget Disposition is R (Restricted), any remaining amount after your site liquidates a C (Committed) encumbrance is not available for the current year's use. The system reclassifies the amount to an appropriate account. To take advantage of this option, establish a contingency account (typically a Fund Balance type), and enter it as a posting modifier on the INEI (Invoice with Encumbrance) rule class. If encumbrances are being rolled C (Committed), you may specify N (No Action) in the Budget Disposition field. As with R (Restricted), any remaining budget dollars will not be available for use in the current year, but the dollars will remain as restricted budget for the line item rather than reclassified to another account. The Percent field allows you to specify a portion of the budget to roll with the encumbrances. However, this percentage must be 100% when the encumbrances are being rolled C (Committed). The Budget Carry Forward Parameters refer to remaining balance or unspent budget dollars at the end of the fiscal year. The Budget Carry Forward Rule Code is J020 (Budget Carry Forward Journal). Budget Type refers to T (Temporary) or P (Permanent) budgets. Budget Class refers to O (Original) or A (Adjusted) budget. The Percent field is used to apply a percentage as with encumbrance budgets. Any budget which rolls will roll into the same line item in the new fiscal year. Use the Document Roll parameters to specify which types of encumbrances will roll at year end. The system allows you to roll the following types of encumbrances: Encumbrances, Purchase Orders, Memo Reservations, Requisitions, Labor Encumbrances, and Work Orders. To roll an encumbrance type, check the corresponding box.
Alternatives for Cash Accounts and Bank Funds

The Bank Fund is a special fund created to show the total cash for the installation and the breakdown of where that cash is deposited. By setting up different banks using the Bank Code Maintenance Form (GXRBANK), you can define the relationships of the cash and cash interfund accounts. This process permits individual cash balances by fund and enables you to see the entity's cash position in total.
November 2010
2-15
Determining the Cash Accounting Relationships

The cash and cash interfund accounts can be set up differently according to your installations needs. Using one cash account and multiple cash interfund accounts shows each fund's cash balance by bank, while the system carries the total cash balance for the installation to the cash account in the bank fund. Multiple cash accounts with one cash interfund account will show each fund's claim on the total cash pool as reflected in the cash interfund account in the bank fund. An advantage of this method is that it enables the installation to maintain additional banks in the bank fund that represent external cash transfers, such as transfers to the State treasurer. The system does not require you to reflect these transfers within any funds other than the bank fund.
Establishing the Cash Accounting Relationships

Steps 2 through 5 below are an integral part of building the Chart of Accounts.
1. Determine the following:
Cash account and cash interfund numbers Bank IDs (for example, FIRST for First National) Bank code numbers
2. Establish the cash and cash interfund accounts on the Account Code Maintenance
Form (FTMACCT).
3. (Optional) Establish Bank Fund type on the Fund Type Maintenance Form
(FTMFTYP). The Bank Fund can either have its own fund type or it can be a separate fund code within the current unrestricted fund type.
4. Establish the Bank Fund on the Fund Code Maintenance Form (FTMFUND). 5. Establish the banks on the Bank Code Maintenance Form (GXRBANK).
External Cash Receipts and Disbursements

You may set up a default bank for each fund record. For any given cash entry, you may override the default. The relationship of cash and cash interfund accounts as identified in the bank table allows the system to post cash to the cash or cash interfund accounts as appropriate within the input fund(s) and to the Bank Fund.
2-16
November 2010
Internal Cash Interfund Transfers

Transferring cash between funds will post offsets to the Due To/Due From account and transfer cash between the banks in the bank fund, if appropriate. If you are using the multiple cash accounts method, you can perform transfers within the bank fund to reflect transfers of bank balances.
Cash Accounts In Foreign Currency

Whenever you enter a foreign currency within the procurement processes, the system automatically calculates the converted amount for use in available balance checking and posting. Use a simple journal entry in the bank fund to record the purchase of the foreign currency itself. We recommend using the routine JE15 Rule Class. Enter a credit entry to the cash account in the bank fund used to purchase the foreign currency; debit the cash account used for maintaining the balance of the specific foreign currency (referenced on the Currency Code Maintenance Form, GUACURR); debit/credit the difference to the exchange account (also referenced on GUACURR).
Budget Entries Only to Pool Accounts

The system enables you to make budget entries only to account codes designated as pool accounts. This restricts non-budget entries to pool accounts. Banner Finance controls this restriction through a data entry indicator value entered on the Accounts Code Maintenance Form (FTMACCT). Use the drop-down list to populate the Data Entry indicator field on FTMACCT. If you select BUDGET from this drop-down list, the system allows only budget entries against this account. The system cannot post non-budget entries to pool accounts and treats these accounts as non-data enterable. The system determines a budget entry by the process codes that make up the rule class code. If a transaction rule class code contains any of the following process codes: O010, O011, O020, or O021, then the system recognizes the rule class as a budget entry, allowing the transaction against the account marked with the data entry indicator BUDGET. If the transaction rule class code does not contain one of these process codes, then the system treats the account as non-data enterable. An online edit-type message displays, and the system stops the cursor in the Account code field.
Tip This feature is applicable to all the transaction forms in Banner Finance as well as the Transaction Interface Process (FGRTRNI).
November 2010
2-17
Multiple Fund Balance Processing

The Multiple Fund Balance feature allows you to close Operating Account Year-to-Date detail and Fund Addition/Deduction detail to more than one fund balance account at Year End and during Concurrent Year Processing. This feature is optional. Check the Multiple Fund Balance box on the System Control Maintenance Form (FOASYSC) to initiate this process. The box defaults to unchecked. If the box is unchecked, the system uses the Fund Balance Account defined on the Chart of Accounts Maintenance Form (FTMCOAS) as the default fund balance account to which all operating account year-to-date control activity or Fund Addition/Deduction activity will close to at year end. This closing of Control Account information takes place in the General Ledger Roll Process (FGRGLRL), Concurrent Year Processing, and in the Close Operating Account Process (FGRCLOP). To implement this feature, you need to set a few indicators and identify the cross reference fund/account information to one or multiple fund balance accounts. Enter cross reference information on the Fund Balance Account Maintenance Form (FTMFBAL). Determine how best to use this feature based on site policies. You can opt to ignore the feature and post journal entries at year end to adjust values from the default fund balance account to the other fund balance accounts if relatively few of the fund balance accounts are affected at year end. You can choose to implement this feature if a large number of the fund balance accounts are affected; for example, investment fund activity could close to Retained Income, Realized Gains, Realized Losses, and Original Gifts accounts. Once you establish these values, your work is done, except for minor upkeep. Implement multiple fund balancing on the following forms:
System Control Maintenance Form (FOASYSC)

Check the Multiple Fund Balance box on FOASYSC to initiate multiple fund balance processing. Remember, if the check box is unchecked, the system uses single fund balance processing. The system closes all Operating Account activity (OPAL) to the fund balance account specified at the chart of accounts level.
Chart of Accounts Maintenance Form (FTMCOAS)

Make sure that a Fund Balance Account is defined in the Parameters Window of the Chart of Accounts Maintenance Form (FTMCOAS). The system uses this account for closing Encumbrance and Budget activity.
2-18
November 2010
Fund Code Maintenance Form (FTMFUND)

Use the drop-down list to populate the Multiple Fund Balance Indicator field on the Fund Code Maintenance Form (FTMFUND). This indicator allows the system to determine the criteria for selecting the correct Fund Balance Accounts. Valid options are Fund, Fund Type, and Account.
Fund Balance Account Maintenance Form (FTMFBAL)

Open the Fund Balance Account Maintenance Form (FTMFBAL) and specify the Fund Balance Account(s) to which year-to-date Operating Ledger and Fund Addition/ Deduction activity should close. Enter all funds for which you have populated the Multiple Fund Balance Indicator field on FTMFUND and specify the appropriate level for determining what Fund Balance Account to use and enter the Fund Balance Account. Specify Fund Balance Accounts by Fund Type (level I or II), Fund, or Fund and Account. For funds with the indicator set to Fund Type, the system looks for the fund type at level one or level two within FTMFBAL. The system then uses whatever fund balance account you defined for that type. If you previously defined both Fund Type levels on this form, the system selects level two over level one. For funds with the indicator set to Fund, the system searches for that fund code within FTMFBAL. The system then closes year-to-date activity for each operating account and each Fund Addition/Deduction account within that fund to the Fund Balance Account cross-referenced on FTMFBAL. For funds with the indicator set to Account, the system expects either of two situations: The fund and each OPAL or Fund Addition/Deduction account that has activity within that fund may be specified with a valid fund balance account. The balance of that account's YTD activity will close to the defined fund balance account. You may specify the fund and a null account with a valid fund balance account. This will handle situations in which the Multiple Fund Balance Indicator field is set to Account but you have not defined the OPAL or Fund Addition/Deduction account on FTMFBAL, handling any exceptions for ease of data entry.
Review of Fields
Set the Multiple Fund Balance indicator on the System Control Maintenance Form (FOASYSC) as appropriate for single or multiple Fund Balance Processing. Check the box to initiate the feature or uncheck it to bypass the feature. You must populate the Fund Balance Account field in the Parameters Window of the Chart of Accounts Maintenance Form (FTMCOAS) for closing encumbrance and budget control information.
November 2010
2-19
The purpose of the Multiple Fund Balance Indicator on the Fund Code Maintenance Form (FTMFUND) is to direct the system to the appropriate Fund Balance Accounts that will be affected during the Year End Processes and for Concurrent Year Processing.
Review of Forms and Reports

The Fund Balance Account Maintenance Form (FTMFBAL) enables you to enter and maintain Fund Balance Account information relating to Fund Type, Fund, or Fund Codes/Account Codes for a particular Chart of Accounts. The Fund Balance Account Report (FGRFBAL) provides a hard copy listing of information entered through the Fund Balance Account Maintenance Form. Execute FGRFBAL by the Chart of Accounts Code through a particular As of Date.
Troubleshooting Notes
The Balance Forward Processing Report (FGRGLRL) and the Close Operating Accounts Report (FGRCLOP) stop processing if you have not defined fund balance accounts on FTMFBAL for the indicator referenced on each Fund record. The system stops processing if it finds that the total of the Fund Balance accounts to which it is attempting to close do not equal the amounts in the Operating Ledger Control Accounts.
General Ledger Consolidated Postings

The term Consolidated Postings refers to the consolidation of the approved, tax, additional, and discount amounts entered on a Purchase Order, Change Order, or Invoice. This net amount is then posted to the transaction history and detail tables. The Consolidated Postings function eliminates the entry of each separate amount, thereby conserving space in the tables.
Example:
The following information is entered on the Invoice/Credit Memo Form (FAAINVE) as a direct pay invoice: Approved: Discount: Additional: Tax: Net: $1000 -$100 + $50 +$150 $1100
When posting processes this transaction and when the Consolidated Posting box is checked, the system writes an entry for $1,100 in the transaction history and detail tables with a rule class of INNI.
2-20
November 2010
If the same entry was posted and the Consolidated Posting box was not checked, the system would write an entry into the transaction detail table for each individual amount. You would see a rule of INNI with an amount of $1,000; a rule of DISI (Discount on Invoice) with an amount of $100; a rule of ADDI (Additional amount on Invoice) with an amount of $50, and a rule of TAXI (Tax on Invoice) with an amount of $150. You must determine if the system should process procurement and payables documents with Consolidated Posting turned on or off. To turn Consolidated Posting on, check the Consolidated Posting indicator, located on the System Control Maintenance Form (FOASYSC). You must weigh the advantages and disadvantages of using Consolidated Posting. You will most likely want to check the Consolidated Posting indicator for the following reasons: You need to save disk space. You do not want to view the break down of discount, additional, and tax amounts. You will most likely not want to check the Consolidated Posting indicator for the following reasons: You need to view the break down of discount, additional, and tax amounts. You want to have additional, discount, or tax amounts posted to a particular account, rather than posting to a particular account (s) on input. If you want to post to a specific account, an account code is placed on the rule classes as a posting modifier. Posting will only interrogate the posting modifiers on the rules if the Consolidated Posting indicator is not checked. Keep in mind that tax liability amounts and rebate amounts are posted individually regardless of whether or not the Consolidated Posting indicator is checked. In addition, direct cash receipts, entered on the Direct Cash Receipt Form (FGADCSR), do not interrogate the Consolidated Posting indicator, only Purchase/Change Orders and Invoices. Consolidated Postings are often confused with Summary Postings. Summary Postings allow you to combine the effect of a number of documents awaiting posting into single entries for accounts that you have defined in the System Control Maintenance table.
General Ledger Summary Postings

General Ledger Summary Postings provide the option of specifying General Ledger accounts for which the system stores transactions in summary fashion rather than individual items. For example, if there were ten invoices processed in a posting run, there would be a transaction record created and queryable on the General Ledger Transaction Detail Activity Form (FGIGLAC) for each accounting distribution on the invoices both to
November 2010
2-21
the Expenditure Control and the Accounts Payable accounts. The system stores all the detail on the Operating Ledger. For ease of analysis, view the summarized entries in the General Ledger using the query forms. Determine which General Ledger accounts you want to store in summary rather than detailed fashion. Typically these would be the cash interfund, Due To/From, Accounts Payable, Control, and similar non-data entry accounts.
Warning It is recommended that you do not use this feature for those General Ledger accounts to which the system may make direct entries (Data Entry Indicator on the Account Code Maintenance Form (FTMACCT) set to Y). Summary postings could create a potential reconciliation problem and jeopardize good internal controls.
Specify these General Ledger accounts to the System Data Validation Table (FTVSDAT) using the System Data Maintenance Form (FTMSDAT). The accounts selected must have an FTVSDAT table entry as follows:
1. In the Entity or Usage Code field on FTMSDAT, enter FGRACTG. 2. In the Attribute Code field, enter GENL_ACCT_CODE. 3. In the Optional Code Number 1 field, enter the Account Code for the account that
the system is summarizing. This account must be a valid General Ledger Account.
4. Enter the Chart of Accounts Code.
After you establish the System Data Validation Table Record, the Posting Process (FGRACTG) creates a new document type, SUM, for each posting run. When the system summarizes General Ledger postings, a document code in MMDDHHMI format is generated. All summarized postings in a given posting run have the same generated document code by fund. The system groups summarized postings by document type and debit/credit indicator. For example, if Encumbrance Control is one of the specified accounts for General Ledger summary, then the system summarizes all Purchase Order debit entries for the Encumbrance Control Account and posts to that account. The system creates a transaction history and detail record for the summarized General Ledger posting. The Item Num field stores the posting year in the format:
FGBTRND_ITEM_NUM FGBTRNH_ITEM_NUM
Transaction History Detail Table Transaction History Table
To review the summarized postings on the Document Retrieval Inquiry Form (FGIDOCR), enter the document number in MMDDHHMI format and enter the document type of SUM.
2-22
November 2010
The general accounting transaction query forms display all other postings for the original documents for accounts that are not summarized by the system. For example, if the Accounts Payable Control account uses summary posting, view the General Ledger Transaction Detail Activity Form (FGIGLAC) and the summarized document number created in the posting run displays the cumulative total dollars posted to the A/P account. On the Operating Accounts Transaction Detail Activity Form (FGITRND), you can view the individual invoice numbers for each accounting distribution.
Transaction Interface Process (FGRTRNI)

Use the Transaction Interface Process to post transactions to the financial ledgers in the following scenarios: You are using Deferred Edit Processing You are using Automatic Journal Vouchers You have an interface system from which you want to send accounting transactions to Banner Finance You are executing the Budget Roll to General Ledger Process (FBRBDRL) You are executing one of the following year-end processes: the End-of-Year Budget Carry Forward Process (FGRBDRL), the Close Operating Account Process (FGRCLOP), or the End-of-Year Encumbrance Carry Forward Process (FGRENRL).
Deferred Edit Processing

You may initiate Deferred Edit Processing to enhance system performance based on site policy. Deferred edit processing enables you to substitute the time it takes the system to edit a transaction in an entry with the time FGRTRNI takes to edit transactions. Set Deferred Edit Processing at the system level or for each document type. To control Deferred Edit Processing at the system level, check the Deferred Edit box on the System Control Maintenance Form (FOASYSC). To control Deferred Edit Processing for individual documents, you may check the Defer Edit box on individual forms such as the following: Encumbrance/Reservations Maintenance Form (FGAENCB) Journal Voucher Entry Form (FGAJVCD) Journal Voucher Quick Form (FGAJVCQ) Journal Voucher Mass Entry Form (FGAJVCM) Invoice/Credit Memo Form (FAAINVE)
November 2010
2-23
Purchase Order Form (FPAPURR) Requisition Form (FPAREQN) If your site uses Deferred Edit Processing, the system places a transaction record in the appropriate Banner Finance System tables for every completed document. The system forwards these transaction records to the Posting Process (FGRACTG) after you successfully execute FGRTRNI. The system compiles accounting errors, if there are any, in the Transaction Error Report (FGRTRNR) once FGRTRNI has completed. Correct the errors using the appropriate forms based on the output produced by FGRTRNR. Run the Posting Process (FGRACTG) to post transactions to the financial ledgers.
Automatic Journal Vouchers

You may process automatic journal vouchers by entering specific information such as the Journal Voucher ID, the submission cycle value, and the submission date on the Automatic Journal Voucher Form (FGAAUTO). Create specific accounting information and dollar amounts using the Journal Voucher Entry Form (FGAJVCD). Link accounting information to the Automatic Journal Voucher ID. Once you complete a journal voucher, run FGRTRNI. FGRTRNI analyzes the schedules of each automatic journal voucher to determine if its schedule date has been met. FGRTRNI edits FOAPAL components and rule classes. FGRTRNI updates the next submission date. The system assigns a unique submission number to each automatic journal voucher. The document number stays consistent. The system forwards documents that pass the FGRTRNI edits to the Approved Document Table (FOBAPPD) and then on to the Posting Process (FGRACTG). FGRTRNI creates submission 1-XXX from submission zero. The number of submissions completed and the number of submissions remaining are updated on FGAAUTO. The Next Submission Date(s), the Submissions Completed, and the Submissions Remaining are also updated, regardless of whether or not errors are found. The system lists documents failing the FGRTRNI edits on the Transaction Error Report (FGRTRNR). Correct the errors using the Journal Voucher Entry Form (FGAJVCD). View automatic journal vouchers using the List of Automatic Journals Form (FGIAUTO). FGRTRNR displays the document number and the submission number (#) of the submission in error. You must correct the errors on FGAJVCD, re-complete the document, and either run posting or FORAPPL based on whether the Approval Override Indicator is defined to be on or off for Journal Vouchers on FOASYSC.
2-24
November 2010
Interfaces
You can interface both Banner systems and non-Banner systems to the Banner Finance System. Use the System Data Maintenance Form (FTMSDAT) to identify the interface systems. When you enter FTMSDAT, the cursor resides in the Entity/Usage Code field. Enter FGRTRNI in this field. Select Next Item. Enter SYSTEM_ID in the Attribute Code field. Select Next Item to move to the Optional Code Number 1 field. Enter a system ID for the system you wish to interface. For example, the Banner Finance seed data contains the interface ID: PAYROLL. This ID identifies the Payroll Module Interface. The seed data contains definitions for all the Banner systems. Use FTMSDAT to define all the nonBanner systems installed at your site. Move to the Data field. This two-character field accepts the following values. The first character accepts D (Detail) or S (Summary). Use this character to identify whether the system sends the accounting transaction in detail or summarized format. Use the second character to identify whether the system R (Rejects) or S (Suspends) transactions if errors occur.
Budget Development Roll Process

Once you establish an approved budget within the Budget Development module, you may roll the budget to the finance ledgers using the Budget Roll to General Ledger Process (FBRBDRL). After you run FBRBDRL, run FGRTRNI to validate the budget entries. If the budget passes the FGRTRNI edits, the system passes the budget information to the Posting Process (FGRACTG). Posting updates the Banner Finance ledgers. The system lists documents that fail the FGRTRNI edits on the Transaction Error Report (FGRTRNR). Correct the errors using the Journal Voucher Entry Form (FGAJVCD) or using the Journal Voucher Quick Form (FGAJVCQ).
End-of-Year Process
Year-end processing consists of the following functions: General Ledger Balance Forward Process (FGRGLRL) End-of-Year Encumbrance Carry Forward Process (FGRENRL) End-of-Year Budget Carry Forward Process (FGRBDRL) Close Operating Account Process (FGRCLOP) (Optional) Roll HR Labor Encumbrances Process (FGRLENC) The FGRLENC process does not depend on the execution of the other year-end processes and does not need to be run if you are not using multiple year encumbering.
November 2010
2-25
The system requires you to run FGRTRNI to edit the FGRENRL, FGRBDRL, and FGRCLOP processes. FGRTRNI validates the FOAPAL components, rule classes, etc. Once FGRTRNI has successfully completed (no errors encountered), post transactions using the Posting Process (FGRACTG). The system lists transactions failing the FGRTRNI edits on the Transaction Error Report (FGRTRNR). Correct the errors using the Journal Voucher Entry Form (FGAJVCD) or using the Journal Voucher Quick Form (FGAJVCQ). Post completed documents (using FGRACTG) to update the Banner Finance ledgers.
Available Balance Process

Banner performs online available balance checking on every transaction that affects expense, labor, or transfer operating ledger accounts. This process does two things: Updates the Available Balance Table (FGBBAVL) with the activity for the transaction. Performs non-sufficient funds (NSF) checking and provides an appropriate message when applicable. The Available Balance Table (FGBBAVL) holds transaction amounts for budget FOAPALs. For each FOAP, the table holds the following amounts: Total adopted budget Total adjusted budget Total year to date activity Total encumbrances on the budget Total reservations on the budget
Available Balance = Total Adopted Budget + Total Adjusted Budget Total Year to Date Activity - Total Encumbrances - Total Reservations
The Budget Availability Status Form (FGIBAVL) shows the budget availability for a FOAP as of the current system date. The Rebuild Process (FGRBAVL) rebuilds the Available Balance Table (FGBBAVL) from the operating ledger and the Back Out Table (FGRBAKO). The Back Out Table holds documents that have updated the Available Balance Table, but have not been posted. Banner performs online available balance checking only if you select the NSF Checking indicator on the System Control Maintenance Form (FOASYSC) for a specific transaction document type.
2-26
November 2010
Note When you post a transaction, Banner always updates the Available Balance Table and displays a warning message if you have exceeded the budget.
Banner updates the Available Balance Table online under the following conditions: The NSF Checking indicator is selected for that document type. There are sufficient funds for the transaction, or the NSF Override Indicator is set to Y for that transaction, or the Available Balance Control Severity is set to Warning for the fund, fund type, or chart. No errors were discovered during available balance processing. In all other cases, Banner changes the NSF Suspense Indicator in the accounting record to Y and it does not update the Available Balance Table. Banner does not complete a transaction if the NSF Suspense Indicator = Y unless approvals are on. When approvals are on and an NSF condition has been found, Banner completes the transaction and sends it to the approvals process. If you override the NSF condition during approvals processing, Banner updates the Available Balance Table. When Banner performs online available balance checking, it updates the Available Balance Table (FGBBAVL) with the activity and inserts records in the Back Out Table (FGRBAKO). The records in the Back Out Table let the posting process know that the Available Balance Table has already been updated for that transaction. This enables the posting process to roll back the update, delete the records in the Back Out Table, perform available balance checking, and update the available balance again. After the document is successfully posted, Banner deletes all records related to that document from the Back Out Table.
Forms and C Processes That Perform Available Balance Checking

There are two database packages, FGKABAL.SQL and FGKBAVL.SQL, that hold all procedures and functions relevant to available balance processing. These procedures are called from the forms and C processes that perform available balance checking. The following forms perform online available balance processing. Invoice/Credit Memo Cancel Form (FAAINVD) Invoice/Credit Memo Form (FAAINVE) Budget Maintenance Form (FBABDMN)
November 2010
2-27
Direct Cash Receipt Form (FGADCSR) Encumbrance Maintenance Form (FGAENCB) Journal Voucher Entry Form (FGAJVCD) Journal Voucher Mass Entry Form (FGAJVCM) Journal Voucher Quick Form (FGAJVCQ) Change Order Cancel Form (FPACDEL) Change Order Form (FPACHAR) Purchase/Blanket Order Cancel Form (FPAPDEL) Purchase Order Form (FPAPURR) Requisition Cancel Form (FPARDEL) Requisition Form (FPAREQN) Stores Issue/Return Form (FSAISSU) Stores Requisition Form (FSAREQN) Project Charge Maintenance Form (FTMCHRG) The following forms perform available balance processing for specific documents when approvals are turned on. Direct Cash Receipt Approval Form (FOQDCSR) Encumbrance Approval Form (FOQENCB) Invoice/Credit Memo Approval Form (FOQINVA) Journal Voucher Approval Form (FOQJVCD) Purchase Order Approval Form (FOQPACT) Requisition Approval Form (FOQRACT) The following C processes perform available balance processing. Posting Process (FGRACTG.PC) Transaction Interface Process (FGRTRNI.PC)
Available Balance Controls

Banner builds records in the Available Balance Table (FGBBAVL) based on the control methods specified in the Chart of Accounts, Fund Type and Fund Code tables. The controls and parameters for checking budget availability are:
2-28
November 2010
Any combination of budgets of Fund, Organization, Account and Program called FOAP key control. Budgets can be controlled on an Annual (A), Quarterly (Q) or Year-to-Date (Y) control period. The severity of the message when not sufficient budget is available for the transaction can be Error (E) or Warning (W). Budgets can also be controlled at an organization or fund or combination higher in the hierarchical structure. (Hierarchical Budgeting) Budgets for detail-level accounts can be controlled at an account higher in the hierarchical structure. (Pooled Budgeting) If a fund has a grant associated with it, budget checking will take into consideration the budget for the entire life of the grant.
FOAP Key Control

Banner contains three forms on which you may enter FOAP key control, control period, and control severity values. Fund Code Maintenance Form (FTMFUND) Fund Type Form (FTMFTYP) Chart of Accounts Maintenance Form (FTMCOAS) Regardless of which form you use, you must enter all three values on the same form. For example, if you enter a FOAP key control value on the Fund Code Maintenance Form, then you must enter control period and control severity values on that form as well. FOAP key control, control period, and control severity values on the Fund Code Maintenance Form (FTMFUND) override values on the Fund Type Form (FTMFTYP). Values on the Fund Type Form (FTMFTYP) override values on the Chart of Accounts Maintenance Form (FTMCOAS). You can select any combination of FOAP keys. For example, if you want to control a budget at the fund level, select only the Fund Key.
Control Period
You can perform budget availability checking on an annual basis, a quarterly basis, or a year-to-date basis. Control Period Option A initiates checking the availability of funds annually, regardless of the fiscal period specified on the accounting entry. This creates only one record in the Available Balance Table (FGBBAVL) for a FOAP in one fiscal year. This option provides the greatest performance.
November 2010
2-29
Control Period Option Q implies that budgeted funds within a quarter are available at the beginning of that fiscal quarter. Control Period Option Y accumulates the budget for all the fiscal periods up to the transaction period of the entry and then checks for availability on that basis. The Organization Budget Status Form (FGIBDST) displays the values posted to the operating ledger. You can see the total annual budget on this form regardless of the control period. The Budget Availability Status Form (FGIBAVL) displays only those funds available at the time of the query based on the specified control period.
Example:
The fund code control period is quarterly and budget entries of $10.00 are posted to each fiscal period. A total of $120.00 is available during the fiscal year and $30.00 is available at the beginning of each quarter. It is now the first day of the second quarter. The Organization Budget Status Form displays $120.00 in the Adjusted Budget column, while the Budget Availability Status Form displays $60.00 in the Adjusted Budget column (the sum of the first and second quarter budget). Online budget checking will not allow you to reserve or spend more than $60.00 from this budget until the beginning of the third quarter.
Control Severity
The Severity Control indicator determines what happens when the budget is not sufficient to post a transaction.
Error (E)
Banner does not let you complete the transaction. The system assigns an NSF condition to the transaction.
Once you complete and approve the transaction, the posting process will only provide a warning that the budget is not sufficient.
Warning (W)
Banner lets you complete the transaction. The system displays a warning.
Hierarchical Budgetary Control

This function enables you to control budgets at levels in a fund or organization structure that are different from the level of the fund and organization entered on the input transaction.
2-30
November 2010
You can load budgets at lower level funds or organizations and control them at a higher level in the structure. The non-sufficient funds editing will check against the sum of the budgets entered at levels below the control level. You can also load budgets directly at the control level fund and organization. Hierarchical budget control can be done in one of three ways: Control the budget at the same higher level fund. Control the budget at the same higher level organization. Control budget at various levels using combined budget control. Budget Control at Same Higher Level Fund With this method, the budget of an input fund is controlled by a budget control fund that is within the same hierarchy as the input fund. The budget control fund is entered on the Fund Code Maintenance Form (FTMFUND). Budget Control at Same Higher Level Organization With this method, the budget of an input organization is controlled by a budget control organization that is within the same hierarchy as the input organization. This budget control organization is entered on the record of the input organization on the Organization Code Maintenance Form (FTMORGN). Combined Budget Control This function enables you to define various hierarchical control points for available balance checking depending on the fund and organization combination on input. For combined budget control to occur, the Combined indicator in the input fund and/or organization record should be set to Y. When the indicator is set to Y, Banner will select the budgetary control fund and/or organization from the Hierarchical Budget Control Table (FTVHBUD), where the key is equal to the input fund and organization.
Pooled Budgeting
This function enables you to load a budget in one account and have other accounts access this account for the available budget. It also enables you to load a budget at lower level accounts and have the sum of those budgets considered as the base amount for nonsufficient funds editing and available balance display on Budget Availability Status Form (FGIBAVL) screens.
November 2010
2-31
To use pooled budgeting, you must indicate which account will be the focal point or pool account on the Account Code Maintenance Form (FTMACCT). The pool account does not need to be the same account type as the input account.
Grant Budgeting
Budgeting for grants is done by budgeting for a fund associated with the grant. Grant funds are budgeted by fiscal year. When Banner performs NSF checking in a transaction form, the budget for the grant/fund combination in all years is taken into consideration. If a budget has been rolled from the prior fiscal year to the current fiscal year, then NSF checking is similar to other non-grant funds. If a budget roll has not taken place, then the budget and available balance for the prior fiscal year is also taken into consideration when checking for an NSF condition in the current fiscal year.
Effective Date Processing

The General Ledger module enables you to insert records and specify effective dates for these records. General Ledger record types include (but are not limited to) Chart of Accounts, Account Codes, Account Index, Fund Type, Fund, Organization, Program Codes, Location Codes, and Bank Codes. The effective dates of committed General Ledger records may be changed. If you choose to leave the Effective Date field blank, the system defaults the current date. Effective dates are time stamped in the format DD-MON-YYYY HHMISS. You can enter a Termination Date for an existing record to disable it from supporting transactions on or after that date. To change the effective date for a general ledger record, use the Copy procedure:
1. From the form in which you want to make changes, select Enter Query. 2. Populate those fields on the form that identify which record to copy. For example, on
the Fund Code Maintenance Form (FTMFUND), populate the Chart of Accounts and Fund fields. Select Execute Query to view the fund code records.
3. Select Next Record until the most current record displays. The most current record
has no Next Change Date.

4. Select Insert Record or Next Record followed by Duplicate Record. Together, these
two functions create a space in the form just below the record being duplicated and copy the previous record.
2-32
November 2010
5. Make your changes to the new record. Enter the new effective date, which must be
equal to or greater than the system date. Click or select Save. When you save the new record to the form, the previous record's Next Change Date value becomes the current record's effective date. The Purchasing and Procurement and Accounts Payable modules do not maintain Next Change Date fields. Date processing in forms in these modules allows you to update existing records' Effective Dates without copying records. For example, populate the Agreement and Vendor fields on the Agreement Processing Form (FPAAGRD). Select Next Block. The agreement record displays. From the Effective Date field, select Next Item to go to the Termination Date field. Enter the date on which this record will no longer support transactions.
Pro-Rata Cost Allocation

Banner Finance provides an allocation feature that allows for the distribution of transaction amounts, on a user-defined pro-rata basis, from an Organization/Account/ Program string in an originating (source) fund to an Organization/Account/Program string in a target fund. The corresponding reductions in the source fund, to offset the amounts allocated to the target fund, are recorded in the specified user-defined contra-accounts.
Defining Allocation Information

The primary allocation parameters are defined on two forms: The Fund Code Maintenance Form (FTMFUND) is used to house certain higher level default allocation parameter values for a particular fund. The Allocation Charge Maintenance Form (FTMALCH) contains the controlling default allocation values for certain combinations of Organization/Account/ Program within a fund. The values present on the FTMALCH form override those defined on the appropriate fund code records (FTVFUND). FTMFUND The Fund Code Maintenance Form (FTMFUND Window 5) defines the Allocation Target Fund, the default source Contra-Account (Organization/Account/Program) and the default Allocation Percentage on the source Fund record. Any or all of these five
November 2010
2-33
fields may contain null values, but if the Allocation Target Fund is null, the other fields will not accept values.
1. Enter a valid Allocation Target Fund code. The fund title will be displayed
automatically. The Allocation Target Fund field must be populated for allocations to occur on transactions with this Fund Code.
2. Enter the desired default source Contra-Account Organization, Account, and/or
Program. Valid entries are accepted in any or all of the three fields. The default source Contra-Account accepts accounts of any Internal Account Type.
3. Enter the default Allocation Percent. This field will accept only positive values from
0.00% to 100.00%. If the default Allocation Percent is 0.00% or null, no allocations occur on transactions with this Fund Code unless a non-zero percentage is present in the Allocation Charge Maintenance Form (FTMALCH). FTMALCH The Allocation Charge Maintenance Form (FTMALCH) allows you to define the relationship between the Allocation Source Organization/Account/Program string, or any element thereof, and the Organization/Account/Program string, or any element thereof, in the Contra-Account that will absorb the charge. It also defines the percentage to be allocated to the Target Fund.
Note When the Pro Rata Allocation Process (FGRPRAP) is run, FTVALCH records take precedence over FTVFUND records. 1. Enter the source Fund Chart of Accounts Code and the source Fund Code in the
Key Information. The source Fund Title defaults.

2. Enter the Effective Date (or use the default of the current date) and the Termination
Date of the Allocation Charge Control record. The Next Change Date will be displayed automatically.
3. The Allocation Source Organization, Account, and Program fields are optional.
Valid entries are accepted in any or all of the three fields. Any source transaction whose Fund/Organization/Account/Program matches the entries set here will undergo the allocation process with the Contra-Account information specified in the other part of the line. Only account codes with an Internal Account Type (FTVSDAT) value of 50, 60, or 70 are accepted in the Allocation Source Account field.
2-34
November 2010
Any transactions whose Organization/Account/Program strings or individual elements are not entered in the Allocation Source fields for the source Fund are allocated using the default Contra Organization/Account/Program and Percentage values stored in the source Funds Fund Code record (FTVFUND). If there are no such values on FTMFUND, the Organization, Account, and/or Program of the original transaction are used.
4. The Contra-Account Organization, Account, and Program fields are also optional.
Valid entries are accepted in any or all of the three fields. Although each of these fields is optional, an entry in any of the Contra-Account fields causes the entire default source Contra-Account Organization/Account/Program string on the Source Funds Fund Code record (FTVFUND) to be overridden. An entry containing null values for all three of the Contra-Account Organization/Account/Program fields causes the source Contra-Account values stored in the source Funds Fund Code record (FTVFUND) to be used. The Contra-Accounts Account field may accept any Internal Account Type value.
5. The Allocation Percentage accepts only positive values from 0.00% - 100.00%. This
field is optional, but any entry overrides the default Allocation Percentage on the source Funds Fund Code record (FTVFUND). A null value entry means that the Allocation Percent on the source Funds Fund Code record (FTVFUND) is used for the allocation. An entry of 0.00% results in no allocation for the chosen Allocation Source string. Therefore, an entry of 0.00% is not equivalent to a null entry, as a null percentage means that an allocation could occur using the default percentage found in the FTVFUND table, while 0.00% means that allocation will not occur. An Allocation Source Organization/Account/Program string may not point to more than one set of values for Contra-Account Organization/Account/Program string and Percentage. The three Contra-Account fields and the Allocation Percentage field may not all be null. The FTVALCH record, by design, allows you to create overlapping (but not duplicate) Allocation Source Organization/Account/Program string references. The Pro-Rata Allocation Process recognizes the overlapping Allocation Source account strings and determines the order of precedence in which data is applied to the allocation. The hierarchy for determining order of precedence moves from the most detailed entry to the least detailed entry as follows:
1. FTVALCH specifies Organization, Account, and Program 2. FTVALCH specifies Organization and Program 3. FTVALCH specifies Organization and Account 4. FTVALCH specifies Account and Program 5. FTVALCH specifies Organization
November 2010
2-35
6. FTVALCH specifies Program 7. FTVALCH specifies Account 8. No FTVALCH record; use FTVFUND values
For example, if two records on FTMALCH have identical source organizations and programs, but only one of these has a source account, the records are overlapping. The record which contains all three elements fits hierarchy levels (1) and (2); the one with only organization and program fits hierarchy level (2) only. A transaction whose account data matches the organization, account, and program specified in the first of these two records will be allocated with the Contra data found in that record. Such a transaction matches both the (1) and (2) elements in the hierarchy, but the (1) element is chosen over the lowerlevel (2) element. Another transaction with the same organization and program but a different account will be allocated with the Contra data found in the second of these two records since it only matches the (2) element in the hierarchy.
Limiting Rule Groups in the Pro-Rata Allocation Process

The Allocation Rule Group Maintenance Form (FTMALRG) allows you to limit the ProRata Allocation Process to certain classes of documents specified by rule group. If there are no entries on FTMALRG, then allocation transactions will be selected without regard to rule groups. If any entries are made on this form, allocations will only be made on transactions whose rule classes fall within the specified rule group(s). This form consists of repeating records with a field for the Rule Group and additional fields for Effective Date, Termination Date, and Next Change Date. All entries on this form are optional, and the Next Change Date is a non-enterable field. This form will operate on a system-wide basis for all Allocation Charge Control records.
Running the Pro-Rata Allocation Process (FGRPRAP)

The Pro-Rata Allocation Process inserts entries into FGBTRNI to produce journal vouchers for all of the allocation entries created. The process consists of the following steps:
1. You are prompted to enter the user-defined parameters for the process. The
Allocation Begin Date and Allocation End Date parameters are used to select the transactions that produce the allocation calculations. These dates each default to the system date if left blank. The Allocation End Date must be the same as or later than the Allocation Begin Date, and any date later than the system date is considered invalid. The Allocation Transaction Date is the user-defined effective posting date assigned to the transaction. This date defaults to the system date if left blank and must be the same as or later than the Allocation End Date. The Source Funds parameter is optional. An entry or entries here limits the selection of transactions to those involving these source funds. Any source fund must have a
2-36
November 2010
valid entry in the Allocation Target Fund field on the FTVFUND record. If no entry is made in this parameter, all funds are eligible for allocation. The only valid entries for the Internal Account Type parameter are 50, 60, or 70. This parameter limits the selection of transactions to those whose account is of one of the Internal Account Types specified. A null value entry automatically includes transactions of all three Internal Account Types in the allocations. The Allocation Target Bank Code and Allocation Contra Bank Code parameters define these respective bank codes to supply the appropriate bank fund and account information when the original transaction is a YTD transaction.
Tip The two Bank Code parameters are not prompted if you have selected Preview mode.
A null entry for the Report Execution Mode parameter defaults to P (Preview). If P (Preview) is selected, no updating takes place and only an as if report is produced. An entry of U (Update) in the Report Execution Mode parameter initiates the Pro-Rata Allocation Process. Enter S (Summary) in the Report Type parameter to produce the summary version of this report. Enter D (Detail) in the Report Type parameter to produce the detailed version of this report. Enter N (No Report) in the Report Type parameter to suppress production of a report (unless the Report Execution Mode = Preview). Select the Number of Printed Lines per Page as desired.
2. The system locates all of the Source Fund(s) transactions in the FGBTRND table that
meet the criteria of the report parameters entered, contain the appropriate Source Fund records in the FTVFUND or FTVALCH records, and pass through any transaction filters noted in the FTVALRG record.
3. Once the eligible source transactions are located, the process totals all of the
transactions with the same combination of Fund, Organization, Account, Program, and Field Codes (for example, OBD, YTD, etc.). The user-defined Allocation Percentages are then applied to each of the derived totals, creating a separate Allocated Amount for each derived total line of account distribution.
4. Two sets of transaction distribution postings are developed from the Allocated
Amounts for each derived total line of account distribution. The first set represents the Allocations From the Source Fund(s). The Organization/Account/Program string for each set of source transactions will be replaced by the appropriate Contra-Account Organization/Account/Program strings from the FTVFUND or FTVALCH records. If no data is found in either of these places, the Organization, Account, and Program from the original transaction will be used. Each like Fund/Organization/Account/ Program/Field string is made into a transaction with a Rule Class of AC01 - AC07.
November 2010
2-37
The A in the Rule Class Code stands for allocation, the C designates Contra-Account, and the 01 through 07 refers to the field indicator of the original transaction. The second set of transaction distribution entries represents the Allocations To the Target Fund(s). The Allocation Target Fund Code(s) on the FTVFUND record(s) will replace the Fund Code(s) of the original transactions. Each like Fund/Organization/ Account/Program/Field string is made into a transaction with a Rule Class of AT01 AT07. The A in the Rule Class Code stands for allocation, the T designates the target fund, and the 01 through 07 refers to the field indicator of the original transaction.
5. Next, each of the eligible transactions used in the Pro Rata Allocation Process is
marked with the journal entry number, sequence number, and percentage so that you may request a historical report of the transactions used to develop any allocation entries, and also to prevent their inclusion in any subsequent Pro-Rata Allocation processes. These markers do not appear in the online display or reports.
6. The final step in the Allocation Process is to produce an Allocation Control Report (if
selected). The summary version of the report shows the summary totals developed for each Allocation Source record and the Allocated Amounts for each derived total line of account distribution. The detailed version of the report produces the full Fund/ Organization/Account/Program account string detail of all the eligible transactions selected to create an allocation entry. The detailed report also includes the summary totals developed for each Allocation Source record and the Allocated Amounts for each derived total line of account distribution.
7. If the Report Execution Mode = U (Update), the end result of this process is the
creation of journal voucher entries in the FGBTRNI table. The FGRTRNI process must be run in order to produce the journal voucher, and FGRTRNR must be run to determine whether any errors occurred in FGRTRNI. The final step is to run FGRACTG to post the journal entry.
Running the Pro Rata Allocation Report (FGRPRAR)

The Pro Rata Allocation Report lists the allocations made by FGRPRAP and allows you to re-create a list of the source transactions for any allocation transactions produced by the Allocation Process. The report consists of the following user-defined parameters: The Allocation Document Number selects the journal voucher document whose allocations will be reported. If this parameter is left blank, the Report Begin/End Dates and the Chart of Accounts will be prompted; otherwise, these parameters will be bypassed. The Report Begin Date and Report End Date determine the range of dates from which allocations are selected. The Report End Date must be the same as or later than the Report Begin Date. Both parameters default to the system date. The Chart of Accounts parameter determines the chart of accounts from which allocations will be reported.
2-38
November 2010
The Report Type parameter enables you to select a S (Summary) report or a D (Detailed) report. The summary version reports the summary totals developed for each set of Allocation Source records and the Allocated Amounts Percentage and Contra Organization, Account, and Program for each derived total line of account distribution. The detailed version reports the Document Number, Organization, Account, Program, and Field of all the eligible transactions selected to create an allocation, in addition to the information on the summary report. If this parameter is left null, the S (Summary) report is produced. Select the Number of Printed Lines per Page as desired.
Governmental Accounting Standards Board (GASB) Reports Processing

This section provides you with information needed to process any of the six reports that comply with statement numbers 34 and 35 of the Governmental Accounting Standards Board (GASB). Attribute reporting enables you to map your Chart of Accounts to the correct columns and rows of the reports, using the seed data provided with the release. You can modify the column title and line item descriptions, as needed, to suit your institutions reporting needs. For samples of GASB reports, refer to the Reports and Processes chapter.
Note Reporting for GASB will not generate printed output directly, instead it creates a comma separated value (.csv) file. Open this file with a standard spreadsheet tool, such as Microsoft Excel. Within Excel, you can customize each report for transactions unique to your institution and enhance the formatting to produce camera-ready financial statements.
GASB 35 Reports
The following reports are meant for use for public institutions that report only businesstype activities.
Public Colleges and Universities Business-type Activities Only

Statement of Net Assets Statement of Revenue, Expenses, and Changes in Net Assets
November 2010
2-39
GASB 34 Reports
The following reports are meant for use by state and local governments and public institutions that report both government and business-type activities.
Government Wide Statements

Statement of Net Assets Statement of Activities
Governmental Funds Statements

Balance Sheet Statement of Revenue, Expenditures, and Changes in Fund Balances
GASB Extract Process (FGPGEXT)

The Data Extract Process is run via job submissions. This process uses the parameters entered to extract the appropriate information from the General Ledger (FGBGENL) and Operating Ledger (FGBOPAL) tables to the table FGWREPT. (These parameters are identified in the table at the end of this section.) If the extract is run for a Chart and End Date that already exist in the table, all records will be replaced. (Reclassification entries are stored separately and are not affected).If the extract is run in Purge mode (parameter 07), then records for the Chart, End Date, and Report Type(s) indicated are removed and not replaced. If any changes are made to Attribute associations or any additional transactions are posted to the ledgers, the extract must be re-run before the changes are reflected in the reports. (This is not required for reclassification entries via FGARCLE). If any FOAPAL elements do not have attributes selected, or have duplicate associations, the FGPGEXT process generates error reports. Another report identifies FOAPAL elements intentionally excluded from the GASB statements. Samples of each of the error reports are included in the Reports and Processes chapter. If there have been transactions directly to Fund Balance accounts (internal ATYP 40) during the period for which the extract is run, the Control Report will show the Net Fund Balance Activity from all funds. This will occur, for example, if Fixed Asset Capitalization is directed to a Fund Balance Account. This may cause an out-of-balance condition between the Operating reports and the Balance Sheet reports unless an equivalent amount of revenue/expense has been excluded from the Operating report. If there is no activity or the transactions net to .00, then there will be no message on the Control Report.
2-40
November 2010
Parameter
Description
01 02
Chart of Accounts End Date of Period Reported
Enter Chart for which data is to be extracted (required) Enter end date for reporting (required) this is converted to the Fiscal Year and Period in which the date entered falls for purposes of the extract and GASB reporting, and extract includes all data to the end of that period. Include Accrual (Y/N) Extract for GASB 34 Statement of Net Assets and Statement of Activities (Y/N) Extract for GASB 34 Balance Sheet and Statement of Revenues, Expenditures, and Changes in Fund Balances (Y/N) Extract for GASB 35 Statement of Net Assets and Statement of Revenues, Expenses, and Changes in Net Assets (Y/N) Processing mode: E P Extract data (replace existing data for Chart FY/ Period, and Report Pair(s) indicated. Purge data for Chart, FY/Period, and Report Pair(s) indicated
03 04 05
Include Accrual Government Wide Financials Governmental Funds Financials Public Inst BTA Financials Processing Mode
06
07
GASB Reclassification Entry Form (FGARCLE)

Use this form to enter adjusting or reclassifying accounting transactions. The sum of the transaction amounts must equal the amount in the document header. This form functions similarly to the Journal Voucher Forms (FGAJVCD, FGAJVCM, and FGAJVCQ) using the JE15 rule class (Journal Type). Information collected on this form is not posted to the main ledgers but is used for reporting purposes only. Access this form from the Generate GASB Reports Menu (*FINGENGB). After a document is marked as Complete, it can be viewed in query mode only. You can query on any of the columns in the main block of this form. For detailed information about this form, refer to the online help.
November 2010
2-41
Transaction Reclassification Query Form (FGIRCLE)

Use this query form as an investigative tool to review reclassification entries and trace their impact on the reports. You can use this form to perform a query by document, by attributes, or by FOAP elements. Option links provide access to Query Document (FGARCLE), Trial Balance (FGITBAL) or Budget Status (FGIBDST) forms. The format of the Header and Detail blocks on this form differ depending on the type of query you choose. For detailed information about this form, refer to the online help.
GASB Parameter Form (FGAGASB)

Use this form to generate GASB reports. Reports are formatted in a comma separated value format file (.csv) that can be opened in a spreadsheet program such as Microsoft Excel.
Specifying a Location for the Extract File

To enter the location for the system to save this file, select the Set GASB reports directory preference option. In the Directory Option window that appears, enter the location where the file should be saved, for example: c:\windows\temp, then select the Save and return to main window option. Client/Server users can use any drive/folder on or mapped to their PC to which they have write access. Web-enabled users can use any drive/folder on or mapped to the Forms Server to which they have write access. They must be able to access that location from their PC, either by direct mapping or FTP, in order to retrieve and use the output file. Citrix users can use any drive/folder on or mapped to the Citrix Server to which they have write access, including the local PC drives. If a Banner session is left active when disconnecting from the Citrix Server, however, the communication with the local drives is severed. After reconnecting to the Citrix Server, you will need to close Banner and start a new session to re-establish the link to local drives for data extract. If you select the Return to main window option, you do not save any changes made to the location.
Warning If you try to extract the report data to file without first specifying a location, you receive the following message: No default data extract location found. Please enter the directory where the GASB report extract file should be saved.
2-42
November 2010
Extracting Report Data to File

After you enter parameters (see the following table for details) and make your selections, select the Extract Report Data to File option.
Parameter Chart of Accounts
Description
Select the appropriate code for the Chart of Accounts from the Chart of Accounts List validation form (FTVCOAS). If you leave this field blank, the GASB report will include information from all charts that have data extracted for the fiscal year and fiscal period selected. Enter the fiscal year to report. Unless you select the Extract Attributes option, you must enter a value in this field. Enter the fiscal period to report. Unless you select the Extract Attributes option, you must enter a value in this field. Select the radio button associated with the report you want to generate: GASB 34 Government Wide Statement of Net Assets GASB 34 Government Wide Statement of Activities GASB 34 Governmental Funds Balance Sheet GASB 34 Governmental Funds Statement of Revenues, Expenditures, and Changes in Fund Balances GASB 35 Statement of Net Assets GASB 35 Statement of Revenues, Expenses, and Changes in Net Assets
Fiscal Year
Fiscal Period
Report Type
November 2010
2-43
Parameter Data Extract Mode:
Description
Select the radio button associated with the report mode you want: Summary The report appears in summary form in GASB report format. Detail The file includes the detail rows from the extract and reclassification tables that were included in the summarized report. Exclusions/Errors This file includes all the remaining rows from the extract and reclassification tables, that is, the fund, account, and program elements that were excluded or were not associated to an attribute.
Note: Incomplete reclassification documents are not included in the Exclusions/Errors file. To view these documents, execute a query on the Transaction Reclassification Query Form (FGIRCLE).
Attributes This file includes attribute associations for the selected GASB report.
Expense Classification:
For the statements of revenues and expenses, select a radio button associated with one of the following options: Expense Classification by Account (Object) This is the default value for the GASB 35 Statement of Revenues, Expenses, and Changes in Net Assets. Expense Classification by Program (Function).This is the default value for the GASB 34 Government Funds Statement of Revenues, Expenses, and Changes in Fund Balances.
Changing Attribute Types and Values

You may want to customize the order of data and the literals that appear on your GASB reports. While there are restrictions on the changes that can be made to the Attribute Types and Values as delivered, there is also a great deal of flexibility. As a general rule, you may insert or delete Attribute Value Codes that are associated with the rows of a report, and may change the descriptions to suit your preferences. The sort of the rows within each section of the report is based on the values. (Values intended to exclude information from reports should all begin with 9999. Two values have been included in the seed data to avoid defaulting a value, which would occur if using Sets Required.) Do not insert, delete, or change any Attribute Value Codes that are associated with the columns of a report. You can, if you like, change the descriptions to alter the
2-44
November 2010
column headings. These include all the Fund Attributes, as well as the Account Attributes associated with type G4GWE1ER for the columns of the Government Wide Statement of Activities. Do not insert, delete, or change any Attribute Type Codes. You can, if you like, change the descriptions to alter the Heading and Subtotal literals for the sections of the reports. The order and placement of the report sections is pre-determined based on the examples from the GASB Statements and cannot be changed.
Associating FOAPAL Elements to Attributes

Account type and fund type associations facilitate the association of Fund and Account codes to attribute types and values. In addition, a hierarchy is included to retrieve attributes for GASB reporting.
Associations for Fund, Account, and Program Codes

Associations for Fund codes can be based on level 2 fund type, level 1 fund, or low-level fund. Associations for Account codes can be based on level 2 account type, one userdesignated hierarchy level, or low-level account code. The account hierarchy is determined from the System Data (FTMSDAT) record with Entity/Usage Code GASB and Attribute Code ACCT_HIER_LEVEL. This is initially set to LEVEL1 with the installation of release 4.2/5.2, but can be changed to any of the following values depending on which is most meaningful for your Chart of Accounts. LEVEL1Level 1 Account Code LEVEL2Level 2 Account Code PREDPredecessor Account Associations for Program codes can be made at the level 1 program or low-level program code.
Retrieval of Attributes for GASB Reporting

If a match is found at the lowest level, that is, the Fund, Account, or Program used at the time of data entry has been associated to an attribute value, then this value will be used. If a match is not found at the lowest level, then the level 1 Fund or Program and the account hierarchy you specified will be used to find an attribute value. If a match is not found at this level, then, for Fund and Account, the level 2 Type (ftvfund_ftyp_code and ftvacct_atyp_code) is used to find an association.
November 2010
2-45
Setting up Program / Account Codes

Program Codes
To accommodate expense reporting by program or function in the operating reports, you may need to set up the following program codes to use in reclassification entries for GASB reporting. Interest Expense Depreciation Expense Capital outlay General Revenue Enterprise Auxiliary operations (one for each operation to be reported in the 34 Statement of Activities) Component Unit operations (one for each row in the GASB 34 Statement of Activities)
Account Codes
To accommodate other reporting requirements, you may need to set up the following account codes to use in reclassification entries for GASB reporting. Invested in capital assets net of related debt with an internal account type of 40 Fund Balance account codes (internal account type of 40) for each line to be displayed in the Net Assets section of the Statement of Net Assets or Balance Sheet
Setting up GASB 35 Public Institution Business-type Activity Statements

This section provides you with the association information you will need to set up the GASB 35 Statement of Net Assets and the Statement of Revenue, Expenses, and Changes in Net Assets. Use the FOAPAL Attribute Association Form (FTMFATA) to establish the associations.
2-46
November 2010
Use the following steps to create associations:

1. Associate each fund type/code with one attribute value linked to type.
G5BAFUND - Public Institution BTA Column - This attribute type determines the column in which the data will be summarized (or excluded).
Note The bank funds should usually be excluded to avoid overstating or understating the cash in the GASB 35 General Ledger statements. 2. Associate each account with an internal ATYP of 10 or 20 with one attribute value
linked to one of the types in the following list. This places the summarized data on the designated row within the Asset and Liability sections of the Statement of Net Assets (or exclude). G5BAA1CA - Current Assets G5BAA2NA - Non-Current Assets G5BAA3CL - Current Liabilities G5BAA4NL - Non-Current Liabilities G5BAA9EX - Exclude Assets/Liabilities
3. Associate each account with an internal ATYP of 30 or 40 with one attribute value
linked to one of the types in the following list. This will place the summarized data on the designated row within the Net Asset section of the Statement of Net Assets (or exclude). G5BAN1NA - Net Assets G5BAN9EX - Exclude Net Assets
4. Associate each account with an internal ATYP of 50, 60, 70 or 80 with one attribute
value linked to one of the types in the following list. This will place the summarized data on the designated row within the Revenue and Expense sections of the Statement of Revenues, Expenses, and Changes in Net Assets (or exclude). G5BAR1OR - Operating Revenues G5BAR2OEX - Operating Expenses G5BAR3NO - Non-Operating Revenues (Expenses) G5BAR4OT - Other changes G5BAR9EX - Exclude operating account
November 2010
2-47
linked to one of the types in the following list. This will place the summarized data on the designated row within the Net Asset section of the Statement of Net Assets (or exclude). G5BAN1NA - Net Assets G5BAN9EX - Exclude Net Assets You also need to associate each account with an internal ATYP of 90 or 95 with one attribute value linked to one of the types in the following list. This will place the summarized data on the designated row within the Other Changes section of the Statement Revenues, Expenses, and Changes in Net Assets (or exclude). G5BAR4OT - Other changes G5BAR9EX - Exclude operating account
6. Associate each program with one attribute value linked to type.
G5BAPROG - Program Code Attributes for Expenses - This attribute type summarizes data by program code for expenses only (accounts with Attribute Type G5BAR2OE) when the Expense Classification on FGAGASB is by program. Associate program codes with one or more value in this attribute type.
Setting up GASB 34 Governmental Funds Statements

This section provides you with the association information you will need to set up the GASB 34 Balance Sheet; and the Statement of Revenues, Expenditures, and Changes in Fund Balances. Use the FOAPAL Attribute Association Form (FTMFATA) to establish the associations. Use the following steps to create associations:
G4GFFUND - Governmental Funds Column This attribute type determines the column in which the data will be summarized (or exclude). You may use a maximum of six Major Funds columns in addition to the General Fund and Other Funds columns (total of eight columns). Bank Funds should be excluded to avoid duplicating the totals found in the inter-fund cash accounts.
linked to one of the types in the following table. This will place the summarized data on the designated row within the Asset and Liability sections of the Balance Sheet (or exclude).
2-48
November 2010
G4GFA1CA - Assets G4GFA2CL - Liabilities G4GFA9EX - Exclude Assets/Liabilities

3. Associate each account with an internal of ATYP 30 or 40 with one attribute value
linked to one of the types in the following table. This will place the summarized data on the designated row within the Net Asset section of the Balance Sheet (or exclude). G4GFN1NA - Net Assets G4GFN9EX - Exclude Net Assets
value linked to one of the types in the following table. This will place the summarized data on the designated row within the Revenue and Expense sections of the Statement of Revenues, Expenditures, and Changes in Fund Balances (or exclude). G4GFR1OR - Revenues G4GFR2OE - Expenses G4GFR3OS - Other Financing Sources (Uses) G4GFR4SI - Special Items G4GFR9EX - Exclude Operating Accounts
linked to one of the types in the following table. This will place the summarized data on the designated row within the Net Asset section of the Balance Sheet (or exclude). G4GFN1NA - Net Assets G4GFN9EX - Exclude Net Assets You also need to associate each account with an internal ATYP of 90 or 95 with one attribute value linked to one of the types in the following table. This will place the summarized data on the designated row within the Other Changes section of the Statement of Revenues, Expenditures, and Changes in Fund Balances (or exclude). G4GFR4SI - Special Items G4GFR9EX - Exclude Operating Accounts
6. Associate each program with one attribute value linked to type.
G4GFPROG - Program Code Attributes for Expenses - This attribute summarizes data by program code for expenses only (accounts with attribute type G4GFR2OE) when the Expense Classification on FGAGASB is by program. Associate program codes with one or more value in this attribute type.
November 2010
2-49
Setting up GASB 34 Government Wide Statements

This section provides you with detailed setup information for the GASB 34 Statement of Net Assets and Statement of Activities. Use the FOAPAL Attribute Association Form (FTMFATA) to establish the associations. Use the following steps to create associations:
G4GWFUND - Government Wide Column This attribute type determines the following: the column in which data will be summarized on the Statement of Net Assets the column in which data will be summarized in the Net (Expense) Revenue and Changes in Net Assets section of the Statement of Activities placement and sub-total breaks in the Functions/Programs section of the Statement of Activities exclude fund from the report
Note Usually, the bank funds should be excluded to avoid overstating or understating the cash in the GASB 34 General Ledger statements. 2. Associate each account with an internal ATYP of 10 or 20 with one attribute value
linked to one of the types in the following list. This will place the summarized data on the designated row within the Asset and Liability sections of the Statement of Activities (or exclude). G4GWA1CA - Assets G4GWA2Cl - Liabilities G4GWA9EX - Exclude Assets/Liabilities
3. Associate each account with an internal ATYP of 30 or 40 with an attribute value
linked to one of the types in the following list. This will place the summarized data on the designated row within the Net Asset section of the Statement of Activities (or exclude). G4GWN1NA - Net Assets G4GWN9EX - Exclude Net Assets
value linked to one of the types in the following list. This will determine in which column data will be summarized in the Expenses - Program Revenues section of the Statement of Activities.
2-50
November 2010
G4GWE1ER - Column for Expenses/Revenues G4GWE9EX - Exclude Expenses/Revenues If a program code has been associated to the value GENREV, an additional association for operating accounts is required to the following attribute types. This will place the summarized data on the designated row within the General Revenue section of the Statement of Activities (or exclude). G4GWG1RV - General Revenue G4GWG9EX - Exclude General Revenue
linked to one types in the following list. This will place the summarized data on the designated row within the Net Asset section of the Statement of Net Assets (or exclude). G4GWN1NA - Net Assets G4GWN9EX - Exclude Net Assets You also need to associate each account with an internal ATYP of 90 or 95 with one attribute value linked to one types in the following list. This will place the summarized data on the designated row within the General Revenue section of the Statement of Activities (or exclude). G4GWG1RV - General Revenue G4GWG9EX - Exclude General Revenue
6. Associate each program with one attribute value linked to the following attribute
type. This will place the summarized data on the designated row in the Functions/ Programs section of the Statement of Activities. G4GWPROG - Program Activities For transactions using a program code associated with an attribute value of GENREV, the data will fall through to the General Revenue section where the rows are summarized based on account attributes associated with attribute type G4GWG1RV. If program codes used at the time of data entry do not reflect the summarization desired for GASB purposes, you may want to use Value 9000WASH Pending reclassification, then use the reclassification form to re-distribute via other program codes.
November 2010
2-51
Producing GASB Reports

This section provides you with information about how to produce GASB reports. Additional information about these reports is included in the Reports and Processes chapter.
1. Update attribute values and types to reflect your GASB report column and row titles
on the Attribute Type Maintenance Form (FTMATTT) and the Attribute Value Maintenance Form (FTMATTV).
2. Update the account hierarchy search on the SDAT record using the System Data
Maintenance Form FTMSDAT, if necessary.

3. Associate Fund Types/Codes, Account Types/Codes, and Program Codes to the
appropriate attributes for GASB reporting using the FOAPAL Attribute Association Form (FTMFATA).
4. Update the General Users Preference Form (GUAUPRF) with the directory in which
to save the GASB reports.

5. Run the GASB Reports Extract Process (FGPGEXT). This process requires a Chart
Code, As Of date, and Which Group of Reports. The As Of date defines the fiscal period assigned to each record in the extract table.
6. Review the error messages and make any required changes. Rerun the extract process
(FGPGEXT).
Note If changes or adjustments are made to the attribute associations or to the ledgers (via JV, Invoice, Encumbrance, and so on) you will need to rerun the extract process FGPGEXT to refresh the extract table data with the new associations. 7. Enter reclassifications on FGARCLE, the Reclassification Entry Form. The
transaction date determines the fiscal period for the transaction. It should be the same as the extract process As of Date. If not, the entries will not match up with the extract data and the GASB reports will not be correct.
8. Produce the GASB report file using the GASB reports parameter form, FGAGASB.
The data reported are determined by the fiscal year and period parameters. Only data in the extract and reclassification table that match these parameters are included in the report. The resulting CSV file is saved to the directory you specified on GUAUPRF, the User Preference Form.
9. To review the reports, open the CSV file with a spreadsheet program. If adjustments
are posted with a JV, you must rerun the extract process FGPGEXT so the adjustments are reflected on the reports. If changes are made to the attribute
2-52
November 2010
associations, rerun the extract process FGPGEXT to update the extract table with the new associations.
10. To edit and format the reports, use standard edit and format functions for your
spreadsheet program. (Some helpful hints for PC users of Microsoft Excel users are listed below.)
For PC Users: Helpful Hints for Using Microsoft Excel

For additional information and guidance on using the following tips, refer to Microsoft Excel Help. To change formatting or width for multiple columns at once, highlight the columns by clicking on the letter in the column heading. Drag across columns or use shiftclick to highlight adjacent columns. Use ctrl-click to highlight non-adjacent columns. (Same applies to rows.) To change the width of a column or height of a row, hover the cursor over the dividing line in the heading until a bar with arrows on opposite sides appears click and drag to desired width or height. Choose Format-Cells-Number tab and category Number to access the check box to separate thousands with commas and to set the number of decimals to display. Choose Format-Cells-Number tab and category Custom to change the number of significant commas and display of 0. ###,##0.0,;(###,##0.0);- as a custom format will display In Thousands using parentheses around negatives and a dash for zeros.
Source Data Display
25,485,860.5 -582.992.42 0
25,485.9 (583.0) -
To have longer column headings wrap to multiple rows, choose Format-CellsAlignment tab, and check Wrap Text under Text Control. Choose Right for Text alignment Horizontal to have these line up with the numbers which follow. To have longer column headings center over multiple columns, highlight all the columns, choose Format-Cells-Alignment tab, and choose Center Across Selection for Text alignment Horizontal. (Headings intended to stretch over multiple columns have been placed in the first of the columns so that this feature may be used.) You may also wish to click the Border tab and put a line across the bottom of the selection. You can create and save styles (under Format menu) that incorporate multiple aspects of the formatting and alignment suggestions above, then easily merge and apply the style when you open a new GASB.csv file.
November 2010
2-53
To change zeros to blank cells for a workbook, choose Tools-Options-View tab, and uncheck Zero Values. To change zeros to a dash (-) choose Edit-Replace and use 0 for Find what and - for Replace with. Be sure to check Find entire cells only (not necessary if you use custom format to display 0 as dash).
General Accounting Transactions

Creating a Journal Voucher Entry Transaction
Three forms are available to create a Journal Voucher Transaction entry. Use either the Journal Voucher Entry Form (FGAJVCD) described below, the Journal Voucher Quick Form (FGAJVCQ), or the Journal Voucher Mass Entry Form (FGAJVCM).
Note FGAJVCQ is similar in function to FGAJVCD but contains less detail.
FGAJVCD
Initiate the processing to create a journal voucher entry on the Journal Voucher Entry Form (FGAJVCD). Complete this form as follows. Key Information
1. Enter an existing journal entry number in the Document Number field or allow the
system to automatically generate a number by selecting Next Item or by entering NEXT. You can copy an existing journal voucher by using either the Copy icon or the options menu. An existing journal voucher refers to a journal voucher that is either in process or that has already been posted. For more information, refer to Copy Journal on page 2-54.
2. Use the optional Submission Number field to limit access to posted submission
numbers. Copy Journal To copy a journal from the journal voucher forms, use the following process.
1. Select the Copy Journal option from the options menu or press the Copy icon. 2. Enter the source journal voucher document number.
2-54
November 2010
3. Enter a new document number, leave this field blank or enter NEXT to generate a new
document number.
4. Change the transaction date as required (the default value is the current date). 5. You may reverse the entry. Select the Reverse JV check box to create the new journal
with the opposite sign from the Copy From journal.

6. Optional: Select the Copy Text check box to copy header text from the source journal
voucher.
7. Select OK.
Journal Voucher Document Header The Transaction Date field defaults to the system date, but you may enter another date. Populate the Document Total field, which represents the sum of the absolute values of the accounting sequence lines you enter. Check the Redistribute field if you intend to distribute the dollar amounts on a percentage basis. When using the distribution method, use the Distribution Total in calculating the percentages. If you leave this field blank, the system applies distribution percentages to the Document Total. If the NSF Checking check box is selected, the system performs NSF checking online. Otherwise, the Posting Process performs the NSF checking. The Defer Edit indicator defaults to the global setting of the Defer Edit indicator on the System Control Table (FSASYSC). If the indicator on FGAJVCD defaults to unchecked, it invokes the edits on the rule class for each committed accounting sequence. Select the Defer Edit check box to bypass the editing process at the time of transaction entry. If you choose this option, you may complete the document online. A batch program edits the transaction. The system documents errors to an error report file for those documents containing errors. Select Next Block or click Transaction Detail to access the Transaction Detail Window and enter the accounting sequences. Transaction Detail Window The system updates the Status indicator field after you save each transaction record. Allowable values are as follows:
A E N P
In the process of being edited Error condition due to an edit failure Non-sufficient funds for transaction to proceed Postable
November 2010
2-55
When the Defer Edit box is checked, the Document Status field remains blank. You may enter a sequence number or allow the system to default the Sequence field. The Journal Type field refers to the Rule Class or Transaction Code for this accounting entry. Enter the accounting distribution, starting with the COA (Chart of Accounts) Code. (This defaults from your User Profile.) Enter the percentage or dollar amount being charged to the accounting distribution in the appropriate fields. Along with the FOAPAL values, you must populate the Debit/Credit indicator. Depending on the rule class you select, the values are D, C, or (+), (-). Populate the Description field. Additional fields on this record may be required depending on the nature of the transaction. For example, a cash transaction requires that you enter the Bank Code, but a budget rule requires a Budget Period. If you are recording direct changes for a project in the Cost Accounting module, enter the appropriate project code in the Project field. Save the record after you populate the appropriate fields. The system performs the editing and available balance processes as long as the Defer Edit indicator is not checked. When you have finished, use the Next Record function to move to the next accounting sequence record. Once you have entered all the records for this document, either click Complete or select Complete from the Options menu. Posting The system balances the document when you click or select Complete from the Completion Window. The system checks that the absolute values of the individual accounting sequences add up to the Document Total. The system also verifies any balancing specifications on the rule classes (debits equal credits on two-sided entries). If the Defer Edit indicator is not checked, go to the appropriate approval forms and approve this document. The system posts completed documents in the next posting run (FGRACTG), and you may review the results from the General Accounting Query forms.
2-56
November 2010
Note To approve documents, you must navigate to the User Approval Form (FOAUAPP) or to the Document Approval Form (FOAAINP).
Workflow Complete If a journal voucher is completed as part of a workflow activity, an Information Alert will display to advise the user of the disposition of the journal voucher. The workflow activity is submitted as complete.
Automatic Journal Voucher Process

Use the Automatic Journal Voucher Process to establish a journal voucher and a schedule for submission to the Posting and Approval Processes. The system creates an automatic journal voucher using the Automatic Journal Maintenance Form (FGAAUTO). Access FGAAUTO from the General Accounting Transaction Forms Menu (*FINGENLA). Use the following procedure to create and process an automatic journal voucher:
1. From the Financial Systems Menu (*FINANCE), select the General Ledger System
Menu (*FINGENLL).
2. From the General Ledger System Menu, select the General Accounting Transaction
Forms Menu (*FINGENLA).

3. From the General Accounting Transaction Forms Menu, select the Automatic Journal
Voucher Form (FGAAUTO). When you access this form, the cursor appears in the Automatic Journal ID field. If you wish to query information for an existing automatic journal, execute a Dynamic Query with the desired values (select Enter Query, then Execute Query). To create a new automatic journal, enter the ID of the automatic journal and a description in the Title field. You may click Automatic Journal ID or select List.
4. After entry of the automatic journal description in the Title field, use the drop-down
lists to populate the Submission Cycle field. The submission cycle controls how often the system submits a particular automatic journal. The submission cycle can be Monthly, Quarterly, Annual, or On Demand. Schedule submissions based on the selected cycle by a combination of the day and the period.
4.1.
If you select Monthly or On Demand submission cycles, the day would need to be either 1 through 31 or L for the last day of the month (that is, the first or last day of the month) and do not populate the Period field.
November 2010
2-57
4.2.
If you select Quarterly or Annual submission cycles, populate both the Submission Day and Period fields. When specifying a Period, take note that the system bases the period value on a calendar year and not the fiscal year. An example would be defining a schedule using a Quarterly cycle, populate the Submission Day field with the 15th of the month and the period value to 03 with a First/Next Submission date of 15OCT-95. When the system processes this submission, the system populates the Next Submission date field with 15-MAR-96 because the 15th day of the 3rd period of the calendar year is the 15th of March 1996. Consider this when using Quarterly or Annual submission cycles for your Automatic Journal Processes.
5. Enter the desired submission cycle and the appropriate information for the day and
period in the respective fields. The system updates the Last Submission field after the last submission processes.
6. Go to the Submissions Total field. Enter the total number of times the system must
submit the journal voucher to the Posting Process (FGRACTG) for recording in the ledgers. For example, if you selected a Monthly submission cycle and you wanted an entry each month, you would enter 12 in the Submissions Total field. Once the Submissions Total equals the Submissions Completed, run the Transaction Interface process to automatically delete the Automatic Journal ID along with all journal voucher header and detail records associated with the Automatic Journal ID. The system increments the Submissions Completed and Submissions Remaining fields after journal submission and completion. You cannot modify these fields.
7. Establish the date for submission by entering a date into the First/Next Submission
field. This date determines when the system processes the automatic journal. The system updates the Last Submission and Last Reversal fields when the automatic journals successfully process. For On Demand, Monthly, and Quarterly submission cycles, the system enters the next submission after the first using the date of successful posting for the first submission. Therefore, if there are problems posting the document on the submission day that results in posting after the submission date, you will need to adjust the submission schedule to the cycle originally specified.
8. In the Reversal field, indicate whether you want the system to reverse the automatic
journal by checking or unchecking the box. If you choose reversals, enter the Day of the reversal and the Period based on the selected submission cycle. The criteria used to populate these fields are the same as when you establish a submission schedule. To illustrate when a reversal would take place, use the previous example of a Quarterly submission with the Next Submission date of 15-MAR-96. If you enter a reversal schedule for Day 01 and Period 04, the reversal date the system uses for processing is 01-APR-96. This date is the transaction date for posting to the ledgers. After choosing reversal processing and completing the schedule information as appropriate, select Next Block to go to the Journal Voucher Header information.
2-58
November 2010
9. Enter the journal voucher Document number, Description, and Document Total.
Use a unique identifying number for the journal that is different from the sequence of numbers that you would normally use for journal vouchers. If you use a number with the sequence type normally used for journal vouchers, type NEXT in the Document field. Due to the internal system sequencing, problems occur when you subsequently enter journals. The document number used is reusable. Each submission has the same document number. The system assigns a submission number for each journal processing providing a unique internal index.
Note The Status field displays the status of the individual journal vouchers associated with the automatic journal voucher. Incomplete journal vouchers need to be addressed via FGAJVCD before the next submission can run. 10. After entering the Journal Voucher Header information, click the Journal Voucher
button or select Journal Voucher from the Options Menu. The system creates a header record and opens the Journal Voucher Entry Form (FGAJVCD). Enter the transactions needed to process this document through the accounting system.
11. The system processes transactions through the internal edits. When the information is
complete, select Complete from the Options menu to indicate that this document is ready for processing as an automatic journal document. The system processes documents that process as automatic journals through the Transaction Interface Process (FGRTRNI). FGRTRNI determines which automatic journals to read based on the next submission date on the Automatic Journal Voucher Table (FGBAUTO). The system processes documents through the Edits and the Available Balance Process where appropriate. If the system encounters errors in the journals during processing, the system writes the errors to the Batch Transaction Error Report Table (FGRTRNR).
12. The Transaction Error Report (FGRTRNR) processes the errors and prints a listing.
Approve the error-free documents. To approve documents, you must navigate to the User Approval Form (FOAUAPP) or to the Document Approval Form (FOAAINP).
13. The system calculates the next submission date for the automatic journal and updates
the Automatic Journal Voucher Table (FGBAUTO) with the next submission date, the last submission date, and the submissions to date.
Rule Code Balancing Methods

Rule Code Balancing Methods provide the ability to edit budget entries, ensure that budget entries are balanced, and maintain the ability to use plus (+) and minus (-) symbols. Method Codes provide the ability to check that pluses (+) equal minuses (-) in all transactions where you can name both sides of the transaction and specify the rule class code on input.
November 2010
2-59
You can edit budget entries in the Journal Voucher Entry Form (FGAJVCD), the Journal Voucher Quick Form (FGAJVCQ), the Journal Voucher Mass Entry Form (FGAJVCM) and the Transaction Interface Process (FGRTRNI). The specific method codes are listed in the following chart.:
Method Code Value
Balance Method Parameters
The sum of pluses (+) equal minuses (-) within Organization (ORGN), within rule class codes (RUCL) on input The sum of pluses (+) equal minuses (-) within Fund (FUND), within rule class codes (RUCL) on input The sum of pluses (+) equal minuses (-) within Chart (COAS), within rule class codes (RUCL) on input The sum of pluses (+) equal minuses (-) in total, within rule class codes (RUCL) on input
U A E
The budget entry rule class codes general design include I routines that use pluses (+) and minuses (-) and are established as self-balancing. This design is consistent with the nature of the Operating Ledger. Use the Balancing Methods feature to edit and balance budget rule class codes that use the plus (+) and minus (-) symbols within organization or fund or chart of accounts.
Tip Although balancing edits are intended for use with budget entries, you can use balancing edits with any rule class codes designed to be two-sided.
Use plus (+) and minus (-) symbols as intended for use on transaction forms established for such entries. These balancing methods are applicable to input on data only. This means, for example, that if a rule class is designed to edit that pluses equal minuses within an organization, then this edit is applied to the organization codes on input. The system does not apply the edit automatically to any posting process codes embedded in the rule class code and subsequently performed during the Posting Process (FGRACTG).
Processing a Cash Receipt From a Vendor

When cash is received from a vendor, you can use the Direct Cash Receipt Form (FGADCSR) to process the transaction. This form can also be used for processing regular cash receipts that do not come from a vendor. The rule class code or journal type does not need to be entered on this form. The Direct Cash Receipt Form generates a rule class to process the cash receipts.
2-60
November 2010
Using the Direct Cash Receipt Form

To use FGADCSR, perform the following steps:
1. Enter a cash receipt document number in the Document Number field.
Leave this field blank or enter NEXT to allow the system to automatically generate a document number.
2. Enter a vendor code in the Vendor Code field to process cash receipts from a vendor,
or you can leave this field blank. The Vendor description defaults from the Vendor Code.
3. The system date defaults in the Transaction Date field, but you may override the
date.
4. Enter the sum of all the accounting sequences that you will enter in the Document
Total field. If a vendor code is entered in the Vendor field, a default value will display in the Collects Tax field.
5. To perform Non-Sufficient Funds checking online, check the NSF Checking box.
A Y is displayed in the Document Text Exists field if text exists on the General Text Entry Form (FOATEXT). The Document Status field displays a C if the document is complete or an I if the document is incomplete. If the document is complete, you cannot use the Next Block function or navigate to the transaction detail block.
6. If you wish to enter text for the document, click the Document Text button. 7. Select Next Block or click the Transaction Detail button to go to the Transaction
Detail Window. The system updates the Status indicator after you save each transaction record. You may receive one of the following values in the Status field: If E is displayed, this indicates that an error condition has occurred due to an edit failure. If N is displayed, this indicates that there are non-sufficient funds for the transaction to proceed. If P is displayed, this indicates that this document may be posted.
8. Either enter a sequence number or let the system increment a sequence number in the
Sequence field.
November 2010
2-61
9. If the vendor refunds involve taxes, enter the appropriate tax group in the Tax Group
field. If taxes are not involved, you can leave the Tax Group field blank.
10. Enter the accounting distribution starting from the COA (Chart of Accounts) field
(defaults from your user profile). You may not enter a value in the Fiscal Year field; the fiscal year is updated by the form based on the transaction date entered.
11. Enter the percentage in the Percent field or the dollar amount in the Amount field
that applies to the accounting distribution. If you enter a value in the Percent field, then the transaction amount will default in the Amount field. If the tax group is entered, the amount you enter includes taxes if the vendor collects All or Selected taxes. These values will default from the vendor. If the vendor collects All taxes, the system will perform a reverse calculation to separate the Tax Amount and Rebate Amount (if applicable) based on the tax group. If the vendor collects Selected taxes, you must enter the Tax Amount in the Tax Information Window and the system will calculate the Rebate Amount (if applicable). If the vendor collects No taxes, the system will calculate the Tax Amount and Rebate Amount based on the total amount of the cash receipt.
12. Enter a + in the DC indicator field to process a cash receipt, or enter a - in this field to
cancel a cash receipt.

13. If you have NSF Override authority, check NSF Override and select Save. Saving
approves the NSF condition. The Description field defaults.

14. Enter a value in the Bank field.
The Deposit Number and Document Reference Number are not required fields.
15. A value defaults from the vendor information in the Currency field, but you may
override this value.

16. If a tax group is entered, you can navigate to the Tax Information Window to view the
Tax Amount and the Rebate Amount that are related to that sequence. If the vendor you enter collects Selected taxes, enter the Tax Amount in this window. You can only update the Tax Information Window if the vendor collects Selected taxes.
2-62
November 2010
17. You can also navigate to the Direct Cash Receipt Summary Form (FGICSUM) to
view all the sequences for that document.

Note The system performs available balance logic if an expense account and tax group are entered. 18. Print the document by clicking the Print Cash Receipt button.
Once you click this button, the system brings you to the Process Submission Control Form (GJAPCTL) to run the Cash Receipts Report (FGRCSRP).
19. Select Next Record to enter more sequences, or select Next Block to complete the
document.
Posting Direct Cash Receipts

Select Next Block from the main window of FGADCSR to navigate to the Transaction Detail window. On the Transaction Detail window, click the Completion button to take you to the Completion window. When you click Complete on the Completion window, the system balances the document. The system checks if the amount of all the sequences adds up to the document total. If the approvals are ON, the document is forwarded to the approval process. Otherwise, the document is forwarded to the posting process. Because rule classes are not entered on the Direct Cash Receipt Form, the form generates the DCSR rule class to process the cash receipt and TAXR to remove the tax liability (if the vendor does not collect taxes). The posting process generates the rule class RBTR to remove the rebates (if applicable). See the following example for actual postings.
Examples:
The vendor refunds $100, which includes taxes from the tax group code TGRP. The tax group TGRP has two rates: TR1 with 5% and TR2 with 10%. The priority code for both the rates is 1. Scenario 1: The vendor does not collect taxes. To record the cash received from the vendor, use rule class DCSR. Appropriate bank fund entries are made.
DR CR
$100 $100
Cash Interfund Expenditure Control Account (the input account for that sequence)
To remove the taxes from the liability account if the vendor does not collect taxes, use rule class TAXR. Tax amount = 100(15/100)
November 2010
2-63
DR CR
$15 $15
Tax Liability Expenditure Control Account (the input account for that sequence)
If TR2 had a rebate and the rebate was 70% based on the FOAPAL entered, use rule class RBTR to remove the rebates from the rebate receivable account. The rebate receivable account and the tax liability account are fetched from the tax rates that belong to the tax group that was entered on the sequence.
DR CR
$7 $7
Expenditure control account (the input account for that sequence) Rebate Receivable
Scenario 2: The vendor collects taxes. To record the cash received from the vendor, use rule class DCSR. Appropriate bank fund entries are made.
DR CR
$100 $100
To remove the rebates from the rebate receivable account, use rule class RBTR.
DR CR
$6.09 $6.09
Expenditure control account (the input account for that sequence) Rebate Receivable
Scenario 3: The tax group is null, so there is only one posting. To record the cash received from the vendor, use the rule class DCSR. Appropriate bank fund entries are made.
DR CR
$100 $100
Defaulting Feature in General Accounting Transaction Forms

Defaulting logic applies to all accounting forms. The following General Accounting Transaction forms contain the defaulting feature:
2-64
November 2010
Journal Voucher Entry Form (FGAJVCD) Journal Voucher Mass Entry Form (FGAJVCM) Journal Voucher Quick Form (FGAJVCQ) Encumbrance/Reservations Maintenance Form (FGAENCB)
Using the Defaulting Feature

The defaulting capability of Banner Finance provides more effective data entry by allowing you to set default values for funds and organizations in the process of establishing the Chart of Accounts. Enter the default Organization, Program, Activity, and Location codes using the Fund Code Maintenance Form (FTMFUND). Enter the default Fund, Program, Activity, and Location codes using the Organization Maintenance Form (FTMORGN). Once these records exist on the Chart of Accounts, the system defaults these values whenever you enter the account distribution. Populate the Default Override field on the Fund Type Maintenance Form (FTMFTYP) to invoke the defaulting feature. Use the drop-down list to select Fund or Organization for the Default Override field. Generally, you populate Restricted type funds to Fund for defaulting purposes and Unrestricted type funds to Organization. The forms work as follows when you enter an account distribution. Select Next Item from the Fund code field and enter an Organization code. When you select Next Item, Fund code, Program code, Activity, and Location values default from FTMORGN. Enter a Fund code on FTMFTYP and select Fund in the Default Override field. Select Next Item and the default Organization code is displayed. When you accept the Organization default by selecting Next Item, the Program, Activity, and Location codes default from FTMFUND. Enter a Fund code on FTMFTYP and select Fund in the Default Override field. You enter only the Organization code as a default value on the Fund Code Maintenance Form (FTMFUND). FTMFUND supplies the Organization Code. The Program, Activity, and Location default from FTMORGN if originally defined. You always have the option to override defaults.
Redefaulting FOAPAL Elements

All the transaction entry forms in Banner Finance support FOAPAL (fund, organization, account, program, activity, location) redefaulting. Defaults defined on either the fund, the
November 2010
2-65
organization, or the account index records display on entry forms when you enter a value that should trigger a default. This feature is most useful if you have defined defaults.
Where to Define Defaults

Define FOAPAL default components on the following forms: On the Fund Maintenance Form (FTMFUND), you may default the organization, program, activity, and location. On the Organization Maintenance Form (FTMORGN), you may default the fund, program, activity, and location. On the Account Index Form (FTMACCI), you may default all components of fund, organization, account, program, activity, and location.
How Redefaulting Works

The following steps show how redefaulting works:
1. Organization, Program, Activity, or Location codes (which have already been defined
on the Fund record) are defaulted as you navigate out of the Fund Code field.
2. The system checks the Fund Type of the Fund Code entered for its Default Override
field.
3. If an Organization is entered which contains default values, the system uses the
Default Override Indicator to determine what Program, Activity, and Location code it should default. The system has to determine if it should select one of the codes from the Fund record or the Organization record. If you leave the Fund code field blank and enter the Organization code, the system defaults the Fund from the Organization record if a fund was specified on the Organization record.
4. Defaulting takes place from left to right (as with most Banner data entry forms) and
from top to bottom in the Budget Development Forms (FBABDRQ and FBABDRA). So, if a value is entered in the Fund Code field and you enter an organization code which contains a default fund, the system will not override the initial Fund code entered.
Account Indexes
Account Index defaults may be defined as overridable or not overridable. If default values are overridable, you may change the value but no further redefaulting occurs from that changed value. If default values of an index are not overridable, the system provides a message indicating that the field you are attempting to change can not be updated.
2-66
November 2010
The account index defaults all values, including null values. Redefaulting does not occur when an account index is present. The following scenario serves as an example: (1) You define an index to include a fund code, an organization code, and a program code which are overridable, but no activity code or location code, (2) You change the fund code to one which contains an activity code default. The system does not default the activity code if the account index code is valued.
How Banner Finance Handles Defaults

You can define a default (such as program code) on both a fund and an organization record, and enter this combination of fund and organization on a transaction entry form. In this case, the system determines which component of fund or organization takes precedence in defaulting the program based on the Default Override value selected on the Fund Type Maintenance Form (FTMFTYP). If you have not defined defaults and you change the value of organization code, the system completely clears the values of program, activity, and location. You need to re-enter the program, activity, and location. This feature prevents you from entering improper combinations of FOAPAL values. The system clears and defaults default capable FOAPAL components to the right of the component being changed, as shown in the following chart. The system does not clear FOAPAL data to the left of the component being changed. The system clears and redefaults FOAPAL values only when you change a FOAPAL component that can initiate a default.
fund
organization
account
program
activity
location
The system clears the account code only for changes to the account index code, as the account code is only defaultable from index. Changes to the fund code clear the organization, the program, the activity, and the location. Changes to organization clear the program, the activity, and the location.
Forms Affected by the Redefaulting Feature

In the following list, forms marked with an asterisk (*) are displayed only if you have the Banner Human Resources System installed. Forms marked with a pound sign (#) are displayed only if you have the Banner Student System installed. Invoice/Credit Memo Form (FAAINVE) Budget Maintenance Form (FBABDMN) Budget Request by Account Form (FBABDRA) Budget Request Entry Form (FBABDRQ)
November 2010
2-67
Encumbrance/Reservations Maintenance Form (FGAENCB) Journal Voucher Entry Form (FGAJVCD) Journal Voucher Mass Entry Form (FGAJVCM) Journal Voucher Quick Form (FGAJVCQ) Change Order Form (FPACHAR) Purchase Order Form (FPAPURR) Requisition Form (FPAREQN) Employee Job Form (NBAJOBS) Position Definition Form (NBAPOSN) Benefit/Deduction Rule Form (PTRBDCA)* Earnings Code Rule Form (PTREARN)* Detail Code Control Form (TFADETC) Detail Code Control Form (TSADETC)# Miscellaneous Transaction Form (TSAMISC)#
Making Adjustments to an Existing Encumbrance

Follow this procedure to adjust committed or uncommitted encumbrances.
1. Open the Encumbrance/Reservations Maintenance Form (FGAENCB). 2. Enter the Encumbrance Number to be adjusted. You may only adjust encumbrances
that have posted successfully to the ledgers.

3. Select Next Block to enter the Encumbrance Header Information. 4. The Encumbrance Title is not a required field; you may bypass it. 5. Enter the encumbrance dollar adjustment amount (amount to change the encumbrance
BY) in the Document Total field. If you want to increase the encumbrance to $3600.00 from $3500.00, enter 100.00 in the Document Total field. For example: Original encumbrance amount Adjusted amount Transaction amount $3500.00 $100.00+ $100.00
6. Choose the radio button that corresponds to the desired Encumbrance Type:
Encumbrance, Labor, or Memo.
2-68
November 2010
7. Enter the associated vendor data. 8. Enter from one to eight characters in the Encumbrance Change field to uniquely
identify this document as a change to an existing encumbrance. The encumbrance change number is key to the posted document.When the system posts the document, the encumbrance change number serves as the document number.
9. Select Next Block to access the Transaction Detail Window.
Transaction Detail Data

As you enter adjustment amounts, FGAENCB maintains the document total accordingly. The system adjusts the encumbrance value by that amount when the Posting Process executes. You can delete header or detail records only if the system has not posted the encumbrance record to the ledgers.
1. Enter the adjustment amount for this accounting distribution in the Current
Encumbrance Amount field.

2. When you adjust an original encumbrance, you must specify Rule Class E020 in the
Journal Type field. E020 is the Encumbrance Adjustment Rule Class. Banner Finance includes process codes within the Rule Class used by the Posting Process to handle an adjustment.
3. FGAENCB tracks the amounts you enter in the Net Amount field. 4. Select Next Record to proceed to any subsequent distributions.
After you enter the adjustment amount, the Amount field is blank and the adjustment displays in the Current Encumbrance Amount field. Use this method to handle any corrections/updates to the transaction amounts before you complete and approve adjusted encumbrances. The system clears the transaction amount from the form and performs the required adjustment on the value in the Current Encumbrance Amount field.
5. The Document Total field contains the adjusted encumbrance amount. In the
previous example, the amount that displays is $3600.00.

6. For committed and uncommitted encumbrances, select Committed from the Commit
Type drop-down list. Select Next Block.
Completing the Encumbrance

After the system performs the encumbrance adjustments, click Complete or select Complete from the Options menu to complete the document and execute posting
November 2010
2-69
according to site requirements. Subsequent changes to the document may not occur until posting is complete. Once you begin to process an adjustment, you cannot reference the associated document number on a subsequent document (such as an invoice) until the system completes, approves, and posts the changes successfully. When you supply an incorrect Rule Class, FGAENCB displays the Transaction Verification Form with your Document Number in the Key Information and error messages in the Error Messages Information. You can process changes to existing encumbrances with the approvals process on. The following is a sample error message: Encumbrance must exist in prior year to be changed to committed.
Net Total Fields on General Accounting Query Forms

Totals display on the Organization Budget Status Form (FGIBDST) and the Executive Summary Form (FGIBDSR). In addition, the one-character Account Type field displays a value representing the type of account displayed on these forms. The Account Type field contains one of the four OPAL account type values:
R L E T
Revenue type accounts Labor type accounts Expenditure type accounts Transfer type accounts
Calculating Totals
When you enter the key components and the system performs a relative query (Query Specific Account box is unchecked), the form calculates the net totals as follows: Revenue - (Labor + Expense + Transfer) FGIBDSR and FGIBDST calculate the Net Total for each of the Detail Information columns: Adjusted Budget, YTD (Year-to-Date) Activity, and budget Commitments. The form does not display a Net Total for the Available Balance column since it does not provide meaningful information for relative queries. When you enter the Key Information components and the system performs a selective query (Query Specific Account box is checked), FGIBDSR or FGIBDST displays the account codes that have activity inclusive to that account type. The Net Totals are a sum of the values displayed and not a calculation. The Available Balance total displays for selective queries.
2-70
November 2010
Example 1:
Enter a valid Chart, Fiscal Year, Organization, and Fund and perform the query. The system displays all account codes with activity within the Key Information components specified. Next to each account code, the value of R, L, E, or T defaults in the Account Type field. The Net Totals for Adjusted Budget, YTD Activity, and budget Commitments are the result of the following computation: Revenue - (Labor + Expense + Transfer) These totals coincide with the values displayed on the Organization Summary Form (FGIBSUM).
Example 2:
Enter a valid Chart, Fiscal Year, Organization, Fund, and an Expenditure Account Type and perform the query. The system displays all account codes with activity within the Key Information components specified. An E displays in the Account Type field and the totals for Adjusted Budget, YTD Activity, budget Commitments, and Available Balance are the sum of the values displayed. FGIBDSR and FGIBDST compute the Net Totals as R - (L + E + T) any time the Query Specific Account box is unchecked. The totals are the sum or absolute amount when the Query Specific Account box is checked.The Net Total fields display the sum of all the records queried. You cannot query on the Account Type field since it is not a database field. Although FGIBDSR and FGIBDST are similar in appearance, keep in mind that FGIBDSR allows for queries at higher level chart components. FGIBDST will not return values for higher level components within the chart hierarchy. The forms return records only if detail exists for the values entered.
Year-End Processes
The Banner Finance Year-End feature incorporates five distinct processes that you schedule using the Year End Ledger Maintenance Form (FGAYRLM). Because the Banner Finance System lets you keep two fiscal years and multiple accounting periods open simultaneously, you do not need to schedule these processes precisely on the calendar dates that define the fiscal year. The first process rolls the General Ledger balances forward into the new fiscal year and opens the accrual period in the prior fiscal year.
November 2010
2-71
The second process rolls the specified open encumbrances forward into the new fiscal year. The third process rolls the specified remaining budget into the new fiscal year. The fourth process closes all the operating control accounts in the General Ledger in the prior fiscal year. The fifth process can be run any time after the last day of the old fiscal year and is not dependent on any other Banner Finance year-end process. This process: Closes current HR labor encumbrances in the current fiscal year Rolls forward open future multiple year HR labor encumbrances into the new fiscal year Closes rolled HR labor encumbrances in the new fiscal year.
Scheduling Year-End Maintenance

1. Open the Year-End Ledger Maintenance Form (FGAYRLM). 2. Enter the Chart of Accounts and Fiscal Year you wish to close. A button and List
are available in both fields. Select Next Block.

3. Enter the Scheduled Date in the appropriate fields for each category of activity:
Balance Forward, Roll Encumbrances, Budget Carry Forward, and Close Operating Accounts.
4. Enter a user-defined document number in the Starting Document Number field. The
first four characters of each document number should be unique for each year-end process. The last four characters must be numeric. The entered document code will be the first code used when creating transactions in the selected year-end process. Each process must have its own start document number. Make sure you use unique document numbers for each Chart of Accounts.
5. Enter the date that each process is scheduled to run in the Scheduled Date field.
Report processing updates the Ending Document Number field with the last document code used. The system defaults the Performed Date when each of the relevant processes executes.
Rolling the General Ledger Balances and Opening the Accrual Period
Verify that prior and current fiscal year records exist on the System Control Fiscal Year Set-Up Form (FTMFSYR). If, for example, your fiscal year calendar is July 1 - June 30 and the current date is July 8, 1996, the prior fiscal year is 96 and the current fiscal year is 97. The Accrual Period for
2-72
November 2010
both fiscal years should be Not Opened. Open accounting Period 01 in the current fiscal year. Depending on how you wish to handle prior year activity, you have two options with the prior year fiscal year record. Once the General Ledger balances have rolled into the current fiscal year, the accrual period will be open on the prior fiscal year record. As you make adjustments and entries associated with the prior fiscal year, you will use a transaction date from the last fiscal period of the prior year. If you close the last fiscal period, the transaction automatically posts to Period 14, or the accrual period. If you leave the last fiscal period open, the same transaction will post to that period - usually period 12. Review the Chart of Accounts Maintenance Form (FTMCOAS). Verify that valid accounts are entered in the Fund Balance Account, Accounts Payable Accrual Account, and Accounts Receivable Accrual Account fields in the Parameters Window of FTMCOAS.
Executing the General Ledger Balance Forward Process

Execute the General Ledger Balance Forward Process (FGRGLRL). This process will perform the following functions: Close all prior year control account balances into the fund balance account (from the Parameters Window of the Chart of Accounts Maintenance Form, FTMCOAS) of the current fiscal year, provided the Multiple Fund Balance indicator on the System Control Maintenance Form (FOASYSC) is unchecked. Interrogate each fund record for its balance indicator (if Multiple Fund Balance is checked on the System Control Maintenance Form, FOASYSC). This indicator may equal FTYP, FUND, or ACCT. Using this indicator, the system references the appropriate fund balance account based on the values entered in the Fund Balance Account Maintenance Form (FTMFBAL). The system closes Year-to-Date control account balances to these Fund Balance Accounts. Create opening balances for the general ledger accounts in the current fiscal year (Accounting Period 00). Control Accounts do not roll in this process. Open the accrual period in the prior fiscal year (Accounting Period 14). The accrual period may remain open for as long as is necessary. Generate a hard-copy report of FGRGLRL. Refer to the Reports and Processes chapter for procedures for generating reports. Update the Date Performed field and the Ending Document Number for the G/L Roll Process on the Year-End Maintenance Table (FGBYRLM) and the Year-End Ledger Maintenance Form (FGAYRLM). Permit concurrent fiscal year processing.
November 2010
2-73
Rolling an Encumbrance
Use the Chart of Accounts Code Maintenance Form (FTMCOAS) to define the Encumbrance Roll Parameters and the parameters defining the budget policy for those encumbrances that roll forward into the next fiscal year. These parameters include: Rule Code field: Enter E090 (Year End Encumbrance Roll). Commit Type field: Enter U for uncommitted or C for committed. Uncommitted encumbrances, when rolled, do not maintain the distinction of being from the prior year. Their balances reflect in the General Ledger Encumbrance Control Account. Committed encumbrances are identified as having been rolled from the prior year. Their balances reflect in the Prior Year Encumbrance Control Account in the current year. Committed encumbrances roll only once; they do not roll a second year. Budget Roll field: Specify whether to roll the budget associated with the encumbrance. If the Commit Type is C, you must enter Y in this field. If the encumbrance is being distinguished as rolling from the prior year, it must come into the current year with its own budget. If the Commit Type is U, enter either Y or N in the Budget Roll parameter depending on internal policies. Budget Disposition field: The value in this field specifies what happens to remaining budget if you liquidate a rolled encumbrance in the current year for less than the encumbrance amount. Valid entries are U (Unrestricted), R (Restricted), or N (No Action). If the Commit Type is U (Uncommitted), the Budget Disposition field must be U (Unrestricted). When an Uncommitted encumbrance rolls from the prior year and you liquidate it for less than the encumbered amount, the remaining budget is available for use in the current year. If the Commit Type is C (Committed), the Budget Disposition can be U (Unrestricted), R (Restricted), or N (No Action). The U (Unrestricted) option works the same for a Committed encumbrance as an Uncommitted encumbrance. If the Budget Disposition is R (Restricted), any remaining amount after you liquidate a C (Committed) encumbrance is not available for the current year's use. The system reclassifies the remaining amount to an appropriate account. To take advantage of this option, establish a contingency account (typically a Fund Balance type) and enter it as a posting modifier on the INEI (Invoice with Encumbrance) rule class. If encumbrances are being rolled C (Committed), you have the option to specify N (No Action) in the Budget Disposition field. As with R (Restricted), any remaining budget dollars will not be available for use in the current year, but the dollars will remain as restricted budget for the line item rather than be reclassified to another account.
2-74
November 2010
The Percent field allows you to specify a percentage of the budget to roll with the encumbrances. When the encumbrances are being rolled C (Committed), this value must be 100%. You can populate these parameters at the Fund Type level on the Fund Type Maintenance Form (FTMFTYP). When rolling the encumbrance, the system will first look at the Fund Type record for these parameters and go to the Chart of Accounts record only if there are no parameters set at the fund type level. Use the Document Roll Parameters to specify which types of encumbrances roll at fiscal year end. Ensure that the FTVSDAT table has a record with the following: Entity/Usage Code equal to FGBTRNI Attribute Code equal to FGBTRNI_RUCL_CODE Optional Code Number 1 equal to the Encumbrance Roll Rule E090, delivered in the sample data. Data field equal to BD01 rule class to roll the associated budget for the encumbrance.
Note Once you roll an encumbrance into the current fiscal year, you may no longer process a change order or cancellation against that encumbrance in the prior fiscal year. However, you may reference it in the current fiscal year.
Make sure to enter most invoice activity that you want to record in the prior year before running this process. You may process an invoice against a rolled encumbrance in the prior fiscal year; however, that invoice will perform a total liquidation of that encumbrance at the time of posting. Execute the Roll Open Encumbrances Processes (FGRENRL). Then run the Transaction Interface Process (FGRTRNI) and the Posting Process (FGRACTG) to post the rolled encumbrances to the current fiscal year. As with the General Ledger Roll process, this process produces a hard copy report listing the encumbrances rolled. Also, it updates the Performed Date and the Ending Document Number fields on the FGBYRLM Table and FGAYRLM form for the Encumbrance Roll Process. When you run FGRENRL and there are no documents to be rolled or closed, the Ending Document Number field for the Roll Encumbrances record on the Year End Maintenance Form (FGAYRLM) will remain blank since no documents are created. The Performed
November 2010
2-75
Date field will be populated to indicate that the process completed successfully, even though no documents were created.
Note Encumbrances which have rolled as C (Committed) from the prior fiscal year will not roll into the new fiscal year if they remain open.
Rolling Prior Year Encumbrances

The Encumbrance/Reservations Maintenance Form (FGAENCB) and its related processing provide maintenance for prior-year encumbrances being rolled into the current fiscal year. The Commit Type features on FGAENCB support the Encumbrance Roll Procedure. Original encumbrances established on FGAENCB will have the encumbrance type default to Uncommitted. To convert an encumbrance from Uncommitted to Committed, you must have rolled the encumbrance forward from the prior year using the Encumbrance Roll Process (FGRENRL). Enter the encumbrance number in the Encumbrance Number field of FGAENCB, and select Next Block. You have the option of valuing the Document Total field in the conversion procedure. Enter a unique number in the Encumbrance Change field and select Next Block to access the Transaction Detail Window. Enter Rule Class E095 in the Journal Type field. This rule class has a process code associated with it for converting the encumbrance, Process Code E022. Banner Finance supplies the rule class and process code in the sample data.Process Code E022 will only execute if the encumbrance number exists in the prior year. Use the drop-down list to select a Commit Type of Committed. Select Next Record or Save. FGAENCB enforces the following rules during the conversion process: Use the E095 Rule Class during a conversion because it contains the Process Code E022. The system successfully posted the encumbrance you are converting in the prior year. The Amount field must remain NULL. You may not modify fields other than Journal Type and Commit Type. After you update all encumbrance detail records, select Complete from the options menu. Complete the document and execute the Posting Process (FGRACTG).
2-76
November 2010
After you convert a committed encumbrance, you may adjust it as an uncommitted encumbrance. FGAENCB enforces the following rules during the adjustment process: The encumbrance must have been posted to the ledgers in the current year. The E020 (Encumbrance Adjustment) Rule Class must be entered in the Journal Type field. This encumbrance cannot be converted back to Uncommitted.
Budget Carry Forward

The Budget Carry Forward parameters refer to unexpended dollars at the end of the fiscal year. Any budget which rolls will roll into the same line items in the new fiscal year. Enter these parameters on the Chart of Accounts Code Maintenance Form (FTMCOAS). Rule Code field: Enter J020 (Budget Carry Forward Journal). Budget Type field: Refers to T (Temporary) or P (Permanent) budgets. Specify T to roll temporary and permanent budgets. Specify P to roll only the permanent budgets. Budget Class field: Specify O to roll Original budget or A to roll Adjusted budget. Percent field: The system provides the flexibility to roll a percentage of the budget from 0% to 100%. You can override these roll parameters at the fund type level by defining their values on the Fund Type Maintenance Form (FTMFTYP). Execute the End-of-Year Budget Carry Forward Process (FGRBDRL). This process will produce a hard copy report and update the Date Performed and the Ending Document Number fields on the FGBYRLM table and FGAYRLM form for the Budget Roll Process. Execute this process only once. Run the Transaction Interface Process (FGRTRNI) and the Posting Process (FGRACTG) to post the transactions to the current fiscal year.
Closing Operating Control Accounts

This is the final step in the year-end closing process. The purpose of this process is to close out the control accounts in the General Ledger in the prior fiscal year to fund balance in the prior fiscal year. All control accounts but the Encumbrance Reserve Account will close to Fund Balance. If Single Fund Balance processing is in effect, the control accounts close to the fund balance account defined on the Chart record. If Multiple Fund Balance processing is in effect, Year-to-Date control accounts are closed to the fund balance accounts defined on FTMFBAL. Non-YTD Control Accounts close to the fund balance account defined on the Chart record.
November 2010
2-77
Make sure that there is a system ID for the job. The sample data provides 'GLCLOSE' on the System Data Validation Table (FTVSDAT) as the system ID. The Close Operating Accounts Process (FGRCLOP) executes only if the following conditions exist: All prior-year fiscal periods are closed. The accrual period for the prior fiscal year on the System Control Fiscal Year SetUp Form (FTMFSYR) is open. The other three year-end processes have run successfully. Execute the Close Operating Accounts Process (FGRCLOP). Run the Transaction Interface Process (FGRTRNI) and the Posting Process (FGRACTG) to post the transactions. Once FGRACTG executes and the system posts the transactions, you can close the accrual period for the prior fiscal year on the Fiscal Year Maintenance Form (FTMFSYR). You have now completely closed the prior year. The year-end processes are as follows: General Ledger Balance Forward Process (FGRGLRL) Encumbrance Carry Forward Roll Process (FGRENRL) End-of-Year Budget Carry Forward Process (FGRBDRL) Close Operating Accounts Process (FGRCLOP) Roll HR Labor Encumbrances Process (FGRLENC)
Year-end Processing Checklist

The following is a quick reference to the Year-end Process.
1. FTMCOAS: Do the Encumbrance, Budget Carry Forward, and Document Roll
Parameters on FTMCOAS accurately reflect your site policies?

2. FTMCOAS: Do you have a valid Fund Balance Account entered on FTMCOAS? 3. FTMCOAS: The system requires that your Chart of Accounts effective date must be
in effect before the year-end jobs are scheduled on the Year End Ledger Maintenance Form (FGAYRLM).
4. FTMACTL: If you are planning to roll any of your encumbrances as C (Committed),
make sure that the appropriate Prior Year accounts exist.

5. FTMSDAT: There must be valid System ID entries for the Encumbrance Roll
(ENCROLL), the Budget Carry Forward (BDGTFRWD), and the General Ledger Close (GLCLOSE) processes. There must also be an entry specifying E090 as the FGBTRNI_RUCL_CODE for FGBTRNI.
2-78
November 2010
6. FTMFSYR: You must set up your new fiscal year. If you have not already done so, at
least the first fiscal period must be open. Also, make sure that Accrual Prd (Period) in both the current and future fiscal years is Not Opened.
7. FGAYRLM: Schedule your year-end jobs. Run these jobs in the order in which they
appear on the form. The first four characters of the document number must be unique. You must distinguish document numbers for each Chart of Accounts for which you will be running the jobs. You do not need to run any of the year-end jobs to begin processing in the new year. Perform the following steps:
7.1.
Run the Balance Forward Process (FGRGLRL). This rolls the General Ledger account balances forward into the new fiscal year. The Control Accounts from the prior year close to the Fund Balance accounts in the new fiscal year. This opens the Accrual Period. Each of the following processes insert records into the Transaction Interface Table (FGBTRNI). Therefore, after each process, you must run the Transaction Interface Process (FGRTRNI) to edit the transactions, then the Transaction Error Report (FGRTRNR) to display your errors, if any. Correct your errors and then run the Posting Process (FGRACTG) to post the transactions.
7.2.
Run the Roll Open Encumbrances Report/Process (FGRENRL). This rolls the encumbrances you specified on the Chart of Accounts record into the new fiscal year. This process updates the Encumbrance Control and related Offset Accounts in the new year. Run the Roll Remaining Budget Balance Report/Process (FGRBDRL). This rolls the remaining budget from the prior year into the new fiscal year according to the parameters defined on the Fund Type or the Chart of Accounts record. The system updates the Budget Control Accounts in the new year. (This is budget that has not already rolled in conjunction with the encumbrance roll.) Run the Close General Ledger Report/Process (FGRCLOP). This closes the Control, Fund Additions, and Fund Deductions accounts in the year prior to the Fund Balance account or accounts that you have defined with the exception of the Encumbrance Reserve Account. (Optional) - If you use multiple year encumbering, you can run the Roll HR Labor Encumbrances Process (FGRLENC). This process closes current Human Resources (HR) labor encumbrances in the current fiscal year, rolls forward open future multiple year HR labor encumbrances into the new fiscal year, and closes rolled HR labor encumbrances in the new fiscal year.
7.3.
7.4.
7.5.
8. FTMFSYR: Close the Accrual Prd (Period) in the prior fiscal year.
November 2010
2-79
Concurrent Year Processing

Once the General Ledger balances have rolled, the system will maintain general ledger balances in both the prior and current fiscal years as appropriate. Current fiscal year transactions require no special recognition other than an Open accounting period. In other words, when entering a transaction for the current fiscal year, use a transaction date in the appropriate accounting period. Prior year transactions require a date within the last fiscal period of the prior year. As stated previously, if you close the last fiscal period, the system posts these transactions to the accrual period, or Period 14. If the last fiscal period is open, the transaction will post to the last fiscal period, usually Period 12. Once you open the accrual period, you may close the last fiscal period at any time. During this period of concurrent fiscal year processing, the Posting Process (FGRACTG) updates the General Ledger balances in both fiscal years.
Note Both the Purchase Order Form (FPAPURR) and the Purchase Order Delete Form (FPAPDEL) support concurrent year processing.
OPAL Transactions in the Prior Year

Any transactions against operating ledger accounts in the prior fiscal year will update the Control Accounts in the prior fiscal year and Fund Balance in the current fiscal year. For example, a prior year invoice will update Expenditure Control and Accounts Payable in the prior year. In addition, it will update Fund Balance and Accounts Payable in the current year. Remember, since the General Ledger balances are not going to roll again, you must simultaneously update Accounts Payable in both fiscal years.
General Ledger Transactions in the Prior Year

Any adjustments to prior year general ledger balances will automatically update the same accounts in the current year opening balance.
Cash Activity in the Prior Year

Ordinarily, cash activity requires no special consideration. Typically, the system processes cash disbursements against Accounts Payable, cash receipts against Accounts Receivable in the current year. If, however, there is a need either to receive cash in the current year and credit revenue in the prior year, or to disburse cash against a prior year expenditure, there are two special rule classes provided in the sample data for this purpose: YR10 for cash disbursements and
2-80
November 2010
YR20 for cash receipts. These rule classes have special process codes to maintain cash in the current year while recognizing OPAL activity in the prior year. Use the A/P Accrual Account and A/R Accrual Account in the Parameters Window of the Chart of Accounts Maintenance Form (FTMCOAS) to balance between the two fiscal years. If you need to use either of these rules, remember that you must use a transaction date in the current fiscal year and you must check the Accrual box in the Transaction Detail Window of the Journal Voucher Entry Form (FGAJVCD). As the system processes cash receipt transactions for prior fiscal year activities, they post to the General Ledger and Operating Ledger as follows: Prior Fiscal Year General Ledger
DR CR
Year-end Accounts Receivable Accrual by fund, on input Revenue, Expenditure or Transfer Control Account by fund, on input
Prior Fiscal Year Operating Ledger
CR
Revenue, Expenditure or Transfer FOAPAL Distribution, on input
Current Fiscal Year General Ledger
DR DR CR CR
Cash in the bank fund Cash equity in the operating fund Cash equity in the bank fund Year-end Accounts Receivable Accrual by fund, on input
Current Fiscal Year Operating Ledger No entries
Cash Disbursement Activity in the Prior Year

As the system processes cash disbursement transactions for prior fiscal year activities, they post to the General Ledger and Operating Ledger as follows:
Prior Fiscal Year General Ledger
DR: Revenue, Expenditure or Transfer Control Account by fund, on input CR: Year-end Accounts Payable Accrual by fund, on input
November 2010
2-81
Prior Fiscal Year Operating Ledger
DR: Revenue, Expenditure or Transfer FOAPAL Distribution, on input

Current Fiscal Year General Ledger
DR: Year-end Accounts Payable Accrual by fund, on input DR: Cash equity in the bank fund CR: Cash in the bank fund CR: Cash equity in the operating fund
Current Fiscal Year Operating Ledger
No entries
Credit Memo in the Prior Year

To support concurrent year processing, the Invoice/Credit Memo Form (FAAINVE) prevents you from creating a Credit Memo in the prior fiscal year against an encumbrance which you have already rolled into the current fiscal year: In addition, a prior-year invoice against an encumbrance which has already rolled into the current year displays as F (Final payment).
Posting of Liquidations in the Prior Fiscal Year

The following are posting examples of liquidations in the prior fiscal year.
Encumbrance That Has Rolled Committed

Create an invoice in the prior year to liquidate an encumbrance that has already rolled into the current year. A C indicates a committed encumbrance.
Example 1:
Committed encumbrance for $200. Liquidate for full amount. Prior Year DR Expenditure Control $200 CR Accounts Payable $200 DR Encumbrance Reserve $200 CR Encumbrance Control $200
2-82
November 2010
Current Year DR Prior Year Encumbrance Reserve $200 CR Prior Year Encumbrance Control $200 For R (Restricted) or U (Unrestricted) Budget DR Prior Year Budgeted Expenditure Control $200 CR Prior Year Budgeted Change to F/B $200 DR Fund Balance $200 CR Accounts Payable $200
Example 2:
Committed encumbrance for $200. Liquidate for $150. Prior Year DR Expenditure Control $150 CR Accounts Payable $150 DR Encumbrance Reserve $200 CR Encumbrance Control $200 Current Year DR Prior Year Encumbrance Reserve $200 CR Prior Year Encumbrance Control $200 DR Prior Year Budgeted Expenditure Ctl. $200 CR Prior Year Budgeted Change to F/B $200 DR Fund Balance $150 CR Accounts Payable $150
Example 3:
Committed encumbrance for $220. Liquidate for $250. Prior Year DR Encumbrance Reserve $200 CR Encumbrance Control $200 DR Expenditure Control $250 CR Accounts Payable $250
November 2010
2-83
Current Year DR Prior Year Encumbrance Reserve $200 CR Prior Year Encumbrance Control $200 DR Prior Year Budgeted Expenditure Ctl $200 CR Prior Year Budgeted Change to F/B $200 DR Fund Balance $250 CR Accounts Payable $250
Encumbrance That Has Rolled Uncommitted

Example 1:
Uncommitted encumbrance for $200. Liquidate for full amount. Prior Year DR Expenditure Control $200 CR Accounts Payable $200 DR Encumbrance Reserve $200 CR Encumbrance Control $200 Current Year DR Encumbrance Reserve $200 CR Encumbrance Control $200 DR Budgeted Expenditure Control $200 CR Budgeted Change to F/B $200 DR Fund Balance $200 CR Accounts Payable $200
Example 2:
Uncommitted encumbrance for $200. Liquidate for $150. Prior Year DR Expenditure Control $150 CR Accounts Payable $150 DR Encumbrance Reserve $200 CR Encumbrance Control $200
2-84
November 2010
Current Year DR Encumbrance Reserve $200 CR Encumbrance Control $200 DR Budgeted Expenditure Ctl. $200 CR Budgeted Change to F/B $200 DR Fund Balance $150 CR Accounts Payable $150
Example 3:
Uncommitted encumbrance for $220. Liquidate for $250. Prior Year DR Encumbrance Reserve $200 CR Encumbrance Control $200 DR Expenditure Control $250 CR Accounts Payable $250 Current Year DR Encumbrance Reserve $200 CR Encumbrance Control $200 DR Prior Year Budgeted Expenditure Ctl $200 CR Prior Year Budgeted Change to F/B $200 DR Fund Balance $250 CR Accounts Payable $250
Creating an Original 1099

Run the following processes after December 31 of the calendar year. For those steps which require a Reporting Year, use the calendar year of each 1099 which you extract. There are no restrictions as to when you may generate a 1099, except those that the IRS imposes.
1. At calendar year end, request the 1099 Report/Withhold Audit Report (FARWHLY). 2. Verify each vendor's distributions to determine if the amounts are correct and whether
you should create a 1099 for the vendor. If you find errors for a vendor, such as Non-employee Compensation that you distributed to Rents, you can use the 1099 Reporting Form (FAA1099) to correct the error. You can also enter additional data. If this vendor has no previous 1099 data, you can enter the data for the vendors 1099 on this form.
November 2010
2-85
3. Enter Transmitter and Institution (Payer) information on the 1099-MISC Magnetic
Tape Transmitter Data Form (FOA1099).

4. Request the Magnetic 1099 File Build (FAM1099) to create the 1099 Tape Summary
Audit Report and irs1099.dat file. You can use the audit report to supply the number of payees and amount distribution information that the IRS 4804 form requires. Leave the Correction Indicator, Test Correction Indicator, and Correction Date fields blank.
5. The irs1099.dat file can be uploaded directly to the IRS. (See IRS publication 1220
for further instructions.) Leave the File Type parameter blank to create a data file that has a carriage return at the end of each 750-character record. Enter LS in the File Type parameter to create a continuous stream of data to be copied to tape.
6. Create the 1099 forms by running the 1099 Forms Test Patterns (FAT1099) and the
1099 Forms Report (FAB1099). To verify a 1099, you can compare each 1099 to the 1099 Reporting/Withholding Audit Verification Report. Refer to the Reports and Processes chapter for more information.
Creating a Correction 1099

Run these processes after the date of December 31. For those steps that require a Reporting Year, use the calendar year of each 1099 that you extract. There are no restrictions as to when you may create a Correction 1099, outside of those that the IRS imposes. If you find errors after you send the original 1099 tape and forms to the IRS, you must resend the corrected 1099 as a separate run. To do this, use the 1099 Reporting Form (FAA1099) to correct the errors. Both the 1099 Magnetic Tape File Build (FAM1099) and the 1099 Forms Print (FAB1099) processes use the date on which you make these corrections the Correction As of Date.
1. Request the Magnetic 1099 File Build (FAM1099) to create the 1099 Tape Summary
Audit Report. You can use the audit report to supply the number of payees and amount distribution information that the IRS 4804 form requires.
2. Enter C for the Correction Indicator parameter, C for the Test Correction
Indicator parameter, and the earliest date on which you made corrections for the Correction Date parameter. The correction date ensures that the system does not include vendors who do not have corrections.
3. Use your site process to create the 1099 tape, or use your site upload facility to upload
this file directly to the IRS (see IRS publication 1220 for further instructions).
2-86
November 2010
4. Create the 1099 forms by running the 1099 Forms Test Patterns (FAT1099) and the
1099 Forms Report (FAB1099). Enter the earliest date on which you made corrections for the Correction Date parameter. The correction date ensures that the system does not use vendors who do not have corrections.
Querying Accounting Data

The General Accounting Query forms enable you to review the accounting data resulting from journal voucher, requisition, purchase order, invoice, and check transactions. These forms always reflect the latest run of the Posting Process (FGRACTG).
Organization Budget Status Form (FGIBDST)

FGIBDST shows detailed OPAL activity. The Chart (of Accounts) and Fiscal Year are required fields. Use the Query Specific Account check box to determine which type of account query will be executed. Uncheck this check box and enter the desired combination of Organization, Fund, Account, Program, Activity, or Location (FOAPAL values) to query a range of accounts. Check this check box and enter the desired combination of Organization, Fund, Account, Account Type, Program, Activity, or Location (FOAPAL values) to query a specific account. Select Next Block to execute the query and display the accounting detail. To query further, place the cursor on the relevant field and select List. This takes you to the Detail Transaction Activity Form (FGITRND). Select List to return to the document that created the transaction originally. Select Next Block to display the accounting distribution.
Executive Summary Form (FGIBDSR)

This form provides a query of operating ledger budget and activity data organized by account. The Chart (of Accounts) and Fiscal Year are required fields. Use the Query Specific Account check box to determine which type of account query will be executed. Uncheck this check box and enter the desired combination of Organization, Fund, Account, Program, Activity, or Location (FOAPAL values) to query a range of accounts.
November 2010
2-87
Check this check box and enter the desired combination of Organization, Fund, Account, Account Type, Program, Activity, or Location (FOAPAL values) to query a specific account. Select Next Block to execute the query and display the accounting detail. To query further, place the cursor on the relevant field. List takes you to the Detail Transaction Activity Form (FGITRND). Select List again to take you to the document that created the transaction originally. Select Next Block to display the accounting distribution. FGIBDSR enables you to view the roll up of OPAL accounting activity. Unlike FGIBDST, FGIBDSR allows you to enter a high level combination of fund, organization, account, program (FOAPAL values) and view all activity within that hierarchy. This form is called Executive Summary because it is useful for those who want to review aggregate numbers rather than analyze specific accounting transactions.
Account Type Query on FGIBDST and FGIBDSR

The Organization Budget Status Form (FGIBDST) and Executive Summary Form (FGIBDSR) provide query capability by account type along with the other FOAPAL elements. FGIBDST and FGIBDSR display the Account Type and Description next to the Account field in the Key Information. Querying by account type will return data for all accounts with that account type. On FGIBDST, you may query by account type alone or refine your query with a combination of Account and Account Type. Check the Query Specific Account box to optimize the query performance of these forms when you use account code in your query criteria. The query option applies to either account type or account code. You may leave either field blank. You can query at a Level One Account Type and see all accounts with account types at subordinate levels. FGIBDSR retrieves the data and places it in collector tables to summarize. For this reason, you cannot query a combination of account type and account code simultaneously. As with FGIBDST, unchecking the Query Specific Account box is not meaningful if the Account Type is entered. When you query on account type, the Query Specific Account box automatically defaults to checked on FGIBDSR. Refer to the Reports and Processes chapter for related General Ledger Reports.
Performing a Query for Specific Date

Searching for a specific date can be accomplished in certain Banner Finance query and maintenance forms by entering the date following by the percent sign (%). The % is necessary to find all records whose dates match the entered date criteria and for all times within that date. As entries are processed through the system or as accounting (FOAPAL)
2-88
November 2010
elements are changed, they are both dated and time stamped. Omitting the % sign following the date causes the system to query the tables for entries which are dated and have a null time stamp. Since entries without a timestamp do not exist, the following message may be returned: Query caused no records to be retrieved The Banner Finance fields that may require this search format are Effective, Termination, Transaction, and/or Activity dates. These dates include a time stamp (i.e., the current time) which is necessary to ensure that the correct records are used when two or more change records of a given type are created in the same day.
Example:
If you are searching for all transaction activity records dated 20-JUL-2009 on the Detail Transaction Activity Form (FGITRND), you would enter the date in the following format: 20-JUL-2009% This search returns all records with this date.
Formatting Preferences on Query Forms

You can change the way Banner displays amounts on the following query forms. Budget Availability Status Form (FGIBAVL) Executive Summary Form (FGIBDSR) Organization Budget Status Form (FGIBDST) Organization Budget Summary Form (FGISUM) General Ledger Trial Balance Form (FGITBAL) Trial Balance Summary Form (FGITBSR) Detail Transaction Activity Form (FGITRND) Grant Inception To Date Form (FRIGITD) Grant Transaction Detail Form (FRIGTRD) Archive--Detail Transaction Activity Form (FXITRND)
November 2010
2-89
By default, Banner displays values using three significant commas and two significant decimal places. Use the following procedure to change the way in which Banner displays values on a form.
1. Access one of the ten query forms in the preceding list. 2. Click on Format Display Preferences. Banner will display the Format Display
Preferences window.
3. (Optional) Change the selected value in the Significant Commas radio group. 4. (Optional) Change the selected value in the Significant Decimal Digits radio group. 5. Click Apply. 6. Click Close.
Research Accounting
Proposal Setup
Use the following steps to set up a proposal in the Research Accounting module.These steps are guidelines and can change according to site policies and procedures .
Step Form Action
Identification Form (FOAIDEN) Agency Code Maintenance Form (FTMAGCY)
Identify proposal accounts, proposal administrators, and principal investigators to Banner Finance as persons. Establish the funding agency codes, contacts, addresses, phone numbers, and so on.
2 3
Financial Manager Maintenance Establish financial managers, proposal Form (FTMFMGR) accounts, proposal administrators, principal investigators, and address information. Cost Share Rate Code Define the rate or lump sum amount for cost Maintenance Form (FTMCSTR) share calculations. Cost Share Credit Account Establish accounts to which cost share amounts Maintenance Form (FTMCSTA) will be credited.
4 5
2-90
November 2010
Step
Form
Action
Cost Share Distribution Maintenance Form (FTMCSTD)
Establish the FOAPAL distribution for the recovery of cost share charges.
7 8 9 10 11 12
Indirect Cost Rate Code Define the rate or lump sum amount for indirect Maintenance Form (FTMINDR) cost (F & A) calculations. Indirect Cost Charge Code Establish the accounts and percentages for Maintenance Form (FTMINDA) indirect cost (F & A) calculations. Indirect Cost Distribution Establish the FOAPAL distribution for the Maintenance Form (FTMINDD) recovery of indirect charges. Basis Definition Code Establish the base for cost share and indirect Maintenance Form (FTMBASI) cost (F & A) calculations. Sponsor Account Codes Establish sponsor-required accounts for Maintenance Form (FRVSACT) financial reporting. Institution/Sponsor Account Codes Maintenance Form (FTMISAC) Proposal Maintenance Form (FRAPROP) Proposal Budget Form (FRABUDP) Event Maintenance Form (FRVEVNT) Proposal Events Assignment Form (FRAEVPA) Identify the relationship between your account codes and sponsor account codes for automatic reporting. Establish a proposal and track it through implementation. Establish proposed budget to be submitted to funding agency for approval. Establish codes for events. Assign event codes to a proposal.
13 14 15 16
November 2010
2-91
The following diagram illustrates proposal setup:
Event Info. FRVEVNT (O) (O) Personnel Info. FOAIDEN
Proposal Info. FRAPROP
(O)
CFDA FRVCFDA
Basis Codes FTMBASI
(O) (O) Proposal Budget Info. FRABUDP (O)
Proposal Tracking and User-defined Elements
Indirect Cost Codes FTMINDR FTMINDA FTMINDD
Proposal Budget Totals FRIBUDT
Cost Share Codes FTMCSTR FTMCSTA FTMCSTD
(O)=Optional
2-92
November 2010
Grant Setup
Use the following steps to set up a grant in the Research Accounting module.The following steps are guidelines and may change according to site policies and procedures.
Step
Form
Action
Identification Form (FOAIDEN) Agency Code Maintenance Form (FTMAGCY)
Identify grant accounts, grant administrators, and principal investigators to Banner Finance as persons. Establish the granting agency contacts, address, phone numbers, etc.
2 3
Financial Manager Maintenance Establish financial managers, grant accounts, Form (FTMFMGR) grant administrators, principal investigators, and address information. Cost Share Rate Code Define the rate or lump sum amount for cost Maintenance Form (FTMCSTR) share calculations. Cost Share Credit Account Establish accounts to which cost share amounts Maintenance Form (FTMCSTA) will be credited. Cost Share Distribution Maintenance Form (FTMCSTD) Establish the FOAPAL distribution for the recovery of cost share charges
4 5 6
7 8 9 10 11 12
Indirect Cost Rate Code Define the rate or lump sum amount for indirect Maintenance Form (FTMINDR) cost (F & A) calculations. Indirect Cost Charge Code Establish the accounts and percentages for Maintenance Form (FTMINDA) indirect cost (F & A) calculations. Indirect Cost Distribution Establish the FOAPAL distribution for the Maintenance Form (FTMINDD) recovery of indirect charges. Basis Definition Code Establish the base for cost share and indirect Maintenance Form (FTMBASI) cost (F & A) calculations. Sponsor Account Codes Establish sponsor-required accounts for Maintenance Form (FRVSACT) financial reporting. Institution/Sponsor Account Codes Maintenance Form (FTMISAC) Identify the relationship between your account codes and sponsor account codes for automatic reporting.
November 2010
2-93
Step
Form
Action
13 14 15
Grant Maintenance Form (FRAGRNT) Fund Code Maintenance Form (FTMFUND) Research Accounting Fund Maintenance Form (FRMFUND) Grant Budget Form (FRABUDG) Event Maintenance Form (FRVEVNT) Grant Events Assignment Form (FRAEVGA)
Establish a grant. Establish fund codes and link them to a grant. Associate indirect cost (F & A) codes and cost share codes with an existing fund. Establish a budget for the grant. Establish codes for events. Assign event codes to a grant.
16 17 18
2-94
November 2010
The following diagram illustrates grant setup:
Event Info. FRVEVNT (O) (O) Personnel Info. FOAIDEN
(O)
Grant Info. FRAGRNT
(O)
CFDA FRVCFDA
(O) Basis Codes FTMBASI (O) Grant Budget Info. FRABUDG (O) Indirect Cost Codes FTMINDR FTMINDA FTMINDD Grant Tracking and User-defined Elements
Roll to Ledgers
Grant Budget Totals FRIBUDG
Cost Share Codes FTMCSTR FTMCSTA FTMCSTD
O=Optional
November 2010
2-95
Grant Billing Setup

Use the following steps to set up the Grant Billing component of the Research Accounting module.The following steps are guidelines and may change according to site policies and procedures.
Step
Form
Action
Research Accounting System Control Form (FRASYSC)
Establish system control records that store general billing information about grants such as payee name, address, and other system-level defaults. Establish format codes to customize bills and reports. SunGard Higher Education delivers standard format codes with Banner. Specify which expenditure groups and subtotals to include in institution-defined format codes. Establish exclusion codes that automatically place non-allowable accounts and/or account types on hold. Establish payment management system codes that link together grants that have the same reimbursement requirements and were received from the same sponsoring agency. Update the Grant Billing Information window. Establish a Billed AR account. If you want to use retainage amounts, establish a Retainage AR account. Establish detail codes to process bills for sponsoring agencies and payments from those agencies. Establish codes for events such as bills and reports. Assign event codes to a grant, associate format codes with a grant, and establish billing frequency.
Billing Format Validation Form (FRVBFRM) Grant Billing Format Form (FTMBFRM) Billing Exclusion Maintenance Form (FTMBECL) Payment Management System Code Maintenance Form (FRVPMSC) Grant Maintenance Form (FRAGRNT) Research Accounting Fund Maintenance Form (FRMFUND) Detail Code Control Form (TFADETC) Event Maintenance Form (FRVEVNT) Grant Events Assignment Form (FRAEVGA)
6 7
9 10
2-96
November 2010
The following diagram illustrates Grant Billing setup:
November 2010
2-97
Trail-in and Trail-out Periods

Project starting and ending dates reside within a grant year. Project starting and ending dates are established by the recipient institution and the sponsoring agency. These dates determine the way in which Banner records the grant year and grant period classification of activity in the grant ledger. The intervals of time referred to as trail-in and trail-out periods are periods in which you may perform grant activity within a fund before the starting date of a project and past the ending date of a project. Funds can be effective during trail-in and trail-out periods and grant accounting activity may occur before and after the grant year within effective funds. If you expect to incur costs before the project starting date, you can create a grant fund with an effective date that is earlier than the project starting date. Similarly, if you need to adjust entries after the project ending date, you can create a grant fund with a termination date that is later than the project ending date. You can also create a period within which only authorized users can post transactions to a fund. If you want authorized users to be able to adjust entries after the fund termination date, you can create a grant fund with a expenditure end date that is later than the termination date.
Note To authorize a user to perform this activity, select the Post After Expenditure End Date check box on the User Profile Maintenance Form (FOMPROF).
Cost Share Calculations

Use the following steps to set up cost share calculations and link them to a proposal or grant.
1. Fill out the Cost Share Rate Code Maintenance Form (FTMCSTR). This form enables
you to define the rate or lump sum amount for cost share calculations.
2. Fill out the Cost Share Credit Account Maintenance Form (FTMCSTA). This form
enables you to do one of the following. Enter the accounts to which cost share amounts will be credited. Enter a fund code that will be used as an alternate fund to track cost share activity.
3. Fill out the Cost Share Distribution Maintenance Form (FTMCSTD). This form
enables you to enter the FOAPAL distribution for the recovery of charges.
4. Fill out the Basis Definition Code Maintenance Form (FTMBASI). This form enables
you to define and establish the base for cost share calculations.
2-98
November 2010
5. Fill out the Research Accounting Fund Maintenance Form (FRMFUND). This form
enables you to associate cost share codes to a fund.
Indirect Cost (F & A) Calculations

Use the following steps to set up indirect cost (F & A) calculations and link them to a proposal or grant.
1. Fill out the Indirect Cost Rate Code Maintenance Form (FTMINDR). This form
enables you to define the rate for indirect cost (F & A) calculations.
2. Fill out the Indirect Cost Charge Code Maintenance Form (FTMINDA). This form
enables you to define the accounts to which you want to post indirect cost (F & A) expenses.
3. Fill out the Indirect Cost Distribution Maintenance Form (FTMINDD). This form
enables you to enter the FOAPAL distribution for the recovery of indirect charges.
4. Fill out the Basis Definition Code Maintenance Form (FTMBASI). This form enables
you to define and establish the base for indirect cost (F & A) calculations.
5. Fill out the Research Accounting Fund Maintenance Form (FRMFUND). This form
enables you to associate indirect cost (F & A) codes to a fund. The diagram that follows illustrates the way Banner performs indirect cost (F & A) calculations. Assume that this diagram represents an installations account structure for Labor and Expenditures and that the following values are entered on the appropriate forms. FTMINDR Rate 10% Memo 5% Assume the negotiated rate of I/C is 10%. The memo of 5% represents the difference between an installations actual rate (that is, 15%) and the negotiated rate. FTMINDA Acct 7180 % 100
7180 represents the account code for I/C expenses.
November 2010
2-99
FTMINDD
Fund
Orgn
Acct
Prog
Actv
Locn
1000
210
4333
100
--
--
100
This information tells the system which account types or account code ranges fall within the base for I/C calculations. The system allows for Level 1 or Level 2 values in the Acct Type field and ranges of accounts within the Acct Code From and To fields. Location overrides, exclusions, rate overrides, and maximum amounts may be entered. FTMBASI Type = Indirect This distribution represents the credit side of the I/C expense. In this example, an unrestricted fund and a revenue account are referenced. Given the previous code information, transactions are entered against Fund 2000.
Tran
Fund
Orgn
Acct
Prog
Actv
Locn
Amount
Type of Transaction
1 2
2000 2000
210 210
6011 7010
100 100
---
---
$100 $2,000
Not part of the base Normal rate 10% (from INDR) Memo rate 5% Normal with maximum of $15,000 Rate overrides N=15%; M=10% Exclusion Location N=12%; M=5% Rate override N=8%; M=5%
3 4 5 6 7
2000 2000 2000 2000 2000
210 215 210 210 215
7400 7110 7300 7010 7210
120 130 140 100 100
------
---10 10
$20,000 $1,000 $2,500 $3,000 $4,000
2-100
November 2010
T Accounts
The following example illustrates the effect of indirect cost (F & A), cost share, and revenue recognition on the ledgers. This example assumes that you selected Indirect Cost
November 2010
2-101
then Cost Share from the Indirect Cost and Cost Share Calculation Order drop-down list on the System Control Maintenance Form (FOASYSC).
Example:
Your institution agreed to provide a 25% cost share for salary expenses. The grant covers indirect costs (F & A) at a rate of 10%. A payroll transaction against this grant triggers cost share, indirect cost (F & A) recovery, and revenue recognition transactions automatically
. Key:
1 2 3 4
Record salary expenditure for the grant. Record indirect cost (F & A) revenue and expense (system-generated) Record cost share revenue and expense (system-generated) Record revenue and unbilled accounts receivable (system-generated)
$1,000 $100 $275 $825
2-102
November 2010
Online vs. Deferred Grant Accounting Process

Banner enables you to specify whether you want to perform grant accounting calculations on a transaction-by-transaction (online) basis or on a periodic (deferred) basis.
Online Method
If you elect to use the transaction-by-transaction basis, the associated revenue recognition, indirect cost (F & A), and cost share transactions automatically generate and post every time the system posts grant activity. This method is very useful when you are first learning to use the Banner Finance System, but it has the disadvantage of creating as many as six additional transactions for a single transaction entry. To use the online method, ensure that the Defer Calculations of Indirect Cost and Cost Share check box is cleared (unchecked) on the System Control Maintenance Form (FOASYSC).
Deferred Method
If you elect to use the periodic basis, you can record activity against grants and calculate revenue recognition, cost share, and indirect cost (F & A) recovery whenever you choose. You can also specify the transactions, grants, and funds on which you want to perform calculations. The deferred method effectively reduces the number of transactions in the system and it enables you to perform retroactive indirect cost (F & A) calculations if you receive notification that indirect cost rates have changed. To use the deferred method, follow these steps.
1. Select the Defer Calculations of Indirect Cost and Cost Share check box on the
System Control Maintenance Form (FOASYSC).

2. When you are ready to calculate revenue recognition, cost share, and indirect cost
(F & A) recovery, run the Grant Accounting Process (FRRGRNT). When you run this process, the system produces entries in the Transaction Input Table (FGBTRNI).
3. Execute the Transaction Interface Process (FGRTRNI). FGRTRNI edits the
transactions and creates approved documents for posting.

4. Execute the Posting Process (FGRACTG) to post grant accounting activity.
November 2010
2-103
Grant Budgets
The Grant Budget Form (FRABUDG) enables you to create a grant budget either by entering original budget information or by copying an existing proposal or grant budget. Before you use this form, you must have linked one or more grant funds to a grant using the Fund Code Maintenance Form (FTMFUND). The Grant Budget Form uses this information to ensure that you post transactions to the correct fund(s). In the Worksheet window on the Grant Budget Form, you can enter accounts and amounts in the budget. You can also perform indirect cost (F & A) and cost share calculations. When you create a grant budget, the Grant Budget Form uses the system date as the default transaction date, the Permanent Adopted Budget rule class (BD01), and a budget period of 01. You can change these values. The Grant Budget Form (FRABUDG) edits the document in which the grant budget is stored: it verifies that the transaction date falls within an open accounting period, validates the FOAPAL elements, and forwards the document to the Transaction Interface Process (FGRTRNI). The Transaction Interface Process then edits the document and analyzes any posting modifiers that may be present on the rule class. Once the document clears the Transaction Interface Process, Banner posts it to the ledgers. If your funding changes after the budget has been rolled, you can use the Reversal check box on the Grant Budget Form (FRABUDG) to de-obligate some or all of the budgets linked to a grant.
Proposal and Grant Events

You can link events or reminders to a proposal or a grant. You can also specify who is responsible for indicating when the event is finished (satisfied) and Banner will send reminders to the responsible person or people. When you associate an event with a proposal or a grant, you can specify when Banner will send reminder notices.
Note Before you can indicate that a person is responsible for an event, you must link that persons Banner user name with the internal identification number that was established on the Identification Form (FOAIDEN). To do this, enter the persons internal identification number in the ID field on the User Profile Maintenance Form (FOMPROF).
The Events Messaging Process (FRPMESG) monitors events associated with personnel. This process may be run in sleep/wake mode.
2-104
November 2010
How to Create Proposal or Grant Events

Use the following steps to create events and link them to a proposal or a grant.
1. Use the Event Code Validation Form (FRVEVNT) to create events for activities such
as reports that you need to produce, certifications that you need to perform, and other actions or reminders.
2. (Optional) Use the Event Group Validation Form (FRVEGRP) to group together
related events. For example, you can group reports that need to be produced at the same time.
3. Use the Proposal Events Assignment Form (FRAEVPA) to link events to a proposal
or use the Grant Events Assignment Form (FRAEVGA) to link events to a grant.
How to Satisfy an Event

Use the Proposal Events Action Form (FRAEVNP) and/or the Grant Events Action Form (FRAEVNG) to satisfy or cancel events. You can also use these forms to see a list of events for which you are responsible.
How to Query Events

Use the Proposal Events Inquiry Form (FRIEVNP) and the Grant Events Inquiry Form (FRIEVNG) to view the following: Events linked to a proposal or a grant Events linked to a person Events linked both to a person and to a proposal or a grant
How to Enhance Descriptions for Proposals and Grants

You can append additional text to the defined status code and event codes descriptions. Alternate Description - Status Code (FRAGRNT, FRAPROP) An alternate description field for the status code is available on the Grant Maintenance Form (FRAGRNT) and the Proposal Maintenance Form (FRAPROP). This field holds up to 35 characters. Information you enter into the alternate status field is appended to the status description and then stored in the status history table. If you select the Copy Grant Information or Copy Proposal Information feature from the Options list, this information will copy over to a new grant or proposal.
November 2010
2-105
Alternate Description - Event Code (FRAEVGA, FRAEVPA) An alternate description field for the event code is available on the Grant Events Assignment Form (FRAEVGA) and the Proposal Events Assignment Form (FRAEVPA). This field holds up to 35 characters. Information you enter into the alternate description field is appended to the event description. Both the event description and the alternate description appear on the Grant and Proposal Inquiry Forms and Reports. Alternate Descriptions Display Alternate descriptions for events can display on the following forms. When an alternate description exists for the event, this description is appended to the existing default description when it is viewed on forms or reports. Grants Events Assignment (FRAEVGA) Grant Event Action Form (FRAEVNG) Proposal Event Action Form (FRAEVNP) Proposals Events Assignment Form (FRAEVPA) Grant Event Inquiry Form (FRIEVNG) Proposal Events Inquiry Form (FRIEVNP) Grant Inquiry Status History Form (FRIGRST) Proposal Status History Inquiry Form (FRIPRST)
How to Add Text to Selected Forms

You can add or update descriptive text on the following forms: FRAPROP - Proposal Maintenance Form FRABUDP - Proposal Budget Form (Text option is labelled Text Information) FRAGRNT - Grant Maintenance Form FRABUDG - Grant Budget Form (Text option is labelled Text Information) FRMFUND - Research Accounting Fund Maintenance Form (Text option is labelled Fund Text or Grant Text)
1. From within the form, select the Text option from the Options menu. The General
Text Entry Form (FOATEXT) is displayed.

2. Enter the text. 3. Select Save.
2-106
November 2010
When FOATEXT is called from another form, the following occurs: Text and identifying code are defaulted into the key block. The document type and document code are carried forward from the calling form. Rollback capability is disabled to prevent anyone from changing the document type or document code and viewing information for a different grant or proposal. When you access FOATEXT directly, however, you can view or update any type/code combination.
Agency Funding Information for Grants and Proposals

A check box, labelled Pass Through Indicator, is displayed on both the Grant Maintenance Form (FRAGRNT) and the Proposal Maintenance Form (FRAPROP). This check box is not user-navigable. The system selects this check box when information is available for display on the Pass Through Agency Distribution Information window.
How to View Pre-existing Information

When pass through data exist in the proposal and a grant is created from the proposal, the pass through data are copied forward into the fields displayed in this window. You can use the information displayed in this window to track percentages of contributions from different agencies.
How to Enter New Information

When this is a new grant or proposal, you may enter information into the fields on this window.
1. From the options menu on FRAGRNT or FRAPROP, select the Pass Through Agency
Distribution Information option.

2. On the window that displays, enter the code for the agency (list of values is available)
and the percentage of the funding the agency contributed. The sum of all percentages on this window must be less than or equal to 100.00. You cannot enter a value in one of these fields without entering a value in the other field.
3. Select Save. The Pass Through Indicator check box is selected, which indicates that
pass through information exists for this proposal or grant.

Note If you select the Copy Grant Information or the Copy Proposal Information feature from the Options menu, this information copies over to a new grant or proposal.
November 2010
2-107
Setting up Banner Finance Forms for Effort Certification

Before you can build an effort certification process at your institution, you must first set up the FRAGRNT and FTMFUND forms. For detailed information about the Effort Certification process, refer to the Banner Effort Reporting and Labor Redistributions Handbook. Perform the following steps:
1. (Required, institution-wide setup) Identify grants for which you want to generate
effort certification reports.

1.1.
Check the Requires Effort Certification check box on the Grant Maintenance Form (FRAGRNT). Establish Accounting Element values on the Effort Reporting tab.
1.2.
2. (Required institution-wide setup) Identify specific funds that are not associated with
grants for which you want to generate effort certification reports.

2.1.
Check the Fund Requires Effort Certification check box on the Fund Code Maintenance Form (FTMFUND). If the fund requires effort allocation, check the Fund Requires Effort Allocation check box on FTMFUND.
2.2.
Grant Billing Detail Table (FRRBDET)

The following is an example of the way transactions appear in the Grant Billing Detail Table (FRRBDET) after you post an expenditure against a grant.
Key:
D I C U H
= = = = =
Direct Cost Indirect Cost (F & A) Cost Share (Matching) Unbilled Status Hold Status
2-108
November 2010
Fund
Doc Code
Comp
Status
Exp Acct
Amount
Trans Date
245 245 245
J165 J165 J165
D I C
U U U
6011 6399 5065
1,000 250 -50
01-MAR-99 01-MAR-99 01-MAR-99
245 245 245
J166 J166 J166
D I C
U U U
6053 6399 5065
200 50 -20
10-MAR-99 10-MAR-99 10-MAR-99
245 245 245
I160 I160 I160
D I C
U U U
6101 6399 5065
100 25 -5
12-MAR-99 12-MAR-99 12-MAR-99
245
I161
6215
50
30-MAR-99
245 245
I162 I163
D D
H H
6218 6275
200 100
30-MAR-99 30-MAR-99
245 245 245
I165 I165 I165
D I C
U U U
6299 6399 5065
2,000 500 -100
01-APR-99 01-APR-99 01-APR-99
All expenses charged against a grant fund are posted to the Billing Detail Table (FRRBDET) with an Unbilled status (U).
November 2010
2-109
If you have deferred grant processing turned on, you must run the Deferred Grant Process (FRRGRNT) to post grant expenditures to the Billing Detail Table.
Note The Research Accounting module was designed based on the assumption that revenue is recognized when an expense is incurred.
Before you post transactions against a grant fund, it is recommended that you run the Fund Exception Report (FRRFEXC) to see if all grant funds have the Accrual Acct and Revenue Acct fields populated on the Fund Code Maintenance Form (FTMFUND). Grant funds that do not have these fields populated will not have rows in the Billing Detail Table (FRRBDET). If you create exclusion codes and link them to a grant, Banner will insert transactions involving excluded accounts into the Billing Detail Table with a Hold status (H). You can view unbilled transactions and hold transactions on the Research Accounting Unbilled Status Control Form (FRABDCN). You can also use this form to change the status of transactions from unbilled to hold or from hold to unbilled before you run the Research Accounting Billing Process (FRRBILL).
Generating Bills
1. Fill out the Grant Billing Information window on the Grant Maintenance Form
(FRAGRNT).
2. Define the billing frequency and bill format code on the Grant Events Assignment
Form (FRAEVGA).It is recommended that you assign only one bill format code to each grant.
3. Set up detail codes on the Detail Code Control Form (TFADETC). Example: Detail Code Grant Type Refund Code
Description
Type
Category
Priority
GBIL GRWH GCSH GRRF GRTF
Billing Retainage Cash/Payments Refunds Transfers
C C P C P
GRN GRN GRN GRN GRN
B W P R T
999 999 999 999 999
Cleared Cleared Cleared Selected Cleared
2-110
November 2010
4. Enter values in the following fields on the Research Accounting Fund Maintenance
Form (FRMFUND). Billed AR Account Code Retainage AR Account Code (Optional) Retainage Amount (Optional) Retainage Percentage (Optional)
5. (Optional) Run the Billing Preview Report (FRRINVS) for a specific date to
determine which grants will be selected by the Research Accounting Billing Process when you run it for that date.
6. Run the Research Accounting Billing Process (FRRBILL) in Audit mode for a
specific Billing Format Code and Billing Period To Date.

7. Run the Billing Exception Report (FRRBEXC) to identify exceptions associated with
the specified grant or PMS code.

8. Correct any exceptions found in Step 7. 9. Run the Research Accounting Billing Process (FRRBILL) in Update mode for a
specific Billing Format Code and Billing Period To Date.

Note You must run the Research Accounting Billing Process for PMS codes to create billed charges and obtain letter of credit drawdown to reduce the receivables. 10. Use the following forms to view the billed amounts and print the bills. You can also
use these forms to change the billed amounts; however, your changes will not affect the ledgers. Standard Billing 1034 Form (FRA134B) Standard Billing 270 Form (FRA270B) Standard Billing 272 Form (FRA272B) Generic Bill Form (FRAGENB) If you would like to print more than one bill at a time, use the Run Standard Bills and Reports Form (FRABRUN).
Generic Bills
Generic bills are user-defined and include information specific to amounts budgeted, billed or retained, based on a group sequence number. When there are no expenses for a billing period, the FRRBILL process produces the bill and updates the Generic Bill Table (FRRGENB) using a group sequence number of 999.
November 2010
2-111
If you plan to produce fixed, generic bills with no expenses, use the Grant Billing Format Form (FTMBFRM) to add sequence number 999 to your generic formats. If you do not do this, you will receive the following message on the FRAGENB form: Invalid group sequence number
Budget Limit Processing

The values entered on the Grant Maintenance Form (FRAGRNT) determine how FRRBILL processes budget limits.
Examples:
On the Grant Maintenance Form (FRAGRNT), if the Budget Limit Indicator is set to Total Budget and the Budget Check Source is the Grant Ledger, the billing process will interrogate the Grant Ledger for available budget as of the billing date. It will evaluate the amount of the bill and the cumulative amount (amount previously billed) against the budget amount. It will then interrogate the Bill If Budget Total Exceeded indicator to determine if it should bill or if it should produce an exception. If, instead, the Budget Limit Indicator on FRAGRNT is set to Total Budget and the Budget Check Source is set to Maximum Billing Amount, the billing process evaluates the amount of the bill and the cumulative amount against the Amount entered in the Maximum field. It will then interrogate the Bill If Budget Total Exceeded indicator to determine if it should bill or if it should produce an exception.
Fixed Bill With a Deferred Account

The Deferred Account captures the difference between the fixed amount and the unbilled cost amount. You can enter the appropriate account code information in the Deferred Account Code field on the Billing window of the Grant Form (FRAGRNT) or in the Deferred Revenue Account field on the Research Accounting System Control Form (FRASYSC).
Example 1:
For a fixed price bill of $5,000 with $0 unbilled charges or costs, the postings are as follows: DR Billed A/R $5,000 CR Deferred Account $5,000
Example 2:
For a fixed price bill of $5,000 with $3,000 unbilled charges/costs, the postings are as follows:
2-112
November 2010
DR Billed A/R $5,000 CR Unbilled A/R $3,000 CR Deferred Account $2,000 At the end of the project, you may have a balance for the Deferred Account, which must be cleared with a manual journal entry.
How to Print a 1034 Continuation Form

Use the following steps to print a 1034 Continuation Form, which contains detailed information about a standard 1034 bill.
1. Create a generic bill format code and associate that format code with a grant using the
Billing Format Validation Form (FRVBFRM) and the Grant Billing Format Form (FTMBFRM).
2. Click the Details button on the Standard 1034 Billing Form (FRA134B). Banner will
run the Generic Bill Form (FRRGENB) and print a separate page that you must collate with the appropriate bill. See the Reports and Processes chapter for more information about standard 1034 bills.
Research Accounting Billing Process (FRRBILL)

The Research Accounting Billing Process (FRRBILL) selects grants that meet the following conditions. The billing format matches the Billing Format Code parameter entered by the user. The Due Date field on the Grant Events Assignment Form (FRAEVGA) is less than or equal to the Period End Date parameter entered by the user. For each grant that matches these criteria, Banner selects all unbilled transactions with a transaction date that is less than or equal to the billing period end date of the grant. You can run the Research Accounting Billing Process in Audit mode or Update mode. When you run this process in Audit mode, Banner identifies any exceptions for the specified grant or PMS code, as shown in the following chart, and inserts rows in the Billing Exception Table (FRRBEXC). You can then run the Billing Exception Report (FRRBEXC) to print a list of the exceptions for that grant or PMS code.
November 2010
2-113
Exception
Description
No Billing Address
The billing address was not entered on the Grant Billing Information window of the Grant Maintenance Form (FRAGRNT). The bill includes expense activity that was incurred before the date in the Project Period field on the Grant Maintenance Form. The bill includes expense activity that was incurred after the date in the To field on the Grant Billing Information window of the Grant Maintenance Form. The total bill amount is less than the value in the Minimum field on the Grant Billing Information window of the Grant Maintenance Form. Banner will not process the bill. You can override this exception on the Research Accounting System Control Maintenance Form (FRASYSC) or the Grant Maintenance Form (FRAGRNT). The total billed amount is greater than the value in the Maximum field on the Grant Billing Information window of the Grant Maintenance Form. Banner will not process the bill. You can override this exception on the Research Accounting System Control Maintenance Form (FRASYSC) or the Grant Maintenance Form (FRAGRNT). The total amount billed for a specific line item is greater than the amount budgeted for that item. Banner will not process the bill. You can override this exception on the Research Accounting System Control Maintenance Form (FRASYSC) or the Grant Maintenance Form (FRAGRNT). For bills that use a generic or institution- defined format, Banner uses the budget for the expenditure group defined on the Grant Billing Format Form (FTMBFRM) instead of the amount budgeted for the line item.
Trail In Activity
Trail Out Activity
Billing Minimum Not Reached
Budget Exceeded in Total
Line Item Budget Exceeded
2-114
November 2010
Exception
Description
Expenses Not Included in Format
An expense was posted to an account code that does not belong to an expenditure group defined on the Grant Billing Format Form (FTMBFRM). Banner will not include this expense in the bill.
Billing Items on Hold One or more of the expenses has a Hold status (H) in the Billing Detail Table (FRRBDET). Banner will not include any expenses with a Hold status in the bill. Use the Unbilled Status Control Form (FRABDCN) to change the status of an expense from hold to unbilled. After you correct the exceptions identified on the Billing Exception Report (FRRBEXC), run the Research Accounting Billing Process (FRRBILL) in Update mode. When you run this process in Update mode, Banner does the following: Update the amount in the Cumulative field on the Grant Billing Information window of the Grant Maintenance Form (FRAGRNT). Update the values in the Last Invoice Number field on the Grant Maintenance Form (FRAGRNT). If you billed by PMS code, then Banner will also update the value in the Last Invoice Number field on the Payment Management System Code Maintenance Form (FRVPMSC). Send a document to posting. The starting character of this document is G, the document type is GBL, and the document type sequence number is 75. The transaction date of this document is the date entered in the Posting Date parameter. Change the Status field to S on the Grant Events Assignment Form (FRAEVGA). Insert a row in the Account Charge/Payment Detail Table (TRRACCD) that summarizes billed amounts by grant fund. Use the Research Accounting Payments Entry Form (FRAAREV) to view the summarized amounts. Insert rows into the bill format table that corresponds to the format code entered by the user. For example, if you run the Research Accounting Billing Process for bills with the 272 format, Banner will insert rows in the 272 Bill Format Table (FRR272B) for each of the selected grants. Change the status of the transaction to Billed in the Billing Detail Table (FRRBDET).
Examples:
The following examples are based on the following Grant Billing Detail Table (FRRBDET) that was generated after running the Research Accounting Billing Process (FRRBILL).
November 2010
2-115
Fund
Doc Code
Comp
Status
Exp Acct
Amount
Trans Date
245 245 245
J165 J165 J165
D I C
B B B
6011 6399 5065
1,000 250 -50
01-MAR-99 01-MAR-99 01-MAR-99
245 245 245
J166 J166 J166
D I C
B B B
6053 6399 5065
200 50 -20
10-MAR-99 10-MAR-99 10-MAR-99
245 245 245
I160 I160 I160
D I C
B B B
6101 6399 5065
100 25 -5
12-MAR-99 12-MAR-99 12-MAR-99
245
I161
6215
50
30-MAR-99
245 245
I162 I163
D D
H H
6218 6275
200 100
30-MAR-99 30-MAR-99
245 245 245
I165 I165 I165
D I C
U U U
6299 6399 5065
2,000 500 -100
01-APR-99 01-APR-99 01-APR-99
If you run the Research Accounting Billing Process for the end date of 31-MAR-99 and you use a cost reimbursement schedule, Banner produces the following journal entries using the specified rule class in the grant fund.
2-116
November 2010
Billed Accounts Receivable Rule Class (GRBL)

Transaction Amount Account Form Where Account Is Defined
Debit Credit
1600 1600
Billed AR Unbilled AR
FRMFUND FTMFUND
If you run the Research Accounting Billing Process for the period ending 31-MAR-99 and you use a fixed reimbursement schedule with a fixed bill amount of $2000, Banner produces the following journal entries using the specified rule classes in the grant fund. Billed Accounts Receivable Rule Class (GRBL)
Debit Credit
2000 1600
FRMFUND FTMFUND
Deferred Revenue Rule Class (GRDF)

Credit
400
Deferred
FRAGRNT or FRASYSC
If you run the Research Accounting Billing Process for the period ending 31-MAR-99 and you enter 10 in the Retainage Percent field on the Research Accounting Fund Maintenance Form (FRMFUND), Banner produces the following journal entries using the specified rule classes in the grant fund. Retainage is calculated for Fixed and Cost Reimbursable bills using either an amount or a percent you defined on FRMFUND. It is also very important for you to specify the retainage account on FRMFUND. Billed Accounts Receivable Rule Class (GRBL)
Debit Credit
1600 1600
FRMFUND FTMFUND
Withholding Accounts Receivable Rule Class (GRWH)

Form on which Account is Defined
Transaction
Amount
Account
Debit Credit
160 160
Retainage AR FRMFUND Billed AR FRMFUND
Alternatively, you can generate one bill for all retainage amounts after you run the final bill for a grant. To do this, run the Research Accounting Billing Process and enter
November 2010
2-117
Y in the Bill Retainage parameter. Banner sums the retainage amounts in each bill that you generated before the date you entered in the Billing Period To Date and produces the following journal entries using the specified rule class in the grant fund. Withholding Accounts Receivable Rule Class (GRWH)
Debit Credit
160 160
Billed AR FRMFUND Retainage AR FRMFUND
You can also bill a sponsoring agency for amounts that they withheld from payments. To do this, run the Research Accounting Billing Process and enter Y in the parameter for bill payment withholding. Banner will summarize all payment withholding amounts that you entered on the Research Accounting Payments Entry Form (FRAAREV) and produce a bill. Banner will not produce journal entries.
Reversing a Bill
After you run the Research Accounting Billing Process (FRRBILL) in Update mode and send the bill to the agency, the agency may ask you to adjust the bill. To do this, run the Research Accounting Billing Reversal Process (FRRBREV). This process reverses the bill and undoes the results of the Research Accounting Billing Process. When you run the Research Accounting Billing Reversal Process, Banner does the following: Sends a document to posting and produce the following journal entries.
Transaction Account Form Where Account Is Defined
Debit Credit
Unbilled AR Billed AR
FTMFUND FRMFUND
Changes the Status field on the Grant Events Assignment Form (FRAEVGA) to P so you can run the Research Accounting Billing Process again. Updates the adjustment number. For example, when you reverse a bill for the first time, Banner will change the adjustment number to 1. After you run the Research Accounting Billing Reversal Process, you can change or adjust the charges by posting transactions against the grant fund. Then, you can re-run the Research Accounting Billing Process to generate a new bill. When you re-run the Research Accounting Billing Process, Banner will add 1 to the current adjustment number. The Grant Billing Detail Table (FRRBDET) contains the most recent adjustment number of each bill. If you want to maintain a detailed history of bill reversals in the Billing Detail History Table (FRRBDTH), select the Maintain History for Reversal? check box on the Research Accounting System Control Form (FRASYSC).
2-118
November 2010
Bill Events
There are two types of bill events: on-demand and scheduled. To define an on-demand type schedule, leave the dates and frequency null on FRAEVGA and provide only one date. To define scheduled bill events, set up a schedule on the Event Form (FRAEVGA) with a series of dates and a frequency. The bottom portion of the Event Form displays event sequences that are tied to specific due dates.
On-demand Events
This section describes the impact of billings, reversals, and re-bills on on-demand events for a grant. How to Set up an On-demand Bill Assume you have a grant for which you want a flexible bill schedule.
1. Access the Event Form (FRAEVGA). 2. Leave the Date From, Date To, and Frequency fields blank. 3. Enter your bill type, format and responsible user id. 4. Specify one event sequence. Here is how this schedule is stored in the billing event
sequence table:
Event Sequence
Date
Status
31-JAN
With this schedule, if you generate five invoices, the detail exists in the billing tables but the event table remains unchanged. The event status remains set to P (Pending), which means you have the flexibility to run the process as needed but will not have to change the event sequence date. The last invoice number is updated in the FRBGBIL table and displays in the Billing window of the Grant form. (FRAGRNT).
Note The Status Date is not updated with an on-demand bill.
How to Reverse an On-demand Bill If you generate two bills and reverse invoice number 1, the system will perform the following actions:
November 2010
2-119
Re-set the status of the billed transactions in the billing detail table to unbilled Create reversal entries in the account billing detail table The system does not update the Last Invoice Number, since invoice number 1 was not the last invoice. Neither does the system reset the event status to P (Pending), since this event was an on-demand billing event.
Invoice Number
Sequence Number
Date
1 2
1 0
31-JAN 28-FEB
How to Re-bill an On-demand Bill With on-demand bills, you cannot choose the invoice number you want to produce simply by specifying the Bill Date. Since each bill cannot be tied to an event sequence, the bill process assigns a new unique invoice number whenever a re-bill is performed.
Example:
Refer to the preceding example. If you try to re-bill January expenses using a January date, the following error message is displayed from FRRBILL: The bills From date is greater than its To Date.
Invoice Number
Sequence Number
Date
Bill From Date
Bill To Date
1 2
1 0
31-JAN 28-FEB
Grant Proj Start Date 01-FEB
31-JAN 28-FEB
If you try again and re-bill January expenses using a date late than February 28, the system re-bills Januarys expenses and assigns an invoice number of 3.
Scheduled Events
This section describes the impact of billings, reversals, and re-bills on scheduled events for a grant. For scheduled bill events, you can determine the invoice number you want to produce by specifying the bill date.
2-120
November 2010
How to Set up a Scheduled Bill Event

1. Access the Event Form (FRAEVGA). 2. Enter values in the Date From, Date To, and Frequency fields. 3. Enter your bill type, format and responsible user ID.
The system creates the schedule. Here is an example of a monthly schedule in the billing event table:
Event Sequence
Date
Status
1 2 3 4 5 6 7
31-JAN 28-FEB 31-MAR 30-APR 31-MAY 30-JUN 31-JUL
S (Satisfied) S S S S P (Pending) P
When a grant or PMS is created with a series of scheduled events, as in this example, FRRBILL uses the bill date to determine the event or events it is satisfying. How to Reverse a Scheduled Bill Event Assume that invoices are associated with each billing run from the previous chart. Invoice number 5 was first generated with a date of 31-MAY. Initially, this invoice had a billing sequence number of 0. If you run the reversal process, the information changes as follows:
Invoice Number
Sequence Number
Event Sequence
Date
Status
1 2 3 4
0 0 0 0
1 2 3 4
31-JAN 28-FEB 31-MAR 30-APR
S S S S
November 2010
2-121
Invoice Number
Sequence Number
Event Sequence
Date
Status
5 6 7 8
31-MAY 30-JUN 31-JUL 30-AUG
P P P P
Running the reversal process has updated the sequence number for invoice 5 to 1. It has also reset the Last Invoice Number to 4, which means that invoice number 4 is the last satisfied invoice. How to Re-bill a Scheduled Bill Event If you decide to run FRRBILL again using a bill date of 31-MAY, the process will create invoice 5, with a sequence number of 2. This satisfies the event (status indicator is set to S) and updates the status date using the bill date, which is parameter # 11 from the frrbill process.
Invoice Number
Sequence Number
Event Sequence
Date
Status
Status Date
1 2 3 4 5
0 0 0 0 2
1 2 3 4 5 6 7 8
31-JAN 28-FEB 31-MAR 30-APR 31-MAY 30-JUN 31-JUL 30-AUG
S S S S S P P P
01-FEB 28-FEB 31-MAR 02-MAY 31-MAY
If you re-run FRRBILL with a date of 30-JUN, the process creates invoice number 5 with a sequence number of 2. In this example, the billing process satisfied two event sequences: May and June, as shown:
2-122
November 2010
Invoice Number
Sequence Number
Event Sequence
Date
Status
Status Date
1 2 3 4 5 5
0 0 0 0 2 3
1 2 3 4 5 6 7 8
S S S S S S P P
01-FEB 28-FEB 31-MAR 02-MAY 30-MAY 30-JUN
Prior Period Reversals

A prior period reversal is the reversal of a grant billing period that is not the last one billed.
Note When a prior period bill is reversed, the Last Invoice Number is not changed.
This process is performed by running FRRBREV. You can reverse any PMS or grant code executed with a bill date that is equal to the value in the Billing Date parameter. The system-determined Bill End Date is stored in the Grant Event Table (FRREVNG) in the Status Date column. As events are selected and FRRBILL satisfies those events, it updates the status date, and allows the Reversal Process (FRRBREV) to pick up the event entries it needs to reverse. This is important for fixed price grants where expenses may not exist for the period billed or reversed.
Example:
Assume your institution has produced five invoices but now needs to reverse invoice number 2. To reverse invoice number 2, access FRRBREV, and perform one of the following actions: Enter the grant code and specify invoice 2 with a sequence number of 0 Enter the grant code and a billing date of 28-FEB
November 2010
2-123
Here are the results:
Invoice Number
Sequence Number
Event Sequence
Date
Status
Status Date
1 2 3 4
0 1 0 0
1 2 3 4 5
S P S S S S P P
01-FEB
31-MAR 02-MAY 31-MAY 30-JUN
6 7 8
The reversal process created sequence number 1 for invoice number 2. The status indicator is reset to P (Pending) and the status date is removed. If you decide to make adjustments and re-submit invoice 2 with a billing date of 28-FEB, the system creates invoice 2 with a sequence number of 2.
Invoice Number
Sequence Number
Event Sequence
Date
Status
Status Date
1 2
0 2
1 2
31-JAN 28-FEB
S S
01-FEB 28-FEB
You can also add unbilled expenses to the latest bill. If you run FRRBILL with a billing date of 31-JUL, this is what you see:
Invoice Number
Sequence Number
Event Sequence
Date
Status
Status Date
1 2 3 4
0 1 0 0
1 2 3 4
31-JAN 28-FEB 31-MAR 30-APR
S S S S
01-FEB 31-JUL 31-MAR 02-MAY
2-124
November 2010
Invoice Number
Sequence Number
Event Sequence
Date
Status
Status Date
5 5 6 2 0 6 7 8
31-MAY 30-JUN 31-JUL 30-AUG
S S S P
31-MAY 30-JUN 31-JUL
In this example, expenses for February have been included in the July invoice. Event sequences 2 and 7 are satisfied (status indicator is set to S) and both display a status date of 31-JUL.
Note In this example, the Last Invoice Number is not updated during the reversal process unless the bill relates to the last bill. When invoice number 2 was reversed, the Last Invoice Number was still 5. Note If invoices 2, 3, 4, and 5 in this example are all reversed, then the last invoice number is reset to 1.
Payments Received From a Sponsoring Agency

Use the Research Accounting Payments Entry Form (FRAAREV) to enter payments received from a sponsoring agency. You can enter payments for a PMS Code (letter of credit drawdown) or a grant.
Entering Payments for a PMS Code

Use the following steps to enter payments for a PMS code:
1. Access the Research Accounting Payments Entry Form (FRAAREV). 2. Enter the PMS Code. 3. Select the Distribute To Grants check box. 4. Enter a detail code in the Detail Code field. 5. Enter the Amount of the payment. 6. Perform a Next Block function. Banner distributes the payment to the grants
belonging to the specified PMS Code.

7. (Optional) Manually change the distribution.
November 2010
2-125
8. Save. Banner credits the payment to the fund and account entered in the LOC Fund
and the Undistributed Cash Account fields on the Payment Management System Code Maintenance Form (FRVPMSC).
9. Use the Cashier Session Review Form (TGACREV) to close and finalize the
cashiering session. See the Banner Accounts Receivable User Guide for more information about cashiering sessions and the Cashier Session Review Form.
10. Use the Application of Payment Process (TRRAPPL) to apply payments to charges. 11. Run the following scripts to feed the transactions to the ledgers.
TGRFEED FURFEED FGRTRNI FGRACTG Banner produces the following journal entries using the specified rule classes. Grant Payment Rule Class (GRPM)
Transaction
Account
Form Where Account Is Defined
Debit Credit
Cash Interfund Undistributed Cash Receipt
GMXBANK FRVPMSC
Banner also posts the corresponding cash to the account in the Cash Receipt Bank Code field on the Fund Code Maintenance Form (FTMFUND). If you want Banner to post cash to the account in the Bank field on the Fund Code Maintenance Form (FTMFUND) instead of the account in the Cash Receipt Bank Code field, change the edit code on the GRPM rule class to edit code 2801. Grant Application of Payment Rule Class (GRAP)
Transaction
Account
Debit Credit
Undistributed Cash Receipts Billed AR
FRVPMSC FRMFUND
If the Undistributed Cash Receipt account and the Billed AR account are associated with different funds, Banner posts interfund entries to balance the charge and payment funds.
2-126
November 2010
Entering Payments for a Grant

Use the following steps to enter payments for a grant:
1. Access the Research Accounting Payments Entry Form (FRAAREV). 2. Enter the Grant. 3. Perform a Next Block function. 4. Enter or select a payment detail code in the Detail Code field. 5. Enter the Payment. 6. (Optional) If you want to apply the payment to a specific transaction, enter the
transaction number in the appropriate Tpay field. If you want to apply the payment to a specific bill, enter the invoice number in the appropriate Invoice Number Paid field.
7. (Optional) Enter a Fund. 8. Save. Banner credits the payment to funds entered in the Payment Fund Code and
the Undistributed Cash Receipt Account fields on the Grant Maintenance Form (FRAGRNT). If you did not enter a value in the Payment Fund Code field on the Grant Maintenance Form and you entered a value in the Tpay field in Step 6, the fund code defaults from the charge associated with the specified Tpay value. If you did not enter a value in the Payment Fund Code on the Grant Maintenance Form and you did not enter a value in the Tpay field in Step 6, then you must enter a value in the Fund field in Step 7.
9. Use the Cashier Session Review Form (TGACREV) to close and finalize the
cashiering session. See the Banner Accounts Receivable User Guide for more information about cashiering sessions and the Cashier Session Review Form.
10. Use the Application of Payment Process (TRRAPPL) to apply payments to charges. 11. Run the following scripts to feed the transactions to the ledgers.
TGRFEED FURFEED FGRTRNI FGRACTG Banner produces the following journal entries using the specified rule class.
November 2010
2-127
Grant Payment Rule Class (GRPM)
Transaction
Account
Debit Credit
Cash Interfund Undistributed Cash Receipt
GXRBANK FRAGRNT
Banner posts the corresponding cash to the account in the Cash Receipt Bank Code field on the Fund Code Maintenance Form (FTMFUND). If you want Banner to post cash to the account in the Bank field on the Fund Code Maintenance Form (FTMFUND) instead of the account in the Cash Receipt Bank Code field, change the edit code on the GRPM rule class to edit code 2801. Grant Application of Payment Rule Class (GRAP)
Transaction
Account
Debit Credit
Undistributed Cash Receipts Billed AR
FRAGRNT FRMFUND
If the Undistributed Cash Receipt account and the Billed AR account are associated with different funds, Banner posts interfund entries to balance the charge and payment funds.
Tips
You can enter the amount withheld by a sponsoring agency in the Withholding Amount field on the Research Accounting Payments Entry Form (FRAAREV). Select the Rebill Indicator check box on the Research Accounting Payments Entry Form if you need to send a bill to the agency for this amount. You cannot create charges on the Research Accounting Payments Entry Form (FRAAREV). Charges are created by the Research Accounting Billing Process (FRRBILL). The only charge that you can enter on this form is a refund to the sponsoring agency. To do this, enter a refund detail code in the Detail Code field. If you received a payment and you do not know the grant for which it is intended, use the Miscellaneous Transaction Form (TFAMISC) to enter the payment and apply that payment to the account in the Payment Holding Account field on the Research Accounting System Control Form (FRASYSC). Later, you can use the Research Accounting Payments Entry Form (FRAAREV) to transfer the payment to the appropriate grant using a transfer detail code. Banner will use the GRTF rule class to process this payment.
2-128
November 2010
Reversal of Applied Payments

After you run the Application of Payment Process (TRRAPPL), you may need to reverse, or undo, the results. To do this, run the Unapplication of Payments Process (TRRUNAP) or use the Grant Unapplication of Payments Form (FRAUNAP).
Note You cannot reverse payments that have been applied manually on the Research Accounting Payments Entry Form (FRAAREV).
When you run the Unapplication of Payments Process, Banner produces the following journal entries using the specified rule class. Grant Application of Payment Rule Class (GRAP)
Transaction
Account
Debit Credit
Billed AR Undistributed Cash Receipts
FRMFUND FRAGRNT or FRVPMSC
Generating Reports
Use the following steps to generate reports:
1. Define the reporting frequency and report format code on the Grant Events
Assignment Form (FRAEVGA).You can assign more than one report format code to each grant.
2. Run the Research Accounting Report Process (FRRGRPT) for a specific Report
Format Code and Reporting Period To Date.

3. Use the following forms to view and print the reports. You can also use these forms to
change the amounts on the reports; however, your changes do not affect the ledgers. Standard Report 269 Form (FRA269R) Standard Report 272 Form (FRA272R) Generic Report Form (FRAGENR) If you would like to print more than one report at a time, use the Run Standard Bills and Reports Form (FRABRUN).
November 2010
2-129
Interfacing Grant Information From an External System to Banner

You can maintain a proposal and grant information in a system external to Banner while simultaneously maintaining billing and accounting information within the Banner environment. This interface includes the following features: Collector tables that hold the data loaded from an external source. Processes that insert and update all associated grant tables including grant budget tables, grant billing tables, grant events, and grant user-defined fields. Codes used to drive the accounting or billing were developed using existing Banner forms. The creation and maintenance of Grant funds, indirect cost, cost share, and billing codes are maintained using existing Banner forms and are not a part of the interface. Before using the grant interface, you must develop a client-specific program to load data from an external source into the collector tables. After these data are loaded into the collector tables, you can submit the interface process, at your discretion, using Banners Job Submission module.
Collector Table Basics

User ID Field The User ID field in all tables defaults to the user ID of the person submitting the interface job. Activity Date Field The Activity Date in all tables defaults to the system date, when executed. Clearing Fields If a field is populated in Banner prior to the interface and the associated data in the collector table are null, then the Banner field is not updated. For budgets, only new budget detail is loaded through the interface. If budget detail (FRRBUDG) already exists in Banner (for the associated Grant), no updates or new inserts occur. An error message prints that indicates the budget detail was not loaded because it already exists. You can then go into Banner and make small changes or recreate the budget with a new budget code.
Error Reporting
The process sends the errors to the FRCTRNR collector table. An error report is printed from the error table listing all errors encountered during the process.
2-130
November 2010
An E error is classified as a fatal error. No update or insert occurs to any Banner tables referenced in a grant code with a fatal error. Grant codes without errors process through into the Banner grant tables. Data with fatal errors must be fixed before the next execution of the applicable C program. A W error creates a warning message. The value in the collector table is not used in the grant tables although processing continues. Both C programs inform the user if data has been processed with a warning message.
Grant Interface Processes

The Grant Interface Process (FRPGINF) and Grant Budget Interface Process (FRPBINF) may be run at the host, via Job Submission, through a job scheduler, or in a sleep/wake process. There is no requirement that these processes be run on a specific cycle or schedule. The processes may be run whenever you want to process grant data from an external source into Banner. For detailed information about these processes, refer to the Reports and Processes chapter.
Grant Security Access

If Fund and Organization Security on FOASYSC is checked (Yes), FRAGRNT Organization security considerations are used in the Grant Interface Process (FRPGINF) when the Organization code is entered on the grant header record in the collector interface table. This level of security affects only the grant header interface. The User ID of the person submitting the job must be defined on FOMPROF. If the User ID (on FOMPROF) has Both or Posting for Master Organization, access is granted and interface processing is continued. If the User ID (on FOMPROF) has No Access, information on FOMUSOR determines access to the organization. The user must be granted Both or Posting access to continue interface processing. If Fund and Organization Security on FOASYSC is checked (Yes), FRABUDG Fund and Organization security considerations are used in Grant Budget Interface Process (FRPBINF) when the Index, Fund, and Organization codes are entered on the grant budget header record in the collector interface table. This level of security affects only the grant budget header interface. Access, for Funds, is granted if Master Fund is defined as either Posting or Both - Query and Posting on FOMPROF. If the user has Master Fund defined as No Authority, the user must have either Posting or Both defined as access on FOMUSFN for the fund or hierarchy that contains the fund or the fund type that contains the fund. Access, for grant organizations, is granted if the user has defined Master Organization as Posting or Both - Query and Posting on FOMPROF. If the user has Master Organization defined as No Authority, the user must have either
November 2010
2-131
Posting or Both defined as access on FOMUSOR for the organization or hierarchy that contains the organization.
Mapping Collector Tables to Grant Tables

The grant interface process maps data elements from collector tables to the grant tables identified here. Detailed information about each table follows this list, along with any applicable default values. FRBBUDGGrant Budget Header Table FRBEVNGGrant Events Code Base Table FRBGBILResearch Accounting Grants Billing Table FRBGRNTGrant Header Table FRRBFIXSponsored Research Grant Events Fixed Schedule Data Repeating Table FRRBUDGGrant Budget Lines Detail Table FRREVNGSponsored Research Grant Events Status Repeating Table FRRGLOCGrant Location Repeating Table FRRGRPIGrant Personnel Repeating Table FRRPRXG Sponsored Research Grant Events User Id Repeating Table FRRGUSNGrant User Defined Codes Repeating Table FRVGRST Grant Status History Table Grant Budget Header Mapping (to FRBBUDG and FRRBUDG) Updating this table for new grants must occur after FRBGRNT. For new grants, the FRBBUDG table is updated before FRRBUDG. For existing grants, budget detail may not be updated. The FRRBUDG table is updated after FRBBUDG. For additional information, refer to Grant Budget Lines Mapping (to FRRBUDG) on page 2-150.
2-132
November 2010
Temporary Table Column Name
Grant Table and Fields

FRBBUDG_GRNT_CODE
Column Comments
Error Consequences
Grant Code
Subject to same edits as FRBGRNT. Required. Required If a budget code is entered and it already exists on FRBBUDG for this grant, process displays a warning message that the existing budget information will be overwritten by the interface. If a new budget code and description is not entered, process displays an error message. If not entered or not valid, process displays warning message and default W.
Grant Budget Code FRBBUDG_GRNT_

BUDG_CODE
Budget Description
FRRBBUDG_BUDGET_ DESC
Required for new budget codes
Budget Type
FRBBUDG_TYPE_CODE
Validated against FTVSDAT. Value is required for new budget codes; default value is W. If not entered, default value is from FRBGRNT_PROJECT_ START_DATE.
Budget Begin Date FRBBUDG_BEG_DATE
Budget Period End Date
FRBBUDG_END_DATE
If not entered, default value If entered, must be > Budget is from FRBGRNT_PROJECT_ Begin Date; if not, process END_DATE displays warning message and default FRBGRNT_
PROJECT_END_DATE.
Budget Year Budget Reversal
FRBBUDG_YR FRBBUDG_REVERSAL_ IND
If entered, must be Y.
November 2010
2-133
Column Comments
Error Consequences
Budget Chart Code FRBBUDG_COAS_CODE If not entered, default value Cannot be null if the is from FRBGRNT_COAS_ following fields are not set to CODE_IC_CS null:
FRCGRNT_INDR_COST_BASIS _CODE FRCGRNT_INDR_COST_RATE_ CODE FRCGRNT_INDR_COST_CHRG_ CODE FRCGRNT_INDR_CST_DIST_T O_CODE FRCGRNT_COST_SHARE_BASI S_CODE FRCGRNT_COST_SHARE_RATE _CODE FRCGRNT_COST_SHARE_CRED IT_CODEFRCGRNT_SHARE_DI STR_CODE
Budget Indirect Cost Basis Code Budget Indirect Cost Rate Code
FRBBUDG_BASI_ CODE_IC
Validated against FRBBASI Validated against FRVINDR
If not on FRBBASI, field is set to null and process displays warning message. If not on FRVINDR, field is set to null and process displays warning message. If not entered, default value is from
FRBGRNT_INDR_CODE_RATE.
FRBBUDG_INDR_ CODE_RATE
Budget Indirect Cost Charge Code
FRBBUDG_INDA_ CODE_CHARGE
Validated against FRVINDA
If not on FRVINDA, field is set to null and process displays warning message. If not entered, default value is from FRBGRNT_INDA_ CODE_CHARGE.
Budget Indirect Cost Distribute Code
FRBBUDG_INDD_ CODE_DISTR
Validated against FRVINDD
If not on FRVINDD, field is set to null and process displays warning message. If not entered, default value is from FRBGRNT_INDD_ CODE_DISTR. Same as above.
2-134
November 2010

FRBBUDG_BASI_ CODE_CS
Column Comments
Error Consequences
Budget Cost Share Basis Code
Validated against FRBBASI
If not on FRBBASI, field is set to null and process displays warning message. If not entered, default value is from FRBGRNT_BASI_CODE_CS.
Budget Cost Share Rate Code
FRBBUDG_CSTR_ CODE_RATE
Validated against FRVCSTR
If not on FRVCSTR, field is set to null and process displays warning message. If not entered, default value is from FRBGRNT_CSTR_CODE_RATE.
Budget Cost Share Credit Code
FRBBUDG_CSTA_ CODE_CHARGE
Validated against FRVCSTA
If not on FRVCSTA, field is set to null and process displays warning message. If not entered, default value is from FRBGRNT_CSTA_ CODE_CHARGE.
Budget Cost Share Distribute Code
FRBBUDG_CSTD_ CODE_DISTR
Validated against FRVCSTD
If not on FRVCSTD, field is set to null and process displays warning message. If not entered, default from
FRBGRNT_CSTD_CODE_DISTR.
Budget Maximum Funding Amount Budget Requested Amount Budget Posting Transaction Date
FRBBUDG_MAX_ FUNDING_AMT
If not entered, default value is from

FRBGRNT_MAX_FUNDING_AMT.
FRBBUDG_ REQUESTED_AMT
If not entered, default value is from FRBGRNT_CURRENT_ FUNDING_AMT. Validated that date is within If not entered, default value open fiscal period on is sysdate. Process performs standard transaction date FRVFSYR, FTVFSPD edits.
FRBBUDG_TRANS_DAT E
November 2010
2-135

FRBBUDG_RUCL_CODE
Column Comments
Error Consequences
Budget Posting Rule Code
Validated against FTVRUCL. Validated for Rule Class Security if Rule Class Security turned on in FOBSYSC.
If entered and invalid, or if user has no access to the rule code, process displays warning message. If not entered, default value is BD01. If user does not have rule code access to BD01, process displays warning message only if Rule Class Security is turned on in FOBSYSC.
Budget Posting Period
FRBBUDG_BUDGET_ PERIOD
Must be 01-12.
If not entered, process displays warning message and default Period 01. If annual, then it should always be 01.
The following fields are not defined on the collector table, but are defaulted to FRBBUDG during the upload.
Column Comments
Error Consequences
PARM VALUE for FRBBUDG_IC_ Calculate Indirect CREDIT_IND Cost and Cost Share PARM VALUE for FRBBUDG_CS_ Calculate Indirect CREDIT_IND Cost and Cost Share
Valid values are null or Y
Valid values are null or Y.
PARM VALUE for FRBBUDG_CS_DISTR_ Valid values are null or Y. Create distribution IND entries for indirect cost and cost share
2-136
November 2010

FRBBUDG_COMPLETE_ IND
Column Comments
Error Consequences
Y is the default value if parameter indicates to create FGBTRNI; otherwise, field is set to null. Updated with sysdate when document is written to FGBTRNI. Updated with the FGBTRNI document number. Field is set to null. If the Complete Indicator is null, field is set to null. If the Complete Indicator is Y, default value is Y. Field is set to null. Fiscal year is defaulted from FRBBUDG_TRANS_ DATE. Process accesses FTVFSYR/FTVFSPD with transaction date to determine fiscal year. System-maintained Sequence. Items 1 and 2 are reserved for the calculated indirect and cost share amounts, respectively. Always reserved whether or not any values are calculated. All other budget line items will begin with 3 and increment by 1. System maintained Line item is updated with P if there are no fatal errors.
FRBBUDG_SUB_DATE
FRBBUDG_DOC_NUM
FRBBUDG_EDIT_ DEFER_IND FRBBUDG_APPROVAL_ IND
FRBBUDG_NSF_ON_ OFF_IND FRBBUDG_FSYR_CODE
FRBBUDG_SEQ_NUM_ MAIN
FRBBUDG_SEQ_NUM FRRBUDG_STATUS_ IND
November 2010
2-137
Grant Events Code Mapping (FRCEVNG to FRBEVNG) For new grants, Updating FRBEVNG occurs after FRBGRNT. Updating FRREVNG occurs after FRBENVG. Updating FRRPRXG occurs after FRBENVG. Updating FRRBFIX occurs after FRBENVG. If Event Header Information is entered, the process calculates the due date based on the number of days and the indicator or the frequency. The process uses that information to create the appropriate number of entries in the FRRENVG, FRRPRXG, and FRRBFIX. If Event Header information is being updated, the existing FRREVNG, FRRPRXG, and FRRBFIX records are deleted and new ones inserted based on the header data.
Note The Collector table definition accommodates entry of multiple fixed bill funds and amounts.

FRBEVNG_GRNT_CODE
Column Comments
Error Consequences
Grant Code Required Event Code Required Number of Days Begin Date Indicator
Subject to same edits as FRBGRNT Validated against FRVEVNT If invalid, process displays an error message.
FRBEVNG_EVNT_CODE
FRBEVNG_NUM_OF_ DAYS FRBEVNG_BEG_DATE_ IND
Required if Number of Days has been entered
If entered and Number of Days is not entered, field is set to null and process displays warning message. If null or invalid and FRVEVNT_TYPE_IND = B and if FRBEVNG_PMT_METHOD_ TYPE_IND=C, process displays error message. Otherwise, process displays warning message.
Frequency
FRBEVNG_FREQ_IND
Valid values are null, W, B, M, Q, S, and A. Required if FRVEVNT_ TYPE_IND=B and if FRBEVNG_PMT_METHOD_ TYPE_IND=C
2-138
November 2010

FRBEVNG_DATE_FROM
Column Comments
Error Consequences
Date From
Date from is equivalent to the Period To date.
If null and if FRVEVNT_TYPE_ IND=B, default value is

FRBGRNT_PROJECT_START_ DATE.
If FRVEVNT_TYPE_IND=B, and if entered and less than

FRBGRNT_PROJECT_START_ DATE process displays error
message. Date To
FRBEVNG_DATE_TO
If entered, must be > Date From. If not, process displays error message. If null and if FRVEVNT_TYPE_ IND=B, default value is FRBGRNT_PROJECT_END_ DATE.
# of Days Reminder Bill Format Code Payment Method Type
FRBEVNG_NUM_OF_ DAYS_REMINDER FRBEVNG_BFRM_CODE
Validated against FRVBFRM Valid values are C or F. Required if FRVEVNT_TYPE_IND=B
If invalid, process displays warning message. If null, process displays warning message and default C.
FRBEVNG_PMT_ METHOD_TYPE_\IND
Grants Billing Information Mapping (FRCGRNT to FRBGBIL) Updating this table will occur after FRBGRNT. Billing information mapping is optional. A collector table is not required to include any billing information. If included, it must then contain the required fields. Appropriate edits and validations take place prior to mapping. is defaulted from FRBGRNT. It is not a field that is contained in the collector table for interfacing to FRBGBIL.
FRBGBIL_COAS_CODE
November 2010
2-139

FRBGBIL_GRNT_CODE
Column Comments
Error Consequences
Grant Code Required PMS Code Billing Exclusion Code Budget Limit Indicator
Subject to same edits as FRBGRNT Validated against FRVPMSC Validated against FRVBECL Valid values are null, T for Total Budget, L for Line Item Budget, N for No Budget Action Required. Default value is T. No entry allowed. Default value comes from FRBGRNT_COAS_CODE. This field is not retained in the collector table for interfacing to FRBGBIL. Validated against FTVFUND If invalid, process displays warning message. If null and PMS code entered, default value is from FTVPMSC. If invalid, process displays a warning message. If invalid, process displays a warning message. If invalid, process displays a warning message: WARNING Budget Limit Ind was defaulted to (T)otal Budget.
FRBGBIL_PMSC_CODE
FRBGBIL_BECL_CODE
FRBGBIL_BUDGET_ LIMIT_IND
FRBGBIL_COAS_CODE
Payment Fund Code
FRBGBIL_PAYMENT_ FUND_CODE
Undistributed Cash FRBGBIL_PAYMENT_ ACCT_CODE Receipt Account
Validated against FTVACCT
If invalid, process displays warning message. If null and PMS code entered, default value is from FTVPMSC.
Last invoice number
FRBGBIL_LAST_INV_ SEQ_NO
If null and PMS code entered, default value is from FTVPMSC.
2-140
November 2010

FRBGBIL_ADDR_TYPE
Column Comments
Error Consequences
Billing Address Type
Validated against STVATYP
If null and Agency Code is on FRBGRNT, default value is from FTVAGCY. If invalid, field is set to null and process displays warning message.
Billing Address Sequence Number
FRBGBIL_ADDR_ SEQNO
Required if Address Type is If null and address type is entered. null and Agency Code is on FRBGRNT, default value is from FTVAGCY. If null and address type is entered, set address type to null and process displays warning message.
Billing Start Date
FRBGBIL_BILLING_ START_DATE
If null, default value is from

FRBGRNT_PROJECT_START_ DATE.
Billing End Date
FRBGBIL_BILLING_ END_DATE

FRBGRNT_PROJECT_END_ DATE.
If entered and not greater than project start date, field is set to null and process displays a warning message. Billing Minimum Amount Limit
FRBGBIL_BILLING_ MIN_AMT
If entered, must be numeric, value with two decimal places. If not, process displays warning message.
Billing Maximum Amount Limit
FRBGBIL_BILLING_ MAX_AMT
Defaults from FRBGRNT

FRBGRNT_MAX_FUNDING_AMT.
If entered, must be numeric value with two decimal places. If not, process displays warning message.
November 2010
2-141

FRBGBIL_DEFERRED_ ACCT_CODE
Column Comments
Error Consequences
Deferred Account Code
Validated against FTVACCT
If invalid, process displays warning message and leaves the account code null.
Billing Cumulative FRBGBIL_ CUMULATIVE_ Amount

BILLED_AMT
Refund Clearing Account 1034 BFRM Extension Bill if budget line exceeded? Bill if budget total exceeded? Bill if minimum not reached? Budget Check Source
FRBGBIL_CLEARING_ ACCT_CODE
Validated against FTVACCT Validated against FRVBFRM Valid values are null, Y, or N Valid values are null, Y, or N Valid values are null, Y, or N Valid values are null, G, or B
If invalid, process displays warning message and leaves the account code null. If invalid, process displays warning message and field is set to null. If invalid, process displays warning message and field is set to null. If invalid, process displays warning message and field is set to null If invalid, process displays warning message and field is set to null. If invalid, process displays warning message and field is set to null.
FRBGBIL_BFRM_ CODE_1034_EXT
FRBGBIL_BUD_LINE_ EXCEED_IND
FRBGBIL_BUD_ TOTAL_EXCEED_IND
FRBGBIL_MIN_NOT_ REACHED_IND
FRBGBIL_BUD_ CHECK_SOURCE_IND
Grant Header Table Mapping (FRCGRNT to FRBGRNT) Collector table FRCGRNT data are mapped to the existing Banner FRBGRNT table. Unless otherwise specified, all fields are optional. Appropriate edits and validations take place prior to mapping.
Note All indirect cost code and cost share code columns must be entered. If these columns are not entered or cannot be defaulted from the proposal, the field is set to null and the process displays a warning message.
2-142
November 2010

FRBGRNT_CODE
Column Comments
Error Consequences
Grant Code Required
A grant code must be entered.
If a grant code is entered and it already exists on FRBGRNT, process displays a warning message that the grant exists and it will be updated. If null, default value is from FOMPROF for user id, which means the user id must be defined in FOMPROF. If not on FTVCOAS, process displays invalid chart code error message.
COAS Code Required when FOASYSC indicates Org Security is on
FRBGRNT_COAS_CODE
Validated against FTVCOAS
Responsible Organization Required when FOASYSC indicates Org Security is on
FRBGRNT_COAS_CODE
Validated against FTVCOAS
If not on FTVORGN, process displays invalid organization error message. If the user does not have update access for the Org code entered, process displays an error message
Proposal Code
FRBGRNT_PROP_CODE
Validated against FRBPROP
If not on FRBPROP, process displays an invalid proposal warning message. If a valid proposal value is entered and it is a new grant, process defaults all corresponding fields from the proposal to the grant.
Long Title Optionally required
FRBGRNT_LONG_ TITLE
Can be null if the Short Title is entered. Default is the Short Title if null.
If null and Short Title is null and proposal code is null, process displays an error message. If null and new grant and valid Proposal Code is entered, default value is FRBPROP_LONG_TITLE.
November 2010
2-143

FRBGRNT_TITLE
Column Comments
Error Consequences
Short Title Optionally required
Can be null if the Long Title is entered. Default the first 35 characters from the Long Title.
If null and Long Title is null and proposal code is null, process displays an error message. If null and new grant and valid proposal code is entered, default FRBPROP_TITLE.
No entry allowed
FRBGRNT_PI_PIDM
Not entered, updated from FRRGRPI Validated against SPRIDEN. Validated against FTVAGCY. If the ID is on SPRIDEN, access FTVAGCY to determine if agency has been set up. If not on FTVAGCY, process displays warning message. Must be numeric value with two decimal places. If not, process displays warning message. Must be numeric value with two decimal places. If not, process displays warning message. Must be numeric value with two decimal places. If not, process displays warning message. Validated against FTVSDAT. Must update the FRVGRST table. If not on FTVSDAT, field is set to null and process displays warning error.
Agency Id Number FRBGRNT_AGENCY_

PIDM
Current Funding Amount
FRBGRNT_CURRENT_ FUNDING_AMT
Cumulative Funding Amount
FRBGRNT_CUM_ FUNDING_AMT
Maximum Funding FRBGRNT_MAX_ FUNDING_AMT Amount
Grant Status Code
FRBGRNT_STATUS_ CODE
Grant Status Date Grant Expenditure End Date
FRBGRNT_STATUS_ DATE FRBGRNT_EXPEND_ END_DATE
If null and if Status Code is entered, default sysdate. Must be > Grant Project Start Date If not, field is set to null and process displays warning message.
2-144
November 2010

FRBGRNT_TERM_DATE
Column Comments
Error Consequences
Grant Termination Date Grant Project Start Date - required
Must be > Grant Project Start Date Must be < Grant Termination Date Must be < Grant Project End Date
If not, field is set to null and process displays warning message. If null, process displays an error message. If the entered value is different than the one already on FRBGRNT and the grant code is in the grant ledger table (FRRGRNL), then process displays an error message. If not greater than project start date, field is set to null and process displays a warning message. If not on FTVSDAT, field is set to null and process displays warning message. If null and new proposal and proposal code entered, default value is from proposal FRBPROP_PROPOSAL_TYPE.
FRBGRNT_PROJECT_ START_DATE
Grant Project End Date
FRBGRNT_PROJECT_ END_DATE
Must be > Grant Project Start Date
Type
FRBGRNT_GRANT_ TYPE
Validated against FTVSDAT
Category
FRBGRNT_CATEGORY
If not on FTVSDAT, field is set to null and process displays warning message. If null and new proposal and proposal code entered, default value is from proposal FRBPROP_CATEGORY.
November 2010
2-145

FRBGRNT_SUB_ CATEGORY
Column Comments
Error Consequences
Sub Category
If not on FTVSDAT, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal FRBPROP_SUB_CATEGORY.
CFDA Number
FRBGRNT_CFDA_ INTERNAL_ID_NO
Validated against FRVCFDA
If not on FRVCFDA, field is set to null and process displays warning message. If null and new grant and proposal code are entered, default value is from proposal FRBPROP_CFDA_ INTERNAL_ID_NO.
Sponsor ID
FRBGRNT_SPONSOR_ ID
If null and new grant and proposal code entered, default value is from proposal FRBPROP_SPONSOR_ID. Validated against FRBBASI If not on FRBBASI, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal
FRBPROP_BASI_CODE_IC.
Indirect Cost Basis Code
FRBGRNT_BASI_ CODE_IC
Indirect Cost Rate Code
FRBGRNT_INDR_ CODE_RATE
Validated against FRVINDR. Must be valued.
If not on FRVINDER, field is set to null and process displays warning messages. If null and new grant and proposal code entered, default value is from proposal FRBPROP_INDR_CODE_RATE.
2-146
November 2010

FRBGRNT_INDA_ CODE_CHARGE
Column Comments
Error Consequences
Indirect Cost Charge Code
Validated against FRBINDA. Must be valued.
If not on FRBINDA, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal FRBPROP_INDA_
CODE_CHARGE.
FRBGRNT_INDD_ Indirect Cost Distribute To Code CODE_DISTR
Validated against FRBINDD. Must be valued.
If not on FRBINDD, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal FRBPROP_INDD_CODE_DISTR.
Cost Share Basis Code
FRBGRNT_BASI_ CODE_CS
Validated against If not on FRBBASI, field is FRBBASI. Must be valued. set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal FRBPROP_BASI_CODE_CS.
Cost Share Rate Code
FRBGRNT_CSTR_ CODE_RATE
Validated against FRVCSTR. Must be valued.
If not on FRVCSTR, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal
FRBPROP_CSTR_CODE_RATE.
November 2010
2-147

FRBGRNT_CSTA_ CODE_CHARGE
Column Comments
Error Consequences
Cost Share Credit Code
Validated against FRBCSTA. Must be valued.
If not on FRBCSTA, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal FRBPROP_CSTA_ CODE_CHARGE.
Cost Share Distribution Code
FRBGRNT_CSTD_ CODE_DISTR
Validated against FRBCSTD. Must be valued.
If not on FRBCSTD, field is set to null and process displays warning message. If null and new grant and proposal code entered, default value is from proposal
FRBPROP_CSTD_CODE_DISTR.
The following fields are not defined on the collector table, but are defaulted to FRBGRNT during the interface process if an agency code was entered.

FRBGRNT_AGENCY_ CONTACT FRBGRNT_AGENCY_ ADDR_CODE FRBGRNT_AGENCY_ ADDR_SEQ_NUM FRBGRNT_AGENCY_ PHONE_TYPE FRBGRNT_AGENCY_ TELE_SEQNO FRBGRNT_AGENCY_ EMAIL
Column Comments
Error Consequences
Grant Code Required
Default value is from FTVAGCY Default value is from FTVAGCY. Default value is from FTVAGCY Default value is from FTVAGCY Default value is from FTVAGCY
Field is set to null, if

FRBGRNT_AGENCY_PIDM
is
null. Field is set to null, if

FRBGRNT_AGENCY_PIDM
is

FRBGRNT_AGENCY_PIDM
is

FRBGRNT_AGENCY_PIDM
is
null Field is set to null, if

FRBGRNT_AGENCY_PIDM
is

FRGRNT_AGENCY_PIDM
is null
2-148
November 2010
Grant Events Code Mapping (FRCEVNG to FRRBFIX) For new grants, Updating FRBEVNG occurs after FRBGRNT. Updating FRREVNG occurs after FRBENVG. Updating FRRPRXG occurs after FRBENVG. Updating FRRBFIX occurs after FRBENVG. If Event Header Information is entered, the process calculates the due date based on the number of days and the indicator or the frequency. The process uses that information to create the appropriate number of entries in the FRRENVG, FRRPRXG, and FRRBFIX. If Event Header information is being updated, the existing FRREVNG, FRRPRXG, and FRRBFIX records are deleted and new ones inserted based on the header data.

FRRBFIX_FUND_CODE
Column Comments
Error Consequences
Fixed Bill Fund
Validated against FTVFUND.
If invalid or null and if FRVEVNT_TYPE_IND=B and

FRBEVNT_PMT_METHOD_
Required if FRVEVNT_ TYPE_IND=F, process TYPE_IND=B and FRBEVNG_ displays error message. PMT_METHOD_TYPE_IND=F. Fixed Bill Amount FRRBFIX_AMOUNT Required if
FRRBFIX_FUND_CODE
is
valued.
If null or invalid and if FRRBFIX_FUND_CODE is valued, process displays error message.
The following fields are defaulted to FRRBFIX during the interface process. .
FRRBFIX_EVNT_CODE
Column Comments
Error Consequences
Default value is from FRBEVNG Default value is from FRBGRNT
FRRBFIX_COAS_CODE
November 2010
2-149
Grant Budget Lines Mapping (to FRRBUDG) Updating this table for new grants must occur after FRBGRNT. For new grants, the FRBBUDG table is updated before FRRBUDG. For existing grants, budget detail may not be updated. The FRRBUDG table will be updated after FRBBUDG. For additional information, refer to Grant Budget Header Mapping (to FRBBUDG and FRRBUDG) on page 2-132. FRRBUDG fields are not defined on the collector table but are defaulted during the interface process.
Note The interface duplicates sequence numbering logic found on FRABUDG. Sequence numbering logic is maintained by the system.

FRRBUDG_GRNT_CODE
Column Comments
Error Consequences
Grant Code Required Budget Code Required Account Code Required
Subject to same edits as FRBBUDG Subject to same edits as FRBBUDG Validated against FTVACCT. If not valid, if terminated, not active, or non-data-enterable, process displays error message.
FRRBUDG_GRNT_ BUDGET_CODE FRRBUDG_ACCT_CODE
Budget Amount Cost Share Amount
FRRBUDG_BUDGET_ AMT FRRBUDG_COST_ SHARE_AMT
If null, default value is 0. May be calculated if Job Submission Parameter to calculate = Y. If invalid, process displays an error message. If null, default value is from FRBBUDG_COAS_CODE_DEF.
Budget Chart Code FRRBUDG_COAS_CODE Validated against FTVCOAS
Budget Index Code FRRBUDG_ACCI_CODE Validated against FTVACCI
If invalid, process displays an error message. If null, default value is from FRBBUDG_ACCI_CODE_DEF.
2-150
November 2010
Column Comments
Error Consequences
Budget Fund Code FRBBUDG_FUND_CODE Validated against FTVFUND.
If null, default value is from FRBBUDG_FUND_CODE_DEF.
Validated for Fund Security If null and Budget Index only if Fund/Orgn Security Code entered, default value is from FTVACCI_FUND_CODE. turned on. Then, use the function. If not valid, if terminated, not active, or non-data-enterable, process displays an error message. If the user does not have update access for the fund code entered, process displays an error message.
FRBBUDG_ORGN_CODE Validated against Budget FTVORGN. Validated for Organization Code Organization Security.
If null, default value is from FRBBUDG_ORGN_CODE_DEF. If null and Budget Index Code entered, default value is from FTVACCI_ORGN_CODE. If not valid, if terminated, not active, or non-data-enterable, process displays error message. If the user does not have update access for the Org code entered, process displays an error message.
Budget Program Code
FRRBUDG_PROG_CODE
Validated against FTVPROG
If null, default value is from FRBBUDG_PROG_CODE_DEF. If null and Budget Index Code entered, default value is from FTVACCI_PROG_CODE. If not valid, if terminated, not active, or non-data-enterable, process displays error message.
November 2010
2-151

FRRBUDG_ACTV_CODE
Column Comments
Error Consequences
Budget Activity Code
Validated against FTVACTV
If null, default value is from FRBBUDG_ACTV_CODE_DEF. If null and Budget Index Code entered, default value is from FTVACCI_ACTV_CODE. If not valid, if terminated, not active, or non-data-enterable, field is set to null and process displays warning message.
Budget Location Code
FRRBUDG_LOCN_CODE
Validated against FTVLOCN
If null, default value is from FRBBUDG_LOCN_CODE_DEF. If null and Budget Index Code entered, default value is from FTVACCI_LOCN_CODE. If not valid, if terminated, not active, or non-data-enterable, field is set to null and process displays warning message.
Grant Events Code Mapping (FRCEVNG to FRREVNG) For new grants, Updating FRBEVNG occurs after FRBGRNT. Updating FRREVNG occurs after FRBENVG. Updating FRRPRXG occurs after FRBENVG. Updating FRRBFIX occurs after FRBENVG. If Event Header Information is entered, the process calculates the due date based on the number of days and the indicator or the frequency. The process uses that information to create the appropriate number of entries in the FRRENVG, FRRPRXG, and FRRBFIX. If Event Header information is being updated, the existing FRREVNG, FRRPRXG, and FRRBFIX records are deleted and new ones inserted based on the header data.
2-152
November 2010

FRREVNG_ RESPONSIBLE_USER_ ID
Column Comments
Error Consequences
Responsible User Id
Validated against FOMPROF
If invalid, process displays error message.
The following fields are defaulted to FRREVNG during the interface process.

FRREVNG_GRNT_CODE
Column Comments
Error Consequences
Default value is from FRBEVNG Default value is from FRBEVNG System-generated 1-up number based on the frequency of the events. Defaults to P Calculated based on the frequency Field is set to null. Field is set to null.
FRREVNG_EVNT_CODE
FRREVNG_SEQ_NUM
FRREVNG_STATUS_ IND FRREVNG_DUE_DATE
FRREVNG_APPROVED_ BY_USER_ID FRREVNG_STATUS_ DATE
Grant Location Information Mapping (FRCGLOC to FRRGLOC) Updating this table occurs after FRBGRNT. Location mapping information is optional. A collector table is not required to include any location information. If included, it must then contain the required fields. Appropriate edits and validations take place prior to mapping. If this is a new grant and proposal code entered for FRBGRNT, default all location information from the proposal. If any location information is entered in the interface table, the data entered are used to override what has been defaulted from the proposal.
November 2010
2-153

FRRGLOC_GRNT_CODE
Column Comments
Error Consequences
Grant Code Required Location Code Required Location Code Indicator Required
Subject to same edits as FRBGRNT Validated against FTVLOCN Must be C, O, or B If invalid, process displays an error message. If invalid, process displays an error message.
FRRGLOC_LOCN_CODE
FRRGLOC_LOCN_ RESEARCH_IND
Grant Personnel Information Mapping (FRCGRPI to FRRGRPI) Updating this table follows the update of FRBGRNT. PI mapping information is optional. The collector table is not required to include any PI information. If included, it must then contain the required fields. Appropriate edits and validations take place prior to mapping.
Temp. Table Column Name

FRRGRPI_GRNT_CODE
Column Comments
Error Consequences
Grant Code Required PI Organization Code PI Indicator Required with PI ID
Subject to same edits as

FRBGRNT_CODE
FRRGRPI_ORGN_CODE
Validated against FTVORGN Validated against FTVSDAT. If this field is valued to 001, system updates FRBGRNT_PI_PIDM.
If not on FTVORGN, field is set to null and process displays warning message. If not on FTVSDAT, process displays error message.
FRRGRPI_ID_IND
PI ID Number Required PI Salutation PI Title PI FTE
FRRGRPI_ID_PIDM
Locate ID in SPRIDEN to determine PIDM
If not on SPRIDEN, process displays error message.
FRRGRPI_ SALUTATION FRRGRPI_TITLE FRRGRPI_FTE
2-154
November 2010

FRRGRPI_EMPLOYEE_ IND
Column Comments
Error Consequences
Locate PIDM in PEBEMPL. Value of Y is defaulted if PI Id is an active employee. Validated against STVATYP If invalid, field is set to null and process displays warning message.
Address Type
FRRGRPI_ADDR_TYPE
Address Sequence Number
FRRGRPI_ADDR_ SEQNO
Required if Address Type is If null, and address type is entered. entered, address type is set to null, and process displays warning message. Validated against STVTELE Required if Phone Type is entered If invalid, field is set to null and process displays warning message If null and phone type is entered, address type is set to null, and process displays warning message. If invalid, field is set to null. Process displays warning message.
Phone Type
FRRGRPI_PHONE_ TYPE
Telephone Sequence Number
FRRGRPI_TELE_ SEQNO
Billing/Report Format Code
FRRGRPI_BFRM_CODE
Validated against FTVBFRM
Grant Events Code Mapping (FRCEVNG to FRRPRXG) For new grants, Updating FRBEVNG occurs after FRBGRNT. Updating FRREVNG occurs after FRBENVG. Updating FRRPRXG occurs after FRBENVG. Updating FRRBFIX occurs after FRBENVG. If Event Header Information is entered, the process calculates the due date based on the number of days and the indicator or the frequency. The process uses that information to create the appropriate number of entries in the FRRENVG, FRRPRXG, and FRRBFIX. If
November 2010
2-155
Event Header information is being updated, the existing FRREVNG, FRRPRXG, and FRRBFIX records are deleted and new ones inserted based on the header data.

FRRPRXG_PROXY_ USER_ID
Column Comments
Error Consequences
Proxy User ID
Validated against FOMPROF
If invalid, process displays warning message.
The following fields are defaulted to FRRPRXG during the interface process.

FRRPXRG_GRNT_CODE
Column Comments
Error Consequences
Default value is from FRBEVNG Default value is from FRBEVNG System-generated 1-up number based on the frequency of the events Defaults to P Calculated based on the frequency Field is set to null Field is set to null
FRRPXRG_EVNT_CODE
FRRPRXG_EVNT_SEQ_ NUM
FRRPXRG_STATUS_ IND FRRPXRG_DUE_DATE
FRRPXRG_APPROVED_ BY_USER_ID FRRPXRG_STATUS_ DATE
Grant User Defined Codes Mapping (FRCGUSN to FRRGUSN) Updating this table occurs after FRBGRNT. User-defined information mapping is optional. A collector table is not required to include any user-defined fields information. If included, it must then contain the required fields. Appropriate edits and validations take place prior to mapping.
2-156
November 2010

FRBGUSN_GRNT_CODE
Column Comments
Error Consequences
Grant Code Required * Literal * Value
Subject to same edits as FRBGRNT Validated against FRVSDAT Validated against FRVSDAT If invalid, process displays a warning message. If invalid, process displays a warning message.
FRRGUSN_SDAT_ CODE_ATTR FRRGUSN_SDAT_ CODE_OPT_1
* If either the Literal or Value field is populated, the other must also exist. Grant Status History Mapping (to FRVGRST) These fields are not defined on the collector table, but are defaulted during the interface process when a Grant Status Code and Grant Status Date are valued in the collector table.

FRVGRST_GRNT_CODE FRVGRST_STATUS_ CODE FRVGRST_COAS_CODE
Column Comments
Error Consequences
Same as FRBGRNT_CODE Same as

FRBGRNT_STATUS_CODE
Same as
FRBGRNT_COAS_CODE
FRVGRST_DATE_ STATUS
Same as
FRBGRNT_STATUS_DATE
Finance Operations
Currency Conversion
Banner Finance provides the option of dealing with foreign vendors and maintaining cash accounts in foreign currencies. The base currency for the entity, referenced on the General Control Table (GUBINST), is used in all foreign currency calculations. Maintain the currency codes, with daily or periodic rates, using the Currency Table Maintenance Form (GUACURR). The Accounts Receivable, Purchasing and Procurement, Accounts Payable, and General Ledger modules use the foreign currency calculation feature.
November 2010
2-157
Unless otherwise specified, the amounts input will be in the installation's base currency and referenced on the Installation Control Form (GUAINST). When dealing with a foreign vendor, you may enter a currency code in the Currency Code field. Use the List function to display the valid currency codes. For additional information about currency conversion, refer to the following sections: Defining Currency Conversion Values on page 2-158 Currency Conversion by Module on page 2-158 Currency Conversion for Journal Vouchers on page 2-159 Currency Conversion Checklist on page 2-160 Currency Codes and Conversion on page 2-264 (Invoice Processing section)
Defining Currency Conversion Values

To process documents in a foreign currency, certain values must exist on the Currency Conversion Table (GTVCURR). Access the Currency Code Maintenance Form (GUACURR) from the System Functions/Administration Menu (*GENSYS). A valid currency code must be previously defined; for example, DM for Deutsche Marks. As mentioned in the Currency Conversion Overview, you have the option to produce checks in foreign currencies or using disbursing agents. For those currencies for which the installation is going to produce checks directly, there must be a unique Accounts Payable Account and Exchange Account as well as a separate Bank Code. When you use disbursing agents, the system records the foreign amounts throughout the procurement process but will produce a summary check to the disbursing agent using the Disbursement Check Report (FABCHKD) which lists the foreign vendors, the currency used, and the amount in the foreign currency for use by the disbursing agent in preparing individual checks. For currencies handled in this manner, there is no need for unique Accounts Payable Accounts and Exchange Accounts but there must be a Disbursing Agent ID (on FTMVEND). The system considers disbursing agents as vendors. Establish disbursing agents using the Vendor Maintenance Form (FTMVEND) before they are entered on the Currency Code Maintenance Form.
Currency Conversion by Module

Banner Finance enables you to deal with foreign vendors and to maintain cash accounts in foreign currencies. Use the base currency for the entity, which you reference on the Installation Control Form (GUAINST), in all foreign currency calculations. Maintain one and only one base currency for the entity. Maintain the currency codes, with daily or periodic rates, on the Currency Table Maintenance Form (GUACURR). Use the currency conversion feature in the following modules.
2-158
November 2010
Purchasing and Procurement You can specify a foreign currency on requisitions and purchase orders. The system retrieves the appropriate rate from the currency conversion table and converts the input amount (in the foreign currency) to the converted amount for posting purposes. In other words, the system maintains the encumbrances in the base currency of the installation. Accounts Payable As with requisitions and purchase orders, you can process invoices and write checks in a foreign currency. The system posts the converted amount, along with the exchange amount (the difference between the foreign or input amount and the converted or base currency amount). An additional feature in the Accounts Payable module provides the option to use a disbursing agent for foreign vendor activity. This is useful in cases in which the bank is to produce checks to foreign vendors. If a disbursing agent handles a currency transaction, the system accumulates the foreign currency transactions for a specific check run, and writes a check to the disbursing agent in the base currency. In addition, the system produces the Disbursement Check Report (FABCHKD) which identifies the vendors with the foreign currency amounts so that the bank can write the appropriate checks. In these cases, you do not need to calculate or post an exchange amount. General Ledger To record purchases of foreign currency, you may reference a foreign currency on the journal voucher. Refer to the online help for details on the Journal Voucher Entry Form (FGAJVCD), the Journal Mass Entry Form (FGAJVCM), and the Journal Voucher Quick Form (FGAJVCQ). Accounts Receivable You can record cash receipts in a foreign currency.
Currency Conversion for Journal Vouchers

To record purchases of foreign currency, reference a foreign currency on FGAJVCD. Enter an existing document number in the Document Number field for an encumbrance on FGAJVCD, enabling you to liquidate a purchase order using FGAJVCD. This is useful for liquidating remaining balances on purchase orders for which proper liquidation through invoice processing did not occur. If this is final payment, the system populates the Partial Payment Indicator on the invoice with a T at the time of invoice processing.
November 2010
2-159
Currency Conversion Checklist

Follow the steps below to ensure that your system processes Currency Conversion correctly:
1. Determine which foreign currencies are to be used by the installation. 2. Decide which are to be handled by disbursing agents and which currency balances
will be handled by the installation.

3. For currencies which are handled by disbursing agents:
Set up a Vendor code for the disbursing agent on the Vendor Maintenance Form (FTMVEND). Set up a cash account for the balance the installation wants to maintain in the Bank Fund for these transactions on the Account Code Maintenance Form (FTMACCT). Set up a disbursing agent bank on the Bank Code Maintenance Form (GXRBANK) so that you can generate checks for foreign vendors in a separate batch job and produce the appropriate report for the disbursing agent to use. Ensure that the Accounts Payable Account and Exchange Accounts are the same as are used for the regular operations which occur in the base currency.
4. For currencies which are maintained by the installation where checks will be
produced in the foreign currency: Set up a cash account for each foreign currency in the Bank Fund. Set up a separate bank account for each foreign currency on the Bank Code Maintenance Form (GXRBANK). Note that there is a Base Currency field on GXRBANK. Use future effective dates when setting up currency information. After establishing the currency codes, update the bank code record with the appropriate currency. Set up unique Accounts Payable Account and Exchange Accounts (asset or liability) for each currency on the Account Code Maintenance Form (FTMACCT).
5. Create your currency records using the Currency Code Maintenance Form
(GUACURR). Within Purchasing, when you enter a foreign currency, the system calculates converted amounts for use in available balance checking and posting. Record the purchase of the foreign currency itself with a simple journal entry in the Bank Fund. Use the JE15 Rule Class. Enter a credit entry to the account in the bank fund used to purchase the foreign currency. Debit the cash account used to maintain the balance of the specific foreign currency (referenced on the Currency Code Maintenance Form, GUACURR); debit/credit the difference to the exchange account (also GUACURR).
2-160
November 2010
Identifying Persons and Entities in Banner Finance

When you add a person or entity into the Banner Finance database, the system establishes an ID and an internal Personal Identification Number (PIDM). An entity could be a corporation, a bank, a university, a government agency, or a business. Generally, you define IDs through ID or Key ID fields of the forms you are using to add persons or entities to the database. IDs display on forms and reports. You may modify ID numbers over time. You have the capability of allowing the system to generate a sequential number for the person or entity you are adding to the system. The system bases generated ID numbers on the values defined on the Sequence Number Maintenance Form (FOASEQN). The PIDM is an internal and unique system-generated eight-digit number stored on the Person Identification Table (SPRIDEN). Every person and entity defined to the database, regardless of what form is used to define them, has a PIDM on the SPRIDEN table. The PIDM does not display on forms or reports. Once the system creates a PIDM, you cannot modify it.
Adding Persons or Entities to Banner Finance With the Identification Form (FOAIDEN)
Generally, you add persons and entities to the Banner Finance database using the Identification Form (FOAIDEN). FOAIDEN provides you with the capability of assigning system-generated or user-defined ID numbers. Once you define person/entity information on this form, you may modify it. When you save persons/entities to the database, the system creates their PIDM(s). The ID field on FOAIDEN is required. Enter NEXT to have the system generate a sequential ID number. Use existing IDs to display and change a record, or add an ID to the system. Select Next Block to go to the Current Identification Information. Notice that the value you entered in Key ID field defaults to the ID field in the Current Identification Information. You cannot supply both person and non-person name information under the same ID.
November 2010
2-161
Searching the Database for Entities With the Non-Person Name/ID Search Form (FOICOMP)
The Non-Person Name/ID Search Form enables you to query all the entities (non-persons) in the database. This form is in query mode when it is displayed.
1. From the ID field on FOAIDEN, select Count Query Hits to access the Non-Person
Name/ID Search Form (FOICOMP).

2. Select Next Block to execute a query of every entity and ID Number in the database.
The entity names display in alphabetical order.

3. Enter a possible spelling of the name you want in the Name field to narrow your
search. If you enter a partial name, use a percent sign (%) as a wild card. This tells the system that you want to view all names containing the letter combination you specify. For example, you can enter %ton to view all names ending in -ton, And% to view all names beginning with And-, or %bel% to view all names containing the -bel- letter combination.
4. Select Next Block to execute the query. 5. Position the cursor on the value you wish to display on the Identification form. Click
or select Exit from that field to populate the Identification form with the ID in the ID field.
Searching the Database for Persons with the Person Name/ ID Search Form (FOIIDEN)
This form enables you to query all the persons (non-entities) in the database. You are in query mode when this form is displayed.
1. From the ID field on FOAIDEN, select List to access the Person Name/ID Search
Form (FOIIDEN).
2. Select Next Block to execute a query of every person and ID Number in the database.
The entity names display in Last Name alphabetical order.

3. Enter a possible spelling of the name you want in the Last Name Prefix, Last Name,
and/or First Name fields to narrow your search. The system conducts the search based on one or both values as specified. If you enter a partial name, use a percent sign (%) as a wild card. This tells the system that you want to view all names containing the letter combination you specify. For example, you can enter %ton to view all names ending in -ton, And% to view all names beginning with And-, or %bel% to view all names containing the -bel- letter combination.
4. Select Next Block to execute the query.
2-162
November 2010
5. Position the cursor on the value you wish to display on the Identification Form
(FOAIDEN). Select Exit from that field to populate the Identification form with the ID in the ID field.
6. Select Next Block from the Current Identification Information after you enter the
required names. The Alternate Identification Information is display only. If you make changes to existing person or entity names, data displays in this block.
7. Select Next Block to access the Address Information.The following are required
fields and allowable values: Type: Enter the Address Type for this individual. The system validates address types using the Address Type Code Validation Form (STVATYP). Select List to display STVATYP. Position the cursor on the value you wish to display in the Type field. Select Exit from that field to display FOAIDEN with that value in the Type field. Select Next Item. Validation forms initially display in window format when you click or select List. Select Next Block once the window displays to go to the validation form. Street Line 1: This is the first line of the address for this individual. Enter at least one line in an address. You may enter up to four address lines. For a person or entity, you may define one address for each address type. If multiple addresses exist in the database, you may scroll through them here. When you save these addresses, the system assigns a sequence number in the Sequence Number field. Sequence numbers specifically identify addresses within address types. Select Next Record within the Address Information to add addresses and address types. City: The city line in the address. Enter the city name, up to 20 characters. Select Next Item. State or Province or Nation: Populate the appropriate fields according to your site policies. The system validates state or province codes using the State/Prov Code Validation Form (STVSTAT). Select List to display STVSTAT. The system validates nation codes using the Nation Code Validation Form (STVNATN). Position the cursor on the value you wish to display in the State or Province or Nation field. Select Exit from that field to display FOAIDEN with that value in the State or Province or Nation field. Select Next Item. ZIP or Postal Code: The ZIP or Postal Code in the address. The system validates ZIP or Postal Code using the ZIP/Postal Code Validation Form (GTVZIPC). Select List to display GTVZIPC. Position the cursor on the value you wish to display in the ZIP or Postal Code field. Select Exit from that field to display FOAIDEN with that value in the ZIP or Postal Code field.
November 2010
2-163
Depending on your sites policies, the ZIP or Postal Code value may default the corresponding city, state/prov, nation, and county codes. If your site uses the default feature, go to the ZIP or Postal Code field. Enter the ZIP or Postal Code and select Next Item to invoke the default feature.
8. Select Next Block when the pop-up window appears to display the entire validation
form.
9. The address type defaults to the Telephone Type field. You may override the default.
The system validates phone types using the Telephone Type Validation Form (STVTELE). Select List to display STVTELE. Position the cursor on the value you wish to display in the Telephone Type field. Select Exit from that field to display FOAIDEN with that value in the Telephone Type field.
10. Select Save.
Adding Vendors to Banner Finance

The Vendor Maintenance Form (FTMVEND) enables you to add individuals to the database identified as vendors. Use FTMVEND to define persons and corporations as vendors. FTMVEND also enables you to identify persons already defined to the SPRIDEN table as vendors. Select List from the Vendor field to access the Entity Name/ID Search Form (FTIIDEN). FTIIDEN is useful if you are defining an individual or a corporation as a vendor.
Searching the Database for Vendors

FTIIDEN allows you to query persons/entities defined to the database. This form is in query mode when you access it.
1. If you know the ID number of the vendor, enter it in the ID field. 2. You may enter a partial name with a wildcard (%) or the entire last name in the Last
Name field. Enter values in the Last Name Prefix, First Name, and Middle Name fields to narrow the search.
3. The Entity Ind field is an entity indicator. To narrow the search, enter P (Person) or
C (Corporation). This form enables you to exit with a person or entity ID number.
4. The Change Ind field is a change indicator. The system defaults N (Name change) or
I (Identification change) into this field based upon the last change made to this ID. You may also populate this field before executing a query. The only form in the Banner Finance System from which you can change IDs and names is the Identification Form (FOAIDEN).
2-164
November 2010
5. Enter Y (Yes) in any of the indicator fields to narrow your search. For example, enter
Y in the V (Vendor) Indicator.

6. Execute the query to display individuals previously defined as vendors. You may
enter A (All) in any of these indicators to display all the persons/entities defined to that category. The system defaults Y or N in the remaining indicator fields, as appropriate. If no query information is entered, the system defaults vendors.
7. Select Exit to display an ID number in the Vendor field.
Using the Vendor Maintenance Form (FTMVEND)

Identifying a Vendor as a Corporation 1. Enter a one- to nine-character ID in the Vendor field for the vendor being established,
or select Generate ID to have the system generate a sequential ID.

2. Select Next Item and enter from one to 60 characters describing the Corporation.
You may define either Corporation or Last Name Prefix, Last Name, First Name, and Middle Name.
3. Select Next Block to continue. Identifying a Vendor as an Individual 1. Enter a one- to nine-character ID in the Vendor field for the vendor being established,
or select Generate ID to have the system generate a sequential ID.

2. Select Next Item twice to bypass Corporation. 3. Optionally enter from one to 60 characters in the Last Name Prefix field. Select Next
Item and enter from one to 60 characters in the Last Name field. Select Next Item and enter from one to 60 characters in the First Name field. Select Next Item and enter from one to 60 characters in the Middle Name field.
4. Select Next Block. 5. Enter the following are required fields on FTMVEND:
Dates: Enter the dates that this record is in effect. Use the DD-MON-YYYY format. Leave these fields blank to default the system date. Collects Taxes: Populate this field according to your site policies. This field designates which compensating or use taxes the system collects. You may choose to collect all taxes, no taxes, or selected taxes. If you define Selected taxes, enter Tax Code(s) in the Taxes Collected Window of FTMVEND.
November 2010
2-165
6. To enter further information for a vendor, including tax data, select the Vendor
Header Additional Information Window from the Options menu. OR Select Next Block to display the Vendor Types Window.
7. Enter the Vendor Types Code. This field accepts one or two characters. The system
validates vendor type codes using the Vendor Type List Values Form (FTVVTYP). Select List to select a vendor type from a list window. Position the cursor on the value you wish to display in the Vendor Types Code field. Select Exit to display FTMVEND with that value in the Vendor Types Code field.
8. Select Next Block to display the Vendor Address Window. The cursor resides in the
Address Type Code field.

9. Enter the following:
Address Type Code: Enter the address code for this vendor. The system validates address types using the Address Type Code Validation Form (STVATYP). Select List to select an address type from a list window. Position the cursor on the value you wish to display in the Address Type Code field. Select Exit from that field to display FTMVEND with that value in the Address Type Code field. Select Next Item. Sequence Number: You may define more than one address to a single address type. If you only define one address, that address must have an assigned sequence number. As you add addresses, you must assign sequence numbers. Sequence numbers must be unique within address types.
Adding Financial Managers to Banner Finance

The Financial Manager Maintenance Form (FTMFMGR) enables you to add persons identified as financial managers to the Person Identification Table (SPRIDEN) and the Person Address Table (SPRADDR). FTMFMGR also enables you to identify persons already defined to the SPRIDEN table as financial managers. Enter only persons, not entities, into the system using FTMFMGR. When you enter Select List from the Financial Manager field to access the Entity Name/ID Search Form (FTIIDEN).
2-166
November 2010
Searching the Database for Persons

FTIIDEN allows you to query persons/entities defined to the database.
1. If you know the ID number of the person, enter it in the ID field or select Generate ID
to access the Common Matching Entry Form (GOAMTCH).

2. You may enter a partial name with a wildcard (%) or the entire last name in the Last
Name field. You may enter values in the Last Name Prefix, First Name, and Middle Name fields to narrow the search.
C (Corporation). This form enables you to query entities, but you may not exit the form with an entity ID to FTMFMGR.
I (Identification change) into this field based upon the last change made to this ID. You may also populate this field before executing a query. The only form in the Banner Finance System from which you may change IDs and names is the Identification Form (FOAIDEN).
Y in the F (Financial Manager) Indicator. Execute the query to display individuals previously defined as financial managers. You may enter A (All) in any of the indicators to display all the persons/entities defined to that category. The system defaults Y or N in the remaining indicator fields, as appropriate. If no query information is entered, the system defaults vendors.
6. Select Exit to display an ID identifying a vendor, financial manager, agency or
investment manager provided you did not originally define them to the database as corporations. You may have defined the original ID record using FOAIDEN, the Vendor Maintenance Form (FTMVEND), the Agency Code Maintenance Form (FTMAGCY), or the Investment Manager Maintenance Form (FTMIMGR).
Using the Financial Manager Maintenance Form (FTMFMGR)

You may enter a one- to nine-character ID number in the Financial Manager field for a financial manager being established. Select Generate ID to have the system generate a sequential ID number. Enter from one to 60 characters describing the financial manager (for example, company name, job title) in the field to the right of the Financial Manager field. Select Next Block. Manager Information The following are the required fields in the Manager Information and allowable values:
November 2010
2-167
Status: Valid entries are A(Active) and I(Inactive). The default is A. Title: Enter from 1 to 35 characters describing the job title of the financial manager you establish. Effective Date: Enter the date that this record is in effect. Use the DD-MONYYYY format. Leave this field blank to default the system date. You may choose to define the organization and location information based on your site policies. The system validates the Default Address Type using the Address Type Code Validation Form (STVATYP). The system supplies a Sequence Number and Last Activity Date. Select Next Block. Address Information The following are the required fields in the Address Information and allowable values: Address Type: Enter the address type for this individual. The system validates address types using the Address Type Code Validation Form (STVATYP). Validation forms initially display in window format when you select List. Select Next Block once the window displays to go to the validation form. Select List to access STVATYP. Position the cursor on the value you wish to display in the Type field. Select Exit from that field to populate FOAIDEN with that value in the Type field. Select Next Item. Sequence Number: You may define more than one address to a single address type. If you only define one address, that address must have an assigned sequence number. As you add addresses, you must assign sequence numbers. Sequence numbers must be unique within address types. Street Line 1: This is the first line of the address for this individual. Enter at least one line in an address. You may enter up to four address lines. You may define multiple address types and multiple addresses for each address type for a financial manager. City: The city line in the address. Enter the city name, up to 20 characters. Select Next Item. State or Province or Nation: Populate the appropriate fields according to your site policies. The system validates state or province codes using the State/Province Code Validation Form (STVSTAT). Select List to display STVSTAT. The system validates nation codes using the Nation Code Validation Form (STVNATN). Position the cursor on the value you wish to display in the State or Province or Nation field. Select Exit from that field to populate FTMFMGR with that value in the State or Province or Nation field. Select Next Item. ZIP or Postal Code: The ZIP or Postal Code in the address. The system validates ZIP or Postal Code using the ZIP/Postal Code Validation Form (GTVZIPC). Select List to display GTVZIPC. Position the cursor on the value you wish to display in
2-168
November 2010
the ZIP or Postal Code field. Select Exit from that field to display FOAIDEN with that value in the ZIP or Postal Code field. Depending on your site's policies, the ZIP/Postal Code value may default the corresponding city, state/prov, nation, and county codes. If your site uses the default feature, go to the ZIP/Postal Code field. Enter the ZIP/Postal Code and select Next Item to invoke the default feature. The address type defaults to the Telephone Type field. You may override the default. The system validates phone types using the Telephone Type Validation Form (STVTELE). Select List to display STVTELE. Position the cursor on the value you wish to display in the Telephone Type field. Select Exit from that field to access FTMFMGR with that value in the Telephone Type field. Select Save.
Adding Agencies to Banner Finance

The Agency Code Maintenance Form (FTMAGCY) enables you to add agencies and contacts to the database. You may define persons and corporations as agencies. FTMAGCY enables you to identify persons and corporations already defined to the SPRIDEN table as agencies. Select List from the Agency field of FTMAGCY to access the Entity Name/ID Search Form (FTIIDEN).
Searching the Database for Agencies

FTIIDEN allows you to query agencies defined to the database.
1. If you know the ID number of the agency, enter it in the ID field or select Generate
ID to access the Common Matching Entry Form (GOAMTCH).

2. You may enter a partial name with a wildcard (%) or the entire last name in the Last
Name field. Enter values in the Last Name Prefix, First Name, and Middle Name fields to narrow the search. Remember, agencies can be persons.
C (Corporation). This form enables you to exit with a person or entity ID number.
I (Identification change) into this field based upon the last change made to this ID. You may also populate this field before executing a query. The only form in the Banner Finance System from which you may change IDs and names is the Identification Form (FOAIDEN).
Y in the A (Agency) Indicator. Execute the query to display previously defined agencies. You may enter A (All) in any of the indicators to display all the persons/entities defined to that category. The system defaults Y or N into the
November 2010
2-169
remaining indicator fields, as appropriate. If no query information is entered, the system defaults vendors.
6. Select Exit to display an ID in the Agency field.
Using the Agency Code Maintenance Form (FTMAGCY)

You may enter a one-to-nine character ID number in the Agency field for a person/agency you wish to establish. Select Generate ID to have the system generate a sequential ID number. Enter from one to 60 characters describing the agency in the field to the right of the Agency field. Select Next Block. The Active Status field is required. Check the box for Active Status or uncheck the box for Inactive Status. The default is checked (Active). The Contact at the agency is optional. You may define agencies in hierarchies. The Banner Finance sample data provides you with a level one agency hierarchy. The following are the required fields in the Address Information and allowable values: Address Type: Enter the address type for this agency. The system validates address types using the Address Type Code Validation Form (STVATYP). Validation forms initially display in window format when you select List. Select Next Block once the window displays to go to the validation form. Select List to display STVATYP. Position the cursor on the value you wish to display in the Address Type field. Select Exit from that field to populate FTMAGCY with that value in the Address Type field. Select Next Item. Sequence Number: You may define more than one address to a single address type. If you only define one address, that address must have an assigned sequence number. As you add addresses, you must assign sequence numbers. Sequence numbers must be unique within address types. City: The city line in the address. Enter the city name, up to 20 characters. Select Next Item. State or Province or Nation: Populate the appropriate fields according to your site policies. The system validates state or province codes using the State/Province Code Validation Form (STVSTAT). Select List to display STVSTAT. The system validates nation codes using the Nation Code Validation Form (STVNATN). Position the cursor on the value you wish to display in the State or Province or Nation field. Select Exit from that field to access FTMAGCY with that value in the State or Province or Nation field. Select Next Item. ZIP or Postal Code: The ZIP or Postal Code in the address. The system validates ZIP or Postal Code using the ZIP/Postal Code Validation Form (GTVZIPC). Select List to display GTVZIPC. Position the cursor on the value you wish to display in
2-170
November 2010
the ZIP or Postal Code field. Select Exit from that field to access FOAIDEN with that value in the ZIP or Postal Code field. Depending on your site's policies, the ZIP or Postal Code value may default the corresponding city, state or province, nation and county codes. If your site uses the default feature, go to the ZIP or Postal Code field. Enter the ZIP or Postal Code and select Next Item to invoke the default feature. The address type defaults to the Telephone Type field. You may override the default. The system validates phone types using the Telephone Type Validation Form (STVTELE). Select List to display STVTELE. Position the cursor on the value you wish to display in the Telephone Type field. Select Exit from that field to display FTMAGCY with that value in the Telephone Type field. Select Save.
Adding Customers to Banner Finance

The Customer Maintenance Form (FTMCUST) enables you to identify existing IDs as customers. You may define persons or corporations as customers. Select List from the Customer field of FTMCUST to access the Customer Code List Values Form (FTVCUST). FTVCUST is most useful when you are using the Cost Accounting module. Individuals defined as customers must exist in the database before being entered on FTMCUST. Add customers to Banner Finance using the Identification Form (FOAIDEN) if the individual does not already exist as another person type in the system. FOAIDEN provides you with the capability of assigning system-generated or user-defined ID numbers. Once you define the customer information on this form, you may modify it.
Adding Employees to Banner Finance

The Employee Maintenance Form (FCAEMPL) enables you to identify existing IDs as employees. Select List from the Employee Number field of FCAEMPL to access the Employee Code List Form (FCVEMPL). FCVEMPL is most useful when you are using the Cost Accounting module. Individuals defined as employees must exist in the database before being entered on FCAEMPL. Add employees to Banner Finance using the Identification Form (FOAIDEN). FOAIDEN enables you to assign system-generated or user-defined ID numbers. Once you define the customer information on this form, you may modify it. When you save customer IDs to the database, a PIDM is also created. Access the Employee Maintenance Form (FCAEMPL). Enter the ID you just created on FOAIDEN in the Employee Number field. List is available for this field but only employees defined to the Cost Accounting module appear. Select Next Item to display the employee name. Select Next Block to go to the Detail Information.
November 2010
2-171
Wages: Enter the employee's annual wages up to 13 digits. The system supplies the decimal point and zeros if the sum is even. Enter the decimal point and the cents if the sum is not even. To successfully add an employee record, you must save at least one field. COA: Enter the one-character chart of accounts code to which this employee is being established. The system validates Chart of Accounts using the Chart of Accounts List Form (FTVCOAS). Select List to access FTVCOAS. Position the cursor on the value you wish to display in the COA field. Select Exit from that field to access FCAEMPL with that value in the COA field. Select Next Item. You may enter only one organization and classification. Organization: Enter from one-to-six characters identifying the organization being established. The system validates organization codes using the Organization Code List Form (FTVORGN). Select List to access FTVORGN. Position the cursor on the value you wish to display in the Organization field. Select Exit from that field to access FCAEMPL with that value in the Organization field. Select Next Item. Classification: Enter from one to four characters identifying the classification (job description) being established. The system validates classification codes using the Classification Code List Form (FTVCLAS). Select List to access FTVCLAS. Position the cursor on the value you wish to display in the Classification field. Select Exit from that field to access FCAEMPL with that value in the Classification field. Select Next Item to display the code description. Enter only one organization and classification within the organization. Click or select Save.
ID Definition Tables
The following tables are accessed when you define persons and entities to the Banner Finance database: Person Identification Table (SPRIDEN) Person Address Table (SPRADDR) Agency Validation Table (FTVAGCY) Customer Table (FTVCUST) Employee Table (FCBEMPL) Financial Manager Validation Table (FTVFMGR) Vendor Validation Table (FTVVEND)
2-172
November 2010
ID and PIDM Relationship

Customers and Employees must have pre-existing Personal Identification Numbers (PIDMs) defined in the Person Identification Table (SPRIDEN)
Entity
Form
- Table
Employee - FCAEMPL - FTVEMPL Customers - FTMCUST - FTVCUST
IDs and PIDMs added through Finance Maintenance Forms and identified as:
SPRIDEN Contains all the database PIDMs
IDs are the links to PIDMs
Entity -
Form -
Table
Agency - FTMAGCY - FTVAGCY Finance Manager - FTMFMGR - FTVFMGR Vendor - FTMVEND - FTVVEND
SPRIDEN stores the most current record for PIDMs that have been modified.
Identification Form (FOAIDEN) Provides you with the ability to create and maintain both person and non-person IDs and names.
IDs established here initiate creation of a PIDM record.
Person Address Table (SPRADDR) Contains all the addresses for PIDMs
Receiving/Matching Processing
Receiving/Matching
The Receiving/Matching feature enables you to control the payment of invoices pending receipt of goods. The System Control Maintenance Form (FOASYSC) and the User Profile Maintenance Form (FOMPROF) contain the fields you populate to establish the Receiving/Matching control parameters.
November 2010
2-173
Receiving Feature
On FOMPROF, Receiving Overage Tolerance and Receiving Override pertain to users who receive goods using the Receiving Goods Form (FPARCVD). These fields enable you to control overshipments or duplicate shipments from vendors. Receiving Overage Tolerance Field Enter the percentage in excess of the ordered quantity that the user has the authority to accept, into the Receiving Overage Tolerance field. Your site procedures might authorize a receiving clerk to receive up to 10% over the ordered quantity. Quantities over that limit require further investigation involving Purchasing or other personnel. The receiving clerk will still be able to receive the goods, but the system considers the packing slip document in suspense and flags the document as an exception in the Receiving/Matching Process (FABMATC). Receiving Override Field Depending on site procedures, one method for handling the Receiving Overage condition is to override the suspense flag. Enter Y in the Receiving Override field for those users, typically a supervisor, who have the authority to override a suspense as the result of an overshipment.
Invoicing Feature
Enter the dollar threshold for paying invoices without evidence of receipt in the Invoice Amount Requiring Receipt field of the System Control Maintenance Form (FOASYSC). This is the dollar amount for which the system requires receiving information to pay the invoice. All invoices that reference Standing types of purchase orders bypass the Receiving/ Matching Process, despite the invoice amount. The Receiving/Matching Process uses the quantity of a commodity to match an item for payment. Standing type purchase orders use only dollar amount, not quantity. The Invoice Overage Tolerance field on FOMPROF represents the percentage of dollars over the original Purchase Order amount that the Invoice form user, usually an A/P clerk, can pay an invoice. Unlike the Receiving Overage Tolerance, this value takes into account the amount (quantity x unit price) rather than just quantity. In the Invoice Tolerance Amount field on FOMPROF, enter the dollar amount limit for overpayments. The overage and amount fields work together. For example, your site's policies may stipulate that A/P clerks can pay up to 10% more than the ordered amount (quantity x unit price), not to exceed $100.00. In this case you would enter 10 in the Invoice Overage Tolerance field and 100 in the Invoice Tolerance Amount field. If the approved amount plus the previously paid amount on the invoice is greater than the ordered amount, FAAINVE checks the values in both the Invoice Overage Tolerance and
2-174
November 2010
Invoice Tolerance Amount fields. FAAINVE calculates the lower amount and determines whether the user has the authority to complete the invoice. For example, with these fields populated with 10% and $100.00 the invoice approved amount is $10,500.00 with an ordered amount of $10,000.00. Although the overage amount as a percentage is less than 10%, the invoice form still prevents the invoice from being completed because the amount in dollars exceeds the $100.00 specified in the Invoice Tolerance Amount field on FOMPROF. If you impose no limits on overage payments, leave these fields blank. If all overpayments require further scrutiny, enter 0 (zero) in these fields. The system uses these two fields together. If you enter a value for one field, you must enter a value for the other field. If you do not enter values in both fields, the system assumes that a blank value prevails.
Establishing Users for the Process

Once you have determined the appropriate limits for the individuals processing invoices, you need to establish a user, typically the A/P supervisor, who has the authority to override an overage condition. For this hypothetical user, enter Y in the Invoice Tolerance Override field on FOMPROF. Once the system recognizes an overage condition, this user may enter Y in the Tolerance Override field on the Invoice/Credit Memo Form (FAAINVE) and complete the invoice if site-defined policies allow. Completing the Invoice If the total dollars on the invoice are less than the dollar amount in the Invoice Tolerance Amount field at document completion time, the invoice form sets Receipt Required to N (No) and marks the invoice as complete. If you have turned approvals processing on for invoices, the system forwards the document to the Approvals in Process Table (FOBAINP). If you have not turned approvals processing on for invoices, the system forwards the document to the Approved Documents Table (FOBAPPD). If the total dollar amount on the invoice is greater than the value in the Invoice Amount Requiring Receipt field, the system sets Receipt Required to Y (Yes) and marks the invoice equal to R (Receipt Required). If authorized, the user can override the Receipt Required value. (For additional information, see Receipt Required Field.) This status means that the invoice is awaiting matching before completion. When an invoice has this status, you may re-enter it to update or delete information. If the invoice references a Standing type purchase order, the system marks the invoice equal to C (Complete) thus bypassing the Receiving/Matching Process. Enter zero (0) in the Amount Requiring Receipt field on FOASYSC to ensure that all invoices require evidence of receipt before payment. If you do not want to control payment of invoices based on receiving data, leave this field blank.
November 2010
2-175
The R status is the signal to the Receiving Matching Process (FABMATC) to find the receiving information for the invoice. FABMATC performs a three-way match of the purchase order, packing slips, and invoice and produces an audit report. The PO Receiving Status Report (FPRRCST) displays the receiving status. The Document History Form (FOIDOCH) displays the receiving document associated with a purchase order and/or invoice. Click in the Receiving window of FOIDOCH and click Document Inquiry or select Duplicate Item to access the Receiving Goods Query Form (FPIRCVD). The invoice status options include R. Choosing to Use Optional Features It is important to remember that these features are strictly optional. Depending on your policies and procedures, you may elect to control payment of invoices based on receipt of goods by entering a value in the Invoice Amount Requiring Receipt field on FOASYSC but not control for either overshipments or overpayments. You can choose to control overshipments in the receiving function by valuing the Receiving Overage Tolerance field on FOMPROF, but permit completion for all invoices regardless of any overage conditions. In some cases, you might determine that appropriate procedures dictate that no one can override either a Receiving Overage condition or an Invoice Tolerance Overage condition and that the correct procedure is to re-enter the documents and only approve those quantities or amounts that are equal to the limits set. Under these circumstances, no users would have the Invoice Tolerance Override or Receiving Override fields populated on FOMPROF.
Document Level Matching

Document Level Matching gives you the option of using the system default for matching with an optional Receipt Required override at the document level, despite the documents amount. Document identification (for those items that require matching/receiving at an institutional level) allows departments to perform the following tasks: Identify specific purchases, beginning with the procurement process, where the associated invoices require receiving/matching prior to payment. Permit the enterprise level matching default to be overridden on a case-by-case basis. Approval queue criteria (chart, fund type, fund, organization, account type, account, and program) are used without modification to route the invoice to the appropriate personnel for approval.
2-176
November 2010
Receipt Required Field

The Receipt Required field is a display-only field that appears only if document level matching is enabled, based on the value in FOASYSC. The value in this field indicates whether invoices associated with this document will require matching. The amount for which a receipt is required is entered on the System Control Maintenance Form (FOASYSC) in the appropriate field for the document type: Requisition Amount Requiring Receipt, Purchase Order Amount Requiring Receipt, or Invoice Amount Requiring Receipt. This value sets the Receipt Required value on the first document in a linked series of documents. Subsequent linked documents are initiated with the same Receipt Required value as the predecessor document. If you have permission to override this value, as established on FOMPROF, you can override this operation. When document level matching is enabled, the Receipt Required field displays on the form for each document type: FPAREQN, FPAPURR, and FAAINVE. If you have the authority, as defined on FOMPROF, you can override the value that appears in this field. When document level matching is enabled, the document must be set to either Yes Receipt Required or No Receipt Required to be completed. Information about the Receipt Required value specific to each document type is included in the following sections. Requisitions The Receipt Required value on the requisition is applied to the document as a whole. Any purchase orders assigned to that requisition include, by default, a matching Receipt Required value. Authorized users can override the default value. Purchase Orders Multiple requisitions may be assigned to a single purchase order. If the Receipt Required value on any requisition is set to Receipt Required, the associated purchase order is also set to Receipt Required, even if other requisitions on the purchase order are set to No Receipt Required. Authorized users can override the default value. The Receipt Required value on the purchase order is applied to the document as a whole. Any invoice processed against that purchase order includes, by default, a matching Receipt Required value. Authorized users can override the default value. All invoices that reference Standing types of purchase orders bypass the Receiving/ Matching Process, despite the invoice amount. The Receiving/Matching Process uses the quantity of a commodity to match an item for payment. Standing type purchase orders use only dollar amount, not quantity.
November 2010
2-177
Invoices When an invoice is marked complete, the wrap-up routine checks to see if the enterpriselevel matching requirement is more restrictive than the Receipt Required value defaulted from the purchase order. If the value is No Receipt Required, and if the invoice amount is greater than or equal to the Invoice Amount Requiring Receipt amount on the System Control Maintenance Form (FOASYSC), the wrap-up routine sets the value to Receipt Required. The wrap-up routine sends the user a message that the value has been reset. With appropriate permissions, the user can change the value back to its original value of No Receipt Required. This process ensures that institutional policies are not overridden unintentionally. All invoices that reference Standing types of purchase orders bypass the Receiving/ Matching Process, despite the invoice amount. The Receiving/Matching Process uses the quantity of a commodity to match an item for payment. Standing type purchase orders use only dollar amount, not quantity.
Setup of Document Level Matching

This section includes a flowchart for the setup of Document Level Matching and a detailed description of each step in the flow.
Note A database level definition defaults U-Unspecified in the Receipt Required columns.This ensures that any existing process, including locally created scripts and enhancement, will inherit a valid default value of U-Unspecified for Receipt Required when inserting new records, without modifications to code.
2-178
November 2010
Start
FOASYSC
Identify users for Override Permissions
FOMPROF
End
1. Create an effective dated record using the Procurement Processing Information
window of the System Control Maintenance Form (FOASYSC). Define the following: Document Level Matching start point (requisition, purchase order, or no Document Level Matching). Receipt Required threshold (amount requiring receipt). A separate threshold field is provided for Requisitions, Purchase Order, and Invoices. Threshold amount fields do not accept data if Document Level Matching is disabled. The Requisition Amount Requiring Receipt field will accept a value only if the Document Level Matching start point is Requisition. The Purchase Order Amount Requiring Receipt field will accept a value only if the Document Level Matching start point is either Requisition or Purchase Order. The Invoice Amount Requiring Receipt field will accept a value without regard to the Document Level Matching start point. A value in the Invoice Amount Requiring Receipt and a Document Level Matching start point of No Document Level matching results in Enterprise (System) Level Matching at the Invoice level.
2. Identify users to be granted Receipt Required override permissions (per document
type) and define Receipt Required override authorization rules on the User Profile
November 2010
2-179
Maintenance Form (FOMPROF) to reflect intended user capabilities. Repeat this process for all document types and desired users.
Banner Invoicing with Document Level Matching

This section includes a flowchart that outlines the process of Document Level Matching and a description of each step in the process. The example discussed here assumes the user is beginning with a requisition. If, instead, you begin at the purchase order or invoice level, then only that portion of the flow applies.
1. Designate the matching process.
If approvals for requisitions is enabled, the requisition is sent through approvals processing before being posted. If approvals for requisitions is disabled, the document is sent directly to the posting job.
2. The Posting Process (FGRACTG) posts the requisition.
A user who has the proper authority on FOMPROF can use the Receipt Required Value Maintenance Form (FPARRIM) to change the value of the Receipt Required field.
3. Assign requisition line items to a purchase order using the Purchase Order
Assignment Form (FPAPOAS). The Receipt Required value from the requisition is used as a default value for the purchase order header that is created on this form.
Note A one-to-one relationship may exist between requisition and purchase order, or items from multiple requisitions may exist within a single purchase order.
If there are multiple requisitions to a single purchase order, the most restrictive value is defaulted into the purchase order. If no Receipt Required value is on the Requisition, the purchase order is created with the value of Unspecified.
Note Users may not directly change the value on this form, but if authorized, can use the Purchase Order Form or the Receipt Required Indicator Maintenance form to override the value later. 4. Define the matching process via the drop-down list using the Purchase Order Form
(FPAPURR). The value in the Receipt Required field is set initially to the most restrictive case found on associated requisitions. If document level matching is not used for requisitions or there is no associated requisition, the document will be initiated with a value of Unspecified. Accessing
2-180
November 2010
the Balancing/Completion window will set the Receipt Required field to match based on the system value. For example, if FOASYSC Purchase Order Amount Requiring Receipt = $500 and the purchase order total is $600, then the Receipt Required value is automatically set to Receipt Required. An authorized FOMPROF user (cleared for Purchase Order override) may update the value that is either defaulted or set by the forms trigger. If approvals for purchase orders is enabled, the purchase order follows approvals processing prior to being posted. If approvals for purchase orders is disabled, the document is sent to the posting job.
5. The Posting Process (FGRACTG) posts the purchase order.
A user who has the proper authority on FOMPROF can use the Receipt Required Value Maintenance Form (FPARRIM) to change the value of the Receipt Required field.
6. Open the Invoice/Credit Memo Form (FAAINVE). Note Authorized users can override the default setting in this window.
When you access this form for the first time, the display-only field in the header reflects the value from the underlying purchase order. This value may change when you access the Balancing/Completion window. The Invoice wrap-up routine checks the Receipt Required value and updates the field to the most restrictive case.
Example:
If the Invoice Amount Requiring Receipt is $500, the default value for Receipt Required from the purchase order is No Receipt Required, and the Invoice amount is $600. The wrap-up routine resets the Receipt Required value to Receipt Required. A message indicates this change, and if you have been granted override authority, you can reset the value to No Receipt Required and complete the document.
Note If authorized, you can override the existing Receipt Required value.
When the document is marked complete, the system tests the value of the FAAINVE Receipt Required flag to determine the value to set for the Invoice Complete indicator as follows: If the Receipt Required flag is set to Receipt Required, the invoice complete indicator is set to R and the invoice is forwarded to the matching process.
November 2010
2-181
If the Receipt Required flag is set to No Receipt Required, the invoice complete indicator is set to Y and the invoice is forwarded to approvals or posting as appropriate. If you leave this document in process and return to it later, the new display-only field in the header reflects the value that was saved.
7. If the Complete indicator is R (Receiving Required), open the Receiving Goods Form
(FPARCVD) to create a receiving document. Continue with Step 8. If the Complete indicator is Y (No Receipt Required), the document is forwarded to the appropriate process. Continue with Step 9.
8. The Matching/Receiving Process (FABMATC) executes and compares Invoice and
Purchase Order quantities/amounts. If sufficient quantities have been received, the invoice is forwarded to the approvals or posting process as appropriate. The Matching/Receiving Process produces a report that lists unmatched and matched documents. Use this report to review and investigate potential receiving/invoicing problems.
Note A user who has the proper authority on FOMPROF can use the Receipt Required Value Maintenance Form (FPARRIM) to change the value of the Receipt Required field. 9. The Posting Process (FGRACTG) posts the invoice. After successful posting, the
invoice is available for payment.
2-182
November 2010
Start
FPAREQN
FGRACTG
FPAPOAS
FPAPURR
FGRACTG
FAAINVE
FAAINVE (Receipt Required Flag Prioritization)
Receipt Required value default from P.O.
No
Flag set? Yes
Wrap-up Routine sets most restrictive case.
FPARCVD
Receiving document created
Choice to Override Receipt Required Value.
FABMATC
Report
Complete document
Invoice Approval? Yes
No
Invoice Posting Job FGRACTG
End FAAINVE
Approval Processing
End
November 2010
2-183
Internal Vendor Order Processing

Internal Vendor Order Processing includes a standardized interface process that enables internal vendors to charge other departmental and organizational customers for goods and services provided. Charges for internal vendor purchase are made directly to the appropriate accounts in the general ledger at the time of payment release. Unlike external vendor transactions, internal vendor transactions are not invoiced. This process enables you to upload a file of expense, revenue, GL, encumbrance liquidation and adjustment transactions from internal vendors or other sources. The file is posted to the Banner Finance General and Operating Ledgers. Text associated with the transactions is also loaded.
Security Considerations
Banner baseline object level security is used to identify which user IDs are permitted to run the FUPLOAD, FURFEED, GUPDELT, FGRTRNI, GURDETL, FOMFSEQ, and GURTEXT processes. Fund level security is not invoked, since GURFEED documents do not route through Fund/Organization security. Interface transactions that error during FGRTRNI and/or FGRACTG processing will be available as incomplete Journal Vouchers, for correction. As with normal JV processing, staff responsible for correcting journal entries will need appropriate permissions, such as fund/organization, rule class, and user class as per site usage.
Internal Controls
You must develop internal control procedures to perform the following: Ensure the upload process functions in accordance with your sites policy. Provide a document numbering schema that does not conflict with document numbers created during the load process.
Note Documents assigned numbers during the load process will not load successfully if another document exists in Banner Finance transaction history (FGBTRNH, FGBJVCH, and GURFEED).
2-184
November 2010
Things to Remember
Internal Vendor Order Processing does not perform inventory tracking functions and does not affect the Stores Inventory module. The requesting department decides if the purchase is to be filled by an Internal Vendor and would complete the appropriate form outside of Banner. The client is responsible for writing the extract process for each internal vendor used to select the appropriate interdepartmental charges and create data files that can be uploaded to Banner. Data files uploaded to Banner must conform to a standard fixed file format as provided by SunGard Higher Education and accessible to the FUPLOAD process. Maintenance of upload files is site-specific. Transactions that include a Fixed Asset account will, through FGRACTG processing, create a record in the Temporary Origination Tag Table (FFBOTAG) if the System Control Form (FOASYSC) is set to process Journal Vouchers for fixed assets. Transactions processed through this enhanced upload/interface are created as completed and approved documents. Transactions processed through this enhanced interface are assigned the next available document number, using the two-digit document number prefix according to the System ID, if a document number is not present in the upload file. The necessary level of detail in the interfaced transactions (in addition to that required by system processing) is defined by the client and must facilitate future processing within Banner Finance and the Fixed Asset module. No encumbrance establishment will occur, only liquidations and adjustments to encumbrances established within Banner Finance. Budget processing transactions will not occur. Transactions requiring vendor pidm or one-time vendor codes will not occur. Tax processing will not occur. Currency conversion will not occur.
Internal Vendor Setup

1. Open the System Data Maintenance Form (FTMSDAT) to define all System IDs used
in this process. Enter the following for each System ID: Entity/Usage Code FGBTRNI Attribute Code SYSTEM_ID Optional Code #1 SYSTEM_ID (user-defined value)
November 2010
2-185
Effective Date As desired Description/Title As desired Short Title As desired Data Field Two alpha characters, as shown in the following chart:
Character First character
Description
Allowable Values
Format
D - Detail S - Summary
Second character
Transactions
R - Rejects S - Suspends
2. Optional) Open the Document Number Management Form (FOMFSEQ) to create any
system ID/document number relationship, where FUPLOAD is expected to create the document number. FOMFSEQ relationships are not necessary for a System_ID where the document number is supplied in the upload file.
3. (Optional) Open the Parameter Value Validation Form (GJAPVAL) and enter the
System ID(s) established in Step One in the Parameter 01 Value. If any one System ID Parameter Value is entered here, all System IDs that will be used by FUPLOAD must also be entered here. The following diagram shows the process flow for setting up internal vendors:
2-186
November 2010
Start
FTMSDAT
FOMFSEQ
GJAPVAL
End
Internal Vendor Order Processing

1. Create an input file to include related internal vendor charges. 2. Execute the Finance Upload to GURFEED Process (FUPLOAD) to save valid
internal charge records. Data load confirmation (document numbers and record count) and related errors are listed in the resulting report. Data must conform to specific GURFEED population requirements.For detailed filerelated details, refer to the Reports and Processes chapter. If you run FUPLOAD in audit mode, the following processing occurs: All associated records are validated. Edited rows are not committed (to GURFEED or GURTEXT). A resulting FUPLOAD Report is generated The load process continues until all records are read and passed through the edit process. If you run FUPLOAD in update mode, the following processing occurs: Individual input file documents are validated as follows: The System ID from the selected documents header record is compared to the input files system ID parameter.
November 2010
2-187
The header records Doc. Code is verified. If a Doc. Code does not exist, a Doc. Code is generated. If the Doc. Code is currently in use, an error is generated and the record is not committed. The header records Transaction Date is checked for an open fiscal period based on the chart of accounts on the detail record. The detail records encumbrance data are validated. If the encumbrance type is L, encumbrance validation is bypassed. The documents trailer record is validated. The documents text record sequence numbers are system-generated (starting at number 10, incrementing by 10, for each new document).
Note It is possible to have successful and unsuccessful documents in the same file.
Successfully validated data are written directly to GURFEED/GURTEXT. Documents that do not pass validation tests are noted in the FUPLOAD Report. Some required GURFEED table columns are not included on the various input file record types but are system-generated. When document validation is complete, a resulting FUPLOAD Report (.lis and.log) is generated. If the input file's permissions are configured to accept changes, the file's extension is updated to processed to indicate job status. For example, if the original input files name was filename.prn, it is changed to filename.processed. Maintenance of upload files is site-specific. Any errors noted in the FUPLOAD report should be corrected in the Internal Vendor data file or, preferably, within the system used to generate the Internal Vendor data file. Specific correction methods are site-specific. Corrected internal vendor data are resubmitted to Finance Upload to GURFEED Process (FUPLOAD) for additional processing.
3. (Optional) Execute the Document Detail Report (GURDETL) to review GURFEED
data. If document data are considered invalid, execute the Document Code Delete Process (GUPDELT) to remove invalid document(s).
Warning It is recommended that access to the Document Code Delete Process (GUPDELT) be restricted to staff members responsible for maintenance of data in the GURFEED and GURTEXT tables. Caution should be exercised when selecting a document for removal. This process can be used for any document in GURFEED, not just those from FUPLOAD. As such, AR, Advancement, and HR information could be deleted without chance of recovery.
2-188
November 2010
4. Execute the Finance Feed Sweep Process (FURFEED) to identify valid data for
further processing. If document data are considered invalid, via FURFEED view mode, execute the Document Code Delete Process (GUPDELT) to remove invalid documents. If document data are considered valid, GURFEED data are loaded via FURFEED select mode, through FGBTRNI to the FGBTRNI table.
5. Execute the Interface Process (FGRTRNI) to populate FGBJVCH and FGBJVCD.
The FOBTEXT table is loaded from records in GURTEXT. Documents that fail FGRTRNI edits are presented as incomplete Journal Vouchers in Banner Finance for user correction and completion. Documents that interface successfully are submitted for posting as Journal Vouchers.
6. Execute the Posting Process (FGRACTG) to store accounting data from Banner
Finance transactions to the appropriate Banner Finance ledgers. The following flow charts illustrate internal vendor order processing.
November 2010
2-189
2-190
November 2010
Approvals Processing
This section identifies the forms and fields you need to define for minimum approvals processing. Approval forms include the following: Finance Approval Menu (*FINAPPR) User Approval Form (FOAUAPP) Document Approval Form (FOAAINP) Approvals Notification Form (FOIAINP) Document Approval History Form (FOIAPPH)
November 2010
2-191
Approval History Form (FOIAPHT) Approval Queue Routing Codes Form (FOMAQRC) Approval Queue Maintenance Form (FTMAPPQ)
Note You can only approve or disapprove documents on the User Approval Form (FOAUAPP) and the Document Approval Form (FOAAINP). The Originating User can disapprove a document using the Document by User Form (FOADOCU). When you disapprove (that is, deny) a document, the system inserts a record with a queue of DENY into the history table.
Banner Finance documents are created online in document entry forms. These documents include Journal Vouchers, Automatic Journal Vouchers, Encumbrances, Purchase Orders, Requisitions, Change Orders, Invoice/Credit Memos. Documents are distributed by the Approvals Process (FORAPPL) to all required approval queues based on accounting information. Account information may include the following: Chart of Accounts Fund Fund Type Organization Account Account Type Program The routing criteria determine which queue the system will use to route a document. After determining the initial routing queue, the system distributes the document to all the appropriate queues/levels necessary for final approval based on total document amount.
Required Forms and Fields

Approval Queue Maintenance Form (FTMAPPQ)
The required fields in the Key Information of this form are Queue ID, Description, and Queue Limit. The queue contains levels of approval necessary with appropriate approval limits by level. Once you establish approval queues using the Approval Queue Maintenance Form (FTMAPPQ), define the routings. The Approval Queue Routing Codes Form (FOMAQRC) displays the Queue ID in the Key Information. Selecting Next Block automatically queries the routing detail information.
2-192
November 2010
Approval Queue Routing Codes Form (FOMAQRC)

The required fields on this form are Document Type, Rule Group, and Chart of Accounts.
System Control Maintenance Form (FOASYSC)

Populate the Approval Override Indicator, by document type, with N to initiate the Approval Process. Populate the Approval Override Indicator, by document type, with I to initiate the Implied Approval Process. Populate the Approval Override Indicator, by document type, with Y to bypass the Approval Process.
User Profile Maintenance Form (FOMPROF)

Enter the User ID and User Name for which you want to establish NSF Override Authority in the Key Information. Select Next Block and go to the NSF Override check box. Select the NSF Override check box to provide override authority. The NSF Checking Indicator enables you to control NSF Checking by document type at time of entry. The following document types have the NSF Checking indicator: Journal Vouchers, Encumbrances, Requisitions, Purchase Orders, Change Orders, and Invoices. The default for this indicator is checked, which directs the system to perform NSF Checking when you enter any of these documents. If the box is unchecked, NSF Checking by document type will be delayed until posting.
Approvals Process Flow

The approvals process flow appears on the following page.
November 2010
2-193
Completed Documents Online for Encumbrances, Journal Vouchers, Invoice/Credit Memos, Purchase Orders, Change Orders. and Requisitions
FOBUAPP_STATUS_IND=(N)ew
Unapproved Document Table (FOBUAPP)
3 Approvals Process (FORAPPL) No Next Approver Approvals in Process Table (FOBAINP) 4 Does document have final approval? Yes Approvals Process (FORAPPL) 5
Yes NSF Queue 7
Do NSF Conditions Exist?
No Approved Document Table (FOBAPPD)
Note: This assumes approvals processing is turned on. If approvals are not being used, the document is written automatically to FOBAPPD when complete and is forwarded to Posting (FGRACTG).
9 Approvals Process (FORAPPL)
2-194
November 2010
1. Complete documents using the appropriate online forms for encumbrances, journal
vouchers, automatic journal vouchers, invoice/credit memos, purchase orders, change orders, and requisitions.
2. When you complete the document, the system inserts a new row into the Unapproved
Document Table (FOBUAPP). Status Indicator FOBUAPP_STATUS_IND=N. The Status Indicator does not recognize revised documents. Revised documents are new upon completion. The Unapproved Document Table (FOBUAPP) contains records for new documents based on document type, change sequence number, and submission number
3. The Approvals Process (FORAPPL) creates records for documents and inserts the
records in the Approvals in Process Table (FOBAINP). The system enters documents into all the appropriate queues based on data items, such as document type and document amount. Once a document successfully processes through FORAPPL, all queue(s) and level(s) required for approval are determined. Once determined, they are unaffected by changes in queue routing (defined on FOMAQRC) and queue limits (defined on FTMAPPQ). If the approval criteria are satisfied, the Approvals Process distributes the document into the appropriate queues. A document may appear in more than one queue. If you have not satisfied approval criteria, FORAPPL issues an error message and the record of this document remains in the Unapproved Document Table (FOBUAPP). The Approvals Process generates all approval-type error message. Update the document using the appropriate online approval forms. You cannot modify a completed document unless FORAPPL denies approval. An example of approval criteria not being satisfied is an NSF condition. Re-save the document for approval. You may view the online queues and review the commodities in the documents before you approve documents. You may transfer to the document detail from the Document Approval Form (FOAAINP) and from the User Approval Form (FOAUAPP). View the documents listed in the queues on the Document Approval Form (FOAAINP). The system deletes records in the Approvals in Process Table (FOBAINP) when you have satisfied all approval levels for a completed document.
November 2010
2-195
4. The system checks documents NSF conditions before they are inserted into the
Approved Document Table (FOBAPPD). The system reserves the NSF Queue for approved documents with NSF errors only.
5. FORAPPL transfers documents with NSF conditions to the Approvals in Process
Table (FOBAINP).
6. If no NSF condition exists, the Approvals Process deletes the record in the
Unapproved Document Table (FOBUAPP) and inserts a record in the Approved Document Table (FOBAPPD).
7. The Posting Process (FGRACTG) updates the finance ledgers with document
accounting information.
Cancelling a Document After Final Approval

You can cancel approved documents from the following forms: Invoice/Credit Memo Cancel Form (FAAINVD) for invoice/credit memos Requisition Cancel Form (FPARDEL) for requisitions Purchase/Blanket Order Cancel Form (FPAPDEL) for purchase and blanket orders Change Order Cancel Form (FPACDEL) for change orders
Cancelling a Requisition
When you create a requisition on the Requisition Form (FPAREQN), you may select Remove Record from the Request field and remove an incomplete document. To complete a document, enter the required data items and go to the Posting Control Information. Enter Y in the Complete field and select Next Block. If you select Remove Record from the Requisition Commodity Information, you remove only the commodity and its accounting data. If you select Remove Record from the Key Information, you remove the document. An authorized approver may deny (that is, disapprove) approval of this document. Approve or deny documents using the User Approval Form (FOAUAPP) and the Document Approval Form (FOAAINP). The Originating User can disapprove a document using the Document by User Form (FOADOCU). If the system denies a document, the document status is Incomplete. The Incomplete status enables you to use the Remove Record function from FPAREQN to remove the document. After final approval, the system updates the General Ledger for the total amount of the requisition. To cancel the document, access the Requisition Cancel Form (FPARDEL). Use FPARDEL to cancel a requisition document after the system has approved it. Once
2-196
November 2010
you save the canceled document, the system updates the General Ledger with a negative amount equal to the amount of the requisition. The system adjusts the available balance. You cannot modify completed and approved documents.
Approval Queue Setup

Approval Queue Maintenance Form (FTMAPPQ)
Access the Approval Queue Maintenance Form (FTMAPPQ). To establish a queue, specify the following.
Field Queue ID
Description
Enter the approval code ID that you wish to create or maintain. Enter descriptive information for the queue. Enter the queue dollar limit. This amount should be equal to the approval limit of the user at the highest level of the queue. This dollar limit defines the upper limit for document approval by any individual user within the queue.
Queue Title Queue Limit
Notes
The Queue Limit field should be less than or equal to the dollar amount being approved by the highest level approver in the queue. It is this dollar amount in the Queue Limit field that acts as the trigger to move a document into the next queue. The queue limit may be less than the approval limit for any or all queue levels. Any document amount that exceeds the queue limit will look for a next queue for approval. If the document meets the criteria for moving forward to the next queue it will be immediately available for approval by the next queue. Approval by the previous queue is not a prerequisite. If everything for this queue should automatically go on to the Next Queue field, regardless of amount, set the Queue Limit field to zero. Select Next Block to the FORAQUS Information. Use these fields to define levels of approval authority at various dollar amounts. The lowest level approver within a queue should start at level 1. The approvals process searches for the lowest level approver. Multiple approvers may exist at a given level; however, all approvers at the same level require the same approval amount.
November 2010
2-197
The lowest level approver can view all documents that come into the queue while each successive user only sees those documents with a dollar value higher than the limit of the last approver. View documents from the User Approval Form (FOAUAPP) and the Document Approval Form (FOAAINP). The higher level approvers are now able to see if all subordinate levels have already approved the document. The higher levels are now able to force the lower level(s) of approval. The approver displays as the approvers of the lower level if they do so.
Example:
Enter a document for $1500.00 into the system on 6/28/96. The system routes it to queue Q1. Q1 is defined as follows: Queue limit is $10,000. Queue level 1 is $1,000. Queue level 2 is $5,000. Queue level 3 is $10,000. Queue level 1 has User ID FIMSUSR1; effective 06/01/96. Queue level 1 has User ID FIMSUSR2; effective 07/01/96 terminated 07/31/96. Queue level 2 has User ID FIMSUSR3; effective 06/01/96. Queue level 3 has User ID FIMSUSR4; effective 06/01/96. The system writes two records to the Document Approval Form (FOAAINP) for the document, indicating that the system requires Queue Q1 level 1 and Queue Q1 level 2 approval. On 06/29/96, only FIMSUSR1 can approve level 1 and FIMSUSR3 can approve level 2. For the month of July, FIMSUSR2 can approve level 1. FIMSUSR3 can force level 1 approval if desired, even though FIMSUSR3 is not at level 1. If you reduce Q1's limit of $10,000 to $1,000, it has no effect on the routing of this document because the routing is already determined. If FIMSUSR1 has its approval privileges terminated as of 06/28/96, it could not approve on 06/29/96.
Warning This would mean that no one could approve level 1 until FIMSUSR2 became valid on 07/01/94. Again, FIMSUSR3 could force approval.
2-198
November 2010
The system discards duplicate records from the Approvals in Process Table (FOBAINP). Records present in the Approval Process (FORAPPL) remain unaffected by changes in queue level amounts or user amounts. The system reads these queue values when FORAPPL executes. The Approvals Notification Form (FOIAINP) displays when you initially request a Banner Finance form. The Approvals Notification Form (FOIAINP) displays documents for which you are the next approver by Document Type and Document Count. The Approval Queue definitions and limits determine who is the next approver. FOIAINP displays documents at the lowest approval level for the user currently logged on. Enter Y at the Transfer to Approval Screen prompt and select Enter to access the User Approval Form (FOAUAPP).
Queue Routing Setup

Once you establish the Approval Queues using the Approval Queue Maintenance Form (FTMAPPQ), define the routing. The Approval Queue Routing Codes Form (FOMAQRC) enables you to establish routing paths for documents by Document Type, Rule Group, and Chart of Accounts. Optionally, you may define a variety of accounting information to the route. A queue may have more than one routing criterion. Enter a valid queue ID. The description will display. List is available. Select Next Block to query routing criteria for the queue ID. The required fields on this form are Document Type, Rule Group, and Chart of Accounts. The following fields further define your routing criteria. Fund - The system validates fund codes using the Fund Validation Table (FTVFUND). List is available. If you enter a high level fund, the system routes its subordinate funds to this queue unless a more specific queue definition exists containing the subordinate fund or a fund closer in the hierarchy. Fund Type - The system validates fund type codes using the Fund Type Validation Table (FTVFTYP). List is available. You may enter either Level 1 or 2 Fund Types. Use these fund type levels to differentiate the routing of Unrestricted and Restricted Funds, if applicable at your site. Orgn - The system validates organization codes using the Organization Validation Table (FTVORGN). List is available. Populate this field to route documents for approval based on departmental requirements. Acct - The system validates account codes using the Account Validation Table (FTVACCT). List is available. Define this field to further specify document routings.
November 2010
2-199
Acct Type - The system validates account type codes using the Account Type Validation Table (FTVATYP). List is available. Define this field to further specify document routings. Use an account type code to route certain types of accounts (for example, Capital Equipment Purchases). Prog - The system validates program codes using the Program Validation Table (FTVPROG). List is available. Populate this field to route documents for approval based on departmental requirements. For example, if a queue contains a Fund and another queue contains an Organization, and you enter a document with both values defined, the system routes the document to the queue defined with the Fund versus the Organization. Define the precedence by the order of the values as displayed on FOMAQRC. Fund takes precedence over Fund Type. Fund and Fund Type take precedence over Organization. Organization takes precedence over Account. The system uses the following selection criteria when an exact match does not exist: Any combination of fund, organization, and account match. Fund has a higher selection criteria than organization, and organization has a higher selection criteria than account for those records that have the same number of matches. The fund matches on this form and the transaction awaiting approval. The organization matches on this form and the transaction awaiting approval. The account matches on this form and the transaction awaiting approval. There are no matches. However, the system matches the record that is the least number of levels away from the transaction. (Specify levels using the validation forms for fund, organization, and account.) Fund has a higher selection criteria than organization, and organization has a higher selection criteria than account for those records that are the same number of levels away from the transaction.
Direct Cash Receipt Approvals

The Approval Process allows you to route Direct Cash Receipt documents. To accommodate this feature and to invoke rule classes, the rule group DCRG contains the following rule classes which were established for the DCR document type: DCSR - Direct Cash Receipt RBTR - Return Rebate Cash Receipt TAXR - Remove Tax Liability on Cash Receipt
2-200
November 2010
The following is the recommended procedure for direct cash receipt approvals:
1. Verify that the rule classes (DCSR, RBTR, TAXR) are part of your production seed
data.
2. Verify that a new Direct Cash Receipt Rule Group (DCRG) is valid in your
production seed data and that the rule classes listed above are linked to this rule group on the Rule Group/ Rule Class Security Maintenance Form (FOMRGRC).
3. Create new approval queues for routing Direct Cash Receipts through the Approval
Queue Maintenance Form (FTMAPPQ).

4. Set up approval routing criteria for the new approval queues on the Approval Queue
Routing Codes Form (FOMAQRC).

5. Click the Approval Override button on the System Control Maintenance Form
(FOASYSC) to go to the Approval Override Information Window.

6. On the Approval Override Information Window, select an option from the Cash
Receipts pull-down list to run the document through or to bypass the approvals process.
Document Level Accounting and Commodity Level Accounting

Document Level Accounting
Document Level Accounting enables you to assign account distributions at the document level, rather than to specific commodities. This means you have less data to enter and spend less time processing documents. For a large document, which you may charge entirely to the same accounting distribution or distributions, this means you only have to enter the distributions once per document, instead of for each commodity record. In addition, when you assign accounting distributions at the document level rather than commodity level, fewer records are stored on the transaction history tables and document accounting tables. You can select the Document Level Accounting check box in the Invoice/Credit Memo Header window of the Invoice/Credit Memo Form (FAAINVE), or in the Commodity/ Accounting window on the Invoice/Credit Memo Form (FPAREQN) or the Purchase Order Form (FPAPURR). If you select the Document Level Accounting check box, the system expects and manages accounting distributions for the document in total. When you make changes to commodities, such as quantity or unit prices changes, the resulting change in dollars is
November 2010
2-201
shared by all the accounting distributions, depending on the amount and percentage each accounting record owns of the document total. On the Change Order Form (FPACHAR), the Document Level Accounting check box default value comes from the purchase order. The indicator displays as selected or cleared and cannot be changed.
Warning Do not mix the two types of accounting (Document Level Accounting and Commodity Level Accounting) within documents or between documents.
If you clear the Document Level Accounting check box, you must assign accounting distributions to specific commodities (Commodity Level Accounting). The check box default is selected, even for purchase orders you create from rush orders. This indicator field governs the processing of the entire document. Once you create accounting records, you can no longer switch the Document Level Accounting indicator. If you decide to change from Document Level Accounting to Commodity Level Accounting (or vice versa), delete the existing accounting records, return to the Commodity block of the Commodity/Accounting window and reset the indicator. With two different types of document processing available, it is very important to understand that you cannot mix the two types within documents or between documents. If you create a requisition as a Document Level Accounting document that you roll into a purchase order, that purchase order becomes a Document Level Accounting document. Conversely, if you create a requisition that is a Commodity Level Accounting document, the purchase order must be a commodity level purchase order. On each of the document forms, the system displays error messages to indicate whether a conflict exists. Once you choose between Document and Commodity Level Accounting, enter the commodity items. Regardless of the accounting method, you enter commodities the same way. To create all of your commodity items first and move from one commodity to another, use Next Record and Previous Record. Alternatively, you can create one or more commodity records, select Next Block, and enter the Accounting Block of Commodity/ Accounting window in order to specify the account distribution(s) for the document.
Commodity Level Accounting

For new purchase orders, requisitions, or invoices, you can set the default accounting level to Commodity Level Accounting instead of Document Level Accounting. If your site currently uses Document Level Accounting as the default, and you want to continue this practice, you do not have to do anything. The level you choose cannot be changed after the accounting sequences are created.
2-202
November 2010
You can choose to use Commodity Level Accounting for all documents (Requisitions, Purchase Orders, Invoices) or selectively for specific documents.
For All Documents

To set up Commodity Level Accounting for all procurement documents, perform the following steps. The effective date you enter on FTMSDAT establishes the initial date that Commodity Level Accounting goes into effect. For example, if you enter a past or current date on FTMSDAT, all documents created from then on will use Commodity Level Accounting. If, instead, you enter a future date on FTMSDAT, Commodity Level Accounting will not take effect until that date.
1. Access the System Data Maintenance Form (FTMSDAT). 2. In the Entity or Usage Code field, enter ALL_DOCS. 3. In the Attribute Code field, enter ACCOUNTING_LEVEL. 4. In the Data field, enter Commodity_Level. 5. Save.
You can turn off this setting on FTMSDAT by terminating the record or changing the record status to inactive.
For Specific Documents

To set up Commodity Level Accounting for specific documents only, perform the following steps. The effective date you enter on FTMSDAT establishes the initial date that Commodity Level Accounting goes into effect. For example, if you enter a past or current date on FTMSDAT, all documents created from then on will use Commodity Level Accounting. If, instead, you enter a future date on FTMSDAT, Commodity Level Accounting will not take effect until that date.
1. Access the System Data Maintenance Form (FTMSDAT). 2. In the Entity or Usage Code field, enter the type of document for which you want to
use Commodity Level Accounting. REQ for requisitions PO for purchase orders, rush orders and blanket orders INVOICE for invoices
November 2010
2-203
3. In the Attribute Code field, enter ACCOUNTING_LEVEL. 4. In the Data field, enter either Commodity_Level or Document_Level. 5. Save.
You can turn off this setting on FTMSDAT by terminating the record or changing the record status to inactive.
Commodity Level vs. Document Level Accounting

Invoice Accounting Distribution Window (FAAINVE)
Once you enter the Invoice Accounting Distribution window on FAAINVE, some distinctions between Commodity Level and Document Level Accounting documents become apparent. If you assign accounting distributions to the document in total, the item number associated with any accounting distribution on the document is zero. Therefore, at the top of the Invoice Accounting Distribution window, you do not see a value in the Item number field, and the Commodity field reads Document Acctg Distribution. If the document uses Commodity Level Accounting, these fields display the specific item number and description for the commodity. If you select the Document Level Accounting check box, you do not have to enter the dollar amounts when you enter the account distribution. The system incorporates a redistribution process into the Wrap-Up routine, which allocates and enters the amounts to the account distributions based on the sum of the commodity dollar amounts. If you process the document with Commodity Level Accounting (for example, the Document Level Accounting check box cleared), you must enter amounts when you create the accounting distributions, with the exception of the Requisition. For additional information, refer to Automatic Accounting Redistribution on page 2-206. For both kinds of documents, enter amounts as specific dollar amounts or with assigned percentages. Once you enter a percentage in this window, the system stores it in the database. If the amount on the commodity changes, the Wrap-Up process recalculates the amounts based on these stored percentages. For additional information, refer to Automatic Accounting Redistribution on page 2-206. Once you create the accounting records, select Next Block to go to the Balancing/ Completion window and complete the document.
2-204
November 2010
Encumbrances and Invoices

You can use the Invoice Credit/Memo Form (FAAINVE) to liquidate an encumbrance created using the Encumbrance Maintenance Form (FGAENCB). Unlike Purchase Orders, you create these encumbrances without commodity items. Select General Encumbrance from the Invoice Type pull-down list on the main window of FAAINVE. When you bring an encumbrance into FAAINVE, the system automatically creates an item when you move from the Invoice/Credit Memo Header window into the Commodity Information window. For this reason, an Invoice that liquidates an encumbrance that you create in the Encumbrance Maintenance Form (FGAENCB) must be a commodity level accounting document. Refer to an encumbrance that you create with the Encumbrance Maintenance Form as a General Accounting Encumbrance.
Accounts Receivable and Invoices

On Invoices which you create for refunds by Accounts Receivable processing, the Document Level Accounting check box default value is cleared, indicating a Commodity Level Accounting document.
Commodity/Accounting Window (FPAPURR, FPAREQN, FPACHAR)

Once you enter the Accounting block of Commodity/Accounting window on FPAPURR, FPAREQN, or FPACHAR, some distinctions between Commodity Level and Document Level Accounting documents become apparent. The Document Level Accounting indicator is visible at the top of the window to act as a visual reminder of what type of processing you have selected for the document. Based on the type of processing selected, the Commodity/Accounting window is dynamically redisplayed with fields appropriate for working within the selected processing type. For details, refer to the following table.
November 2010
2-205
Type of Accounting Document Level
Fields Displayed Commodity Line Total Document Commodity Total Document Accounting Total Remaining Commodity Amount
Notes Be sure the amount in the
Document Commodity Total

field equals the amount in the
Document Accounting Total

field.
Remaining Commodity Amount displays the difference between the net total of all commodities entered on the document and the net total of accounting distributions entered on the document.
Commodity Level
Commodity Line Total
Be sure the amount in the Commodity Line Total field Commodity Accounting Total equals the amount displayed in the Remaining Comm Amount Commodity Accounting Total field for each commodity entered. Remaining Comm Amount displays the difference between the net total of the currently selected commodity and the net total of all the accounting distributions entered for the selected commodity.
Completing the Document

For both Document Level and Commodity Level Accounting documents, you can enter amounts as specific dollar amounts or with assigned percentages. Once you enter a percentage in the Accounting Block of Commodity/Accounting window, the system stores it in the database. If you enter a specific dollar amount the percentage is calculated and stored in the database. Therefore, if the amount on the commodity changes, the Wrap-Up routine recalculates the amounts based on these stored percentages. For additional information, refer to Automatic Accounting Redistribution on page 2-206. Once you create the accounting records, select Next Block to access the Balancing/Completion window and complete the document.
Automatic Accounting Redistribution

Automatic reallocation of amounts occurs at the accounting level when you make a change to an existing commodity record on a document. This eliminates the need to adjust
2-206
November 2010
accounting distributions when you make a change in quantity or unit price to a commodity record. The system automatically distributes this change to the accounting distributions based on the percentage of the total held by each accounting distribution. For this process to automatically recalculate the amounts based on the stored percentages, the total of the percentages (either assigned or calculated) must equal 100%. Until the percentages are set to 100%, you will be required to manually update the Accounting amounts or assigned percentages for each accounting distribution entered. For Document Level Accounting, the percentage is based on document total. For Commodity Level Accounting, you change the total related to the specific commodity. The Wrap-Up routine accommodates currency conversion calculations and also prevents rounding problems encountered when you process certain kinds of tax-related transactions. The Wrap-Up routine includes two processes: The first process examines the amounts for all the accounting records for a specific commodity and determines if the detailed accounting amounts add up to the summary amounts on the commodity record. If not, a rounding error must be corrected. The process corrects the rounding error and sends you a message that states that the system has corrected a rounding error. The second process calls the Available Balance process, if appropriate. If the Available Balance process determines that there are insufficient funds, the system sets the NSF Suspense flag on the accounting record to Y.
Automatic Accounting Reallocation

Use the Access Completion check box (in conjunction with the suspense indicators on the commodity and accounting records) to determine when to allocate amounts automatically to accounting distributions. In the Purchase Order Form (FPAPURR), Change Order Form (FPACHAR) and Requisition Form (FPAREQN), the Access Completion check box is replaced with a Distribute check box since the Commodity and Accounting blocks exist on the same window. The fundamental difference between these two check boxes is that Access Completion only completes its related processes when used in conjunction with the Next Block function. The Distribute process completes its related function when used in conjunction with either Next Block or the link to the Balancing/Completion window. When you first create a commodity record, the Access Completion/Distribute check box is left cleared until you create accounting distributions. Once you create accounting distributions, the Access Completion/Distribute check box default value is selected. Differences in accounting reallocation functionality between the two types of document processing are explained in the following sections entitled Allocating Document Level
November 2010
2-207
Accounting Records on page 2-208 and Allocating Commodity Level Accounting Records on page 2-208. For this process to automatically recalculate the amounts based on the stored percentages, the total of the percentages (either assigned or calculated) must equal 100%. Until the percentages are set to 100%, you will be required to manually update the Accounting amounts or assigned percentages for each accounting distribution entered.
Allocating Document Level Accounting Records

If a commodity record exists and accounting records exist for the document when you initially query the commodity, the Access Completion/Distribute check box default value is selected. If you select Next Block at this point and select the Access Completion/Distribute check box, the system automatically allocates the change of the new dollar amount to the accounting distributions. If using the Access Completion check box, it then automatically opens the Balancing/Completion window. It is not necessary to go to the Accounting window to manually reallocate the amounts in this case. If using Distribute, it navigates to Accounting block and displays the updated dollar amounts. To change unit prices on multiple commodity records on a Document Level Accounting document, make the change to the first commodity and select Next Record to add or change the next commodity. Executing Next Record saves your changes and takes you to the next commodity, but does not reallocate the change at this time. Once you complete your changes, leave Access Completion/Distribute selected, and then select Next Block or click on the Balancing/Completion link to allow the system to distribute the changes. If you prefer to enter specific accounting amounts, leave Access Completion/Distribute cleared. When you select Next Block in this case, the system does not automatically allocate the amounts. You can distribute the amounts among the accounting distributions as you wish. Once you make the desired changes, select Next Block from the Accounting window or click on the Balancing/Completion link to access the Balancing/Completion window and complete the document.
Allocating Commodity Level Accounting Records

Accounting amounts are reallocated differently for Commodity Level Accounting documents. Like Document Level Accounting, the Access Completion/Distribute check box remains cleared until you create accounting records. The system automatically selects the Access Completion/Distribute check box once you create an accounting record. The system reallocates accounting amounts when you select Next Block in a Commodity Level Accounting document.
2-208
November 2010
Since the system links accounting records to specific commodity items, you must invoke the Wrap-Up routine when you move from one commodity record to the next. You may still clear the Access Completion/Distribute check box and select Next Block to enter the Accounting window and allocate the amounts manually.
Request Processing
For information about Banner Finance eProcurement, refer to the Finance eProcurement for HigherMarkets Banner Handbook.
Creating a Requisition
To create a requisition, access the Requisition Form (FPAREQN) from the Request Processing Menu (*FINREQST). Use this form to create and maintain the header, commodity, and accounting information for requisitions. For detailed information about the FPAREQN form, refer to the online help. You have two options when you create the accounting information for the requisition. Document Level Accounting enables you to assign accounting distributions to the document in total. Commodity Level Accounting enables you to assign account distributions to individual commodities. The advantages of Document Level Accounting are reduced data entry time and a reduced number of records stored in the requisition accounting and transaction history tables. You must retain the accounting method that you choose for a given requisition through all subsequent related documents.
Entering Currency Conversion Information on a Requisition

Unless you specify otherwise, all entered amounts are in the base currency of your installation. To verify this currency, refer to the Installation Control Form (GUAINST). When you select a foreign vendor, you can enter a currency code in the Currency Code field in the Requisition Commodity Supplemental Data Window. Select List to select from a Currency Code Validation Window. When you enter an established vendor, the vendor's currency code defaults into this field. The system calculates the converted amount (by dividing the input amount by the exchange rate) at both the commodity and accounting levels. The system uses the converted amount for Available Balance checking and posts this amount to the ledgers.
November 2010
2-209
To view the converted amounts, navigate to the Currency Conversion Window. To access this window, select Count Hits from either the Quantity or Unit Price fields in the Requisition Commodity Data Window or from anywhere within the Requisition Accounting Data Window.
Currency Conversion and Document Level Accounting

When commodities are brought forward from a requisition in the Currency Conversion process, the accounting distributions are brought forward based on the proportionate amounts of the commodity to the document total. For example, assume that you have a requisition with two commodities, each valued at $100.00. If the requisition has two accounting distributions at the document level, it brings forward $100.00 of accounting distributions if one of the two items is assigned to a purchase order. The system distributes the $100.00 of accounting distributions based on the percentage of the document total each accounting distribution holds.
Automatic Accounting Redistribution

The system reallocates amounts at the accounting level when you change an existing commodity record on a document. This eliminates the need to adjust accounting distributions when you make a change in quantity or unit price to a commodity record. The system distributes this change to the accounting distributions based on the percentage of the total each accounting distribution holds. This feature is available for both Document Level Accounting and Commodity Level Accounting document processing. For Document Level Accounting, this percentage is based on document total; for Commodity Level Accounting, this percentage is based on the total as it relates to the specific commodity that you change. Changes to commodity records occur in the Requisition Form (FPAREQN), Purchase Order Form (FPAPURR), and Change Order Form (FPACHAR). For additional information, refer to the online help for each of these forms.
Wrap-Up Routine
This routine accommodates currency conversion calculations and tax calculations, as well as online budget availability checking. It includes two processes: The first process examines the amounts for all the accounting records for a specific commodity and determines if the detailed accounting amounts add up to the summary amounts on the commodity record. If they do not add up, a rounding error occurs. This process corrects the rounding error and sends a message that a rounding error has been corrected. The second process calls the Available Balance process, if appropriate. If this process determines that there are insufficient funds, it sets the NSF Suspense flag on the accounting record to Y.
2-210
November 2010
An additional process enables you to save accounting changes automatically on the basis of commodity changes without reentering the Requisition Accounting Data Window. When appropriate (see below), the first process reallocates the sum of the commodity amounts to the accounting distributions based either on an equal allocation (if no percentages appear in the accounting records or if you use stored percentages). Remember, when you enter accounting information, you may reallocate the amounts on a percentage basis. Also, when you create a purchase order from this requisition, the system calculates the proportions of the accounting to the commodity and stores them as percentages in the purchase order.
Automatic Reallocation
In the Commodity Data Window of each of the purchasing forms, there is an Access Completion check box to facilitate the automatic reallocation process. This check box, in conjunction with the suspense indicators on the commodity and accounting records, determines when to allocate amounts automatically to the accounting distributions. If no accounting distributions exist, the Access Completion check box defaults to unchecked. You cannot check this check box until you create accounting distributions. The system automatically checks the Access Completion check box once you create accounting distributions, the box defaults to checked each time a commodity record displays regardless of the type of document processing selected. However, the functionality for Document Level Accounting is slightly different than for Commodity Level Accounting. Document Level Accounting If a commodity record exists and accounting records exist for the document when you first query the commodity, the Access Completion box is checked. If you make a change to the commodity (for example, if you change the unit price), the commodity Suspense indicator displays Y. If you select Next Block with the Access Completion box checked, the system automatically reallocates the change in terms of the new amount to the accounting distributions and opens the Balancing/Completion Window. You do not need to reallocate the amounts manually in the Accounting Data Window. To make changes to unit prices on multiple commodity records on a Document Level Accounting document, change the first commodity record and select Next Record to add or change the next commodity. This saves your changes and takes you to the next commodity record, but it does not automatically reallocate the change at this time. Once you complete all your changes, select Next Block to have the system distribute the changes. If you prefer to enter specific amounts for the accounting, uncheck the Access Completion box. When you select Next Block at this point, the automatic redistribution does not take place, and the Accounting Data Window opens.
November 2010
2-211
Distribute the amounts among the accounting distributions as desired. When you complete the changes, select Next Block to open the Balancing/Completion Window and complete the document. Commodity Level Accounting The allocation process for Commodity Level Accounting documents differs somewhat from Document Level Accounting. As with Document Level Accounting, the Access Completion box remains unchecked until accounting records are created, and you cannot access the check box. Once you create an accounting record, the system automatically checks the Access Completion check box. However, unlike the Document Level Accounting, the system automatically reallocates accounting amounts when you select Next Block or Next Record in a Commodity Level Accounting document. Since the system links accounting records to specific commodity items, you should invoke the Wrap-Up routine when you move from one commodity record to the next. You may still uncheck the Access Completion check box. Select Next Block to enter the Accounting Data Window and allocate the amounts manually. Whether you use Commodity Level or Document Level Accounting on the Requisition Form (FPAREQN), you can leave the amounts on the Accounting Window blank, and the form will automatically allocate the amounts. When you incorporate this additional process into Wrap-Up, you can enter accounting distributions without entering dollar amounts on Document Level Accounting documents.
Purchase Order Processing

Use the Purchase Order Form (FPAPURR) to create and issue purchase orders. This form calculates percentage distributions based on accounting sequences from a requisition. It also calculates currency conversion amounts when you purchase from a foreign vendor. Access this form from the Purchase Order Processing Menu (*FINPO).
Note For information about Banner Finance eProcurement, refer to the Finance eProcurement for HigherMarkets Banner Handbook.
Creating a Purchase Order

For detailed information about creating a Purchase Order, refer to the online help for the Purchase Order (FPAPURR) form. You can create a purchase order with either a general ledger account or an expense account. You cannot combine these two different accounts on the same purchase order.
2-212
November 2010
If you create a purchase order from a requisition, you must designate it as an expense purchase order. Note that when you create a purchase order from an existing requisition, you must use the same method of accounting that you used on the requisition. If you create a purchase order with Commodity Level Accounting, you may assign account distributions to specific commodities, if necessary. If you create a purchase order with Document Level Accounting, assign accounting distributions to the purchase order document in total. Document Level Accounting has the following advantages: Reduced data entry time. Fewer records stored by the system in the purchase order accounting and transaction history tables.
Date Processing
Even though you may roll encumbrances from a prior year if the accrual period is still open, you can also enter a transaction date for the purchase order into the prior year. The system treats this purchase order as if you had rolled it as a committed encumbrance. The system posts this balance to the general ledger for the prior year for which you enter this transaction.
Currency Conversion
Unless you specify otherwise, all amounts are entered in the installation's base currency. This currency is referenced on the Installation Control Form (GUAINST). When you select a foreign vendor, enter a currency code in the Currency Code field in the Vendor Information Window. Click the button or select List to select a currency code from a list window. When you enter an established vendor, the associated vendor's currency code defaults into the field from the vendor record. The system calculates the converted amount (input amount divided by the exchange rate) at both the commodity and accounting levels. The system uses the converted amount for available balance checking and posts this amount to the ledgers. To view the converted amounts:
1. Open the Currency Conversion Window. 2. Select Count Hits from either the Quantity or Unit Price fields in the Purchase Order
Commodity Data Window or from anywhere within the Purchase Order Accounting Data Window.
November 2010
2-213
Commodity Tax Information

If you use the tax features of Banner Finance, then you must select the Tax Processing On box on the System Control Maintenance Form (FOASYSC) and also select a Default Tax Group Code. You can establish tax groups at the Ship-To or commodity levels. At the header level, the system looks to the Ship Code for a tax group. If no tax group exists on the Ship Code, the system uses the default tax group on the System Control Maintenance Form (FOASYSC). At the commodity level, the form looks for a tax group on the commodity record (FTVCOMM). If a tax group does not exist, the tax group defaults from the header. Other options for commodity tax information: You should always set up a no-tax group on the tax group table to use when you do not want to tax either an entire document or certain commodities on a document. You can view the tax calculations and how the system distributes them by selecting Next Set of Records from either the Commodity Data Window or the Accounting Data Window. You can calculate tax rates in a simple or compounded manner at the commodity level.
Creating a Change Order

Access the Change Order Form (FPACHAR) from the Change Order Processing Menu (*FINCO). Use this form to revise header, commodity, and accounting information on the current purchase order or blanket order. There are some important exceptions when you revise purchase order information using the Change Order Form. You cannot change the Vendor, the Document Level Accounting indicator, or Currency code with a change order. In addition, you cannot change an Expense Purchase Order to a G/L Purchase Order or vice versa. The Document Level Accounting box in the Change Order Header Information Window indicates whether the purchase order or change order document assigns account distributions to the entire document in total or to specific commodities.
2-214
November 2010
Main Window
The main window contains the Purchase Order and Blanket Order number fields.
1. Enter the number of the purchase order or the blanket order which you wish to revise.
A button and List are available for both fields. To revise a blanket order, leave the Purchase Order field blank.
2. Enter NXT in the Change Sequence Number field to have the system generate the
next available change sequence number. You cannot generate a new change order sequence number until you complete, approve, and post the previous purchase order and/or blanket order.
3. If you need to revise the entire order, check the Change All box. Select Next Block to
access the Change Order Header Information Window. To select specific line items from the order to modify, check the Select Items box. If Select Items is checked, Next Block navigates you to the Purchase Order Item Selection Form (FPQCHAP) to select items. You can also access FPQCHAP by checking the Select Item box in the Change Order Commodity Data Window and selecting Next Item.
Change Order Header Information Window

A copy of the current header information defaults into this window; you may update the fields as necessary.
1. The purchase order Order Date field represents the date associated with the change
order. It defaults to the system date, but may be changed. The purchase order date from the original purchase order remains unchanged.
2. The Transaction Date is a required field that determines the fiscal period. It defaults
to the system date, but also may be changed.

3. The Buyer code and Ship Code are required fields. If you change the Discount code,
the system adjusts all items automatically for the new order.
4. The Document Level Accounting indicator defaults from the original order and
cannot be changed. If this field shows Y, then Document Level Accounting is in effect. Document Level Accounting enables you to assign an account distribution(s) to the document in total. If this field shows N, then Commodity Level Accounting is in effect which enables you to assign different account distributions to each commodity.
5. If Document Level Accounting is in effect and you wish to change only the
accounting distribution, you may check the Change Accounting Only box, which permits changes to the accounting distribution information only.
November 2010
2-215
Because you cannot process a procurement document without both a commodity and an accounting record, the form automatically brings in a commodity from the purchase order. This results in the system creating a commodity record for the change order, even though no changes were made to the commodity. When you query the Purchase/Blanket/Change Order Form (FPIPURR) for the specific change, a commodity record displays with zero amounts.
6. Click Document Text or select Block Menu to access the Procurement Text Entry
Form (FOAPOXT).
7. If you are changing only the header information on this order, select Previous Block
to access the Balancing/Completion Window and complete the change order.
Change Order Header Supplemental Data Window

In this window, optional information such as the FOB Code, the chart of accounts Class Code, and the Carrier may be changed. The Currency code cannot be changed. If the current record has header text, you may copy it into the change order by checking the Copy Text from Current box and selecting Save.
Vendor Information Window

The Vendor and Name (unlabeled) fields default and may not be changed. You can enter and change information in both the vendor Address Code and Sequence Number fields, but the combination of these fields must be valid for you to save the record.
Document Indicators Window

1. Check the NSF Checking box to have the system perform budget checking online. 2. If the Deferred Editing box is unchecked, ongoing editing of the document is
performed by the system. Check this box to activate the deferred editing feature. This feature speeds up system processing, but disables the system from displaying online errors immediately.
Change Order Commodity Data Window

Use this window to revise the commodity information. The order and vendor information defaults.
1. You may check the Select Item box and select Next Item to navigate to the Purchase
Order Item Selection Form (FPQCHAP) and select individual commodity items. The Purchase Order Item Selection Form lists the items from the original order. To select all of the items, check the Change All box and click or select Save. To choose a specific item, check the box at the right of the item record and click or select Save. To
2-216
November 2010
return to the Change Order Form, select Exit. Select Next Block to access the commodity data. If Select Item is not checked, you may select Next Block to access the commodity information.
2. Enter the Item number if you know it, or select Next Item to enter or change the
Commodity code (or the commodity Description if you do not specify a commodity code). You have several navigation options from the commodity fields: Select List from the Commodity code field to access the Commodity Validation Form (FTVCOMM) and select a commodity. Select Count Hits from the Commodity code field to access the Vendor Products Validation Form (FPVVPRD). This form displays a list of commodities which are available from the requested vendor. Select Execute Query from the Commodity code field to access the Vendor Products Query Form (FPIVPRD). This form displays a list of vendors who offer a particular commodity. If an agreement exists with a vendor other than the vendor you first select, a message displays. If you click the Commodity button, an Option List enables you to choose one of the three forms mentioned above. Click Description or select List from that field to access the Commodity Alpha Search Form (FPIACOM). To add a commodity code to the Commodity Table, enter the new code and description, then enter Y in the Add field. The system updates the FTVCOMM table when you save the commodity record.
3. The U/M field is required. Once you enter the commodity, the unit of measure
defaults from the commodity, and if you desire, you can change it.
4. As with a purchase order, the system requires the Tax Group field when you set the
Tax Processing indicator is activated on the System Control Maintenance Form (FOASYSC). You can change the tax group at the commodity level, if necessary.
5. You may enter or modify the Quantity and Unit Price. The Extended Amount is
calculated automatically.
6. The system calculates the discount amounts, provided you enter a discount code in
the Change Order Header Information Window. If not, you may enter a Discount Amount manually in this window.
7. The system calculates the Tax Amount based on the commodity tax group. 8. The Blanket Order Remaining Balance field displays only when the change order
is associated with a blanket order or the purchase order you enter is associated with a blanket order. When this field displays, the amount shown can either represent the
November 2010
2-217
remaining balance for the entire blanket order document or the amount that remains for a specific commodity. The definition of the displayed amount depends on the value in the Document Control indicator on the Blanket Order Form (FPABLAR). You cannot enter any changes to the purchase order that exceed the Remaining Blanket Order balance.
9. If line item text exists on the original order, you may attach it to change order by
checking the Copy Text From Current box and selecting Save. If you wish to review or edit line item text, click Line Item Text or select the menu option to access the Procurement Text Entry Form (FOAPOXT).
10. The Access Completion box enables you to move directly to the document
completion process from the Change Order Commodity Data Window when accounting records have been created. You cannot check the Access Completion box until accounting records exist for the commodity. When accounting records exist, the box defaults to checked. If you change the commodity information and select Next Block with the Access Completion box checked, the form opens the Balancing/ Completion Window. The Wrap-Up routine recalculates the accounting amounts based on the new commodity amount, corrects any rounding problems, and calls the Available Balance process. Wrap-Up occurs when you navigate from the Change Order Commodity Data Window to the Balancing/Completion Window (when accounting records exist) or from the Change Order Accounting Data Window to the Balancing/Completion Window if the document uses Document Level Accounting. If the purchase order is a Commodity Level Document, Wrap-up also occurs when you navigate from the Change Order Accounting Data Window to the Change Order Commodity Data Window. To reallocate the accounting amounts manually, uncheck the Access Completion box and select Next Block to access the Change Order Accounting Data Window. You can navigate to the following areas from the Change Order Commodity Data window: To navigate to the Tax Distribution Window (which you can only access when the Tax Processing Indicator is set to Y), select Next Set of Records from anywhere within this window. To access the Currency Conversion Window (which you can only access when you enter a foreign currency), select Count Hits from either the Quantity or Unit Price fields. To navigate to the Change Order Accounting Data Window, uncheck the Access Completion box and select Next Block. To save commodity amount changes automatically to the Change Order Accounting Data Window and transfer to the Balancing/Completion Window, check the Access Completion box and select Next Block.
2-218
November 2010
To view the commodities you wish to review and/or approve, click Review Commodities or select Block Menu to access the Commodities for Review Query Form (FOICOMM). To access the General Text Entry Form (FOATEXT), click View Commodity Text or select the menu option. To access the Procurement Text Entry Form (FOAPOXT) to create and edit line item text, click Line Item Text or select the menu option.
Change Order Accounting Data Window

The accounting data for existing commodities displays in this window. You cannot enter information in the Sequence Number field. Also, you cannot enter information in the FOAPAL fields for an account sequence which exists on the current order. If you need a new FOAPAL sequence, delete (or zero out) the old amount on the old FOAPAL, select Insert Record, and enter all of the new accounting information. The system generates a new sequence number when you save the record. If you use an account index, the system checks Override Indicators when you save the record. You can create multiple accounting sequences and distribute the amounts on a percentage or amount basis. You have the following options when you enter accounting information: You can save the record without entering amounts. When you execute redistribution from the Change Order Commodity Data Window, the system assigns the extended amounts equally among the number of account distributions that you enter. If the document uses Document Level Accounting, the system distributes all commodity amounts. If this is a Commodity Level change order, the system only distributes the specific commodity amount among the assigned accounting sequences. You can manually enter the dollar amounts. You can manually enter the percentages. Redistribution of commodity items depends on whether the Document Level Accounting box is checked: Checked - When you select Next Block in the Change Order Commodity Data Window to execute the redistribution function, the system redistributes the total of all commodity items to the accounting records using the percentages you enter for each account distribution. Unchecked - The system only redistributes the specific commodity amount among the assigned accounting sequences based on the percentages you enter.
November 2010
2-219
Move from one accounting sequence to another using the Next and Previous Record functions. To view the available budget, select Block Menu from any of the FOAPAL fields to access the Budget Availability Status Form (FGIBAVL). Select Next Block to access the Balancing/Completion Window. If you receive an insufficient funds message and you have authorization to override the budget, check the NSF Override box and click or select Save again to recommit the record. You can navigate to the following areas from this window: To navigate to the Currency Conversion Window, select Count Hits. To access the Balancing/Completion Window, select Next Block. To view the available balance, click Budget Availability or select Block Menu from any of the FOAPAL fields to access the Budget Availability Status Form (FGIBAVL). To view the accounting records, click View Accounting or select the menu option to access the Commodities and Accounting for Review Query Form (FOICACT).
Currency Conversion Window

As with the other procurement documents, the system calculates the converted amount (input amount divided by the exchange rate) at both the commodity and accounting levels. Banner Finance uses the converted amount for available balance checking; this is the amount that posts to the ledgers. To view the converted amounts, navigate to the Currency Conversion Window. Select Count Hits from either the Quantity or Unit Price fields in the Change Order Commodity Data Window or from anywhere within the Change Order Accounting Data Window.
Commodity Tax Information

If you use the tax features of Banner Finance, enter the Default Tax Group Code on the System Control Maintenance Form (FOASYSC) to create a default tax group. You can establish tax groups at the Ship-To or commodity levels. When the header record is created, the system looks to the Ship Code for a tax group. If none exists, the form defaults in the Default Tax Group from FOASYSC. At the commodity level, the form looks to the commodity for a tax group. If there is no commodity tax group, it defaults from the header. You should always set up a no-tax group in the Tax Group Table to use when either an entire document or certain commodities on a document are not to be taxed. You can view the tax calculations and see how the system distributes them by selecting Next Set of Records from either the Commodity or Accounting Data Windows. You can direct the Banner Finance System to calculate tax rates in a simple or compounded manner at the commodity level.
2-220
November 2010
Balancing/Completion Window
The Balancing/Completion Window displays summary information. The amounts that display on the Balancing /Completion Window reflect summary information for the entire order (items that you did not change in addition to items you changed or added). Click or select Complete to complete this document and return to the main window.
Querying a Change Order

Special conditions exist when you query an unposted change order on the Purchase/ Blanket/Change Order Query Form (FPIPURR). The value for several fields varies depending upon whether you completed, approved, and posted the change order, and whether Document Level Accounting was used on the original document. If the change order has not yet been posted, the Total Amount field in the Key Information on FPIPURR will differ from the amount you enter on the change order by the additional charge amounts, regardless of whether Document Level or Commodity Level Accounting is in effect. If the change order has not yet been posted and Document Level Accounting is in effect, the following fields differ: In the Accounting Data Window, the Commodity Amount fields reflect the amount of the current commodity totals. The Accounting Amount fields reflect the change to amounts prior to posting and the actual change, subsequent to posting. In the Balancing/Completion Window, the Header, Commodity, and Status columns reflect the current commodity amounts rather than the total purchase order consolidated amounts and status. Once you post the change order, these fields reflect the changes.
Processing a Blanket Order

Banner Finance enables you to control spending against a blanket order either at the Document total or Item level. The Purchase Order Form (FPAPURR), Change Order Form (FPACHAR), and Invoice/Credit Memo Form (FAAINVE) display the Blanket Order Remaining Balance in the commodity window when appropriate. If you exceed the Blanket Order Amount, you receive an error in the Purchase Order Form (FPAPURR) and a warning in the Invoice/Credit Memo Form (FAAINVE). On the Change Order Form (FPACHAR), you can reduce or increase the blanket order but you receive an error if you attempt to reduce the Remaining Balance below the current Remaining Balance.
November 2010
2-221
These forms, in addition to the cancellation forms (FPAPDEL, FPACDEL, and FAAINVD) also update the Blanket Order Remaining Balance Table (FPRBLAO). This table provides the information that appears on the Blanket Order Activity Form (FPIBLAR). The Purchase/Blanket/Change Order Query Form (FPIPURR) and the Invoice/Credit Memo Query Form (FAIINVE) display the Blanket Order Remaining Balance. Note that the system issues blanket orders for gross rather than net amounts. All validation against the Blanket Order Remaining Balance is against the approved amount (quantity x unit price), not inclusive of taxes or discounts. The Posting Process (FGRACTG) updates the Remaining Balance column of the new Blanket Order Remaining Balance Table (FPRBLAO). Prior to the posting update, the Pend column on the Blanket Order Activity Form (FPIBLAR) shows Y. Once the system posts a document associated with a blanket order, this field appears null, unless the posted document is a cancellation. Cancellations display a C in the Pend column. The Blanket Order Remaining Balance that displays on the transaction forms always includes pending as well as posted activity. However, the two situations listed below may create confusion. Keep in mind: Regardless of whether you control the blanket order at the Document total or Item level, the Posting Process (FGRACTG) updates the item Remaining Balance. This means that if you control a blanket order at the Document total level, the Blanket Order Remaining Balance for a given item could be negative and display as such, even though the overall balance is positive. When you create a purchase order or an invoice directly against a blanket order, the Blanket Order Remaining Balance displays once you create the transaction. Both types of transactions reduce the Blanket Order Remaining Balance by the amount of the transaction.
Blanket Order Remaining Balance

An invoice against a purchase is slightly different than an unencumbered invoice. At the point when you process an invoice against a purchase order, the system has already adjusted the Blanket Order Remaining Balance to reflect the purchase order. The Posting Process (FGRACTG) determines if the invoice amount is greater than the purchase order amount for the item for which you pay. If this is so, the system adjusts the Blanket Order Remaining Balance to reflect the difference. If the invoice amount is less than or equal to the purchase order item amount, there is no adjustment to the Blanket Order Remaining Balance. The result is that when you pay for an invoice against a purchase order against a blanket order, the Blanket Order Remaining Balance field does not display on the invoice form.
2-222
November 2010
Also, when you query the activity on the Blanket Order Activity Form (FPIBLAR), the invoice record shows a Transaction Amount of 0.00 prior to when you post the invoice. Once the invoice is posted, the Transaction Amount field reflects any adjustments you make during the posting process.
Termination Date
The system uses the Termination Date to determine whether or not a blanket order is still open. You can change this date with the Change Order Form (FPACHAR) as long as the new Termination Date is not earlier than the dates of the existing purchase order or invoice activity against the blanket order. This means that a blanket order can have a balance of zero and the Invoice/Credit Memo Form does not prevent you from paying invoices against the blanket order. If this occurs, the Blanket Order Remaining Balance field is highlighted on the Invoice/Credit Memo Form (FAAINVE).
Blanket Order Remaining Balance

The Blanket Order Remaining Balance field in the Purchase Order Commodity Data Window or Currency Conversion Window of FPAPURR displays the remaining balance of the blanket order and Purchase/Blanket/Change Order Query Form (FPIPURR) only when a purchase order is accountable to a blanket order. When you enter a quantity in a purchase order or you change a unit price, FPAPURR checks the remaining balance of the blanket order. Based on the type of document control, FPAPURR determines if you will exceed this balance. If it appears that you may exceed the blanket order by the new amount (quantity x unit price), an error message displays and you are unable to enter this item. If the new amount is acceptable (that is, does not exceed the total amount or item level) the remaining balance of the blanket order is redisplayed to reflect the change. The system performs blanket order checking twice: once when you calculate the commodity extended amount, and again when you complete the purchase order. This enables other documents to access the same blanket order between the time you enter the purchase order commodity and the time that you complete it. Once you complete the document, the system updates the remaining balance of the blanket order, and you may not make any other modifications.
Posting the Purchase Order

When the document is complete, the system places a record in the Blanket Order Remaining Balance Table (FPRBLAO). FPRBLAO calculates the remaining balance of the blanket order. In this scenario, FPRBLAO determines that you created a document against a blanket order, and it has not posted. Therefore, the system does not update the remaining balance of the blanket order in the Purchase Order Detail Goods Table (FPRPODT). Once you execute posting, the system executes FPRBLAO and FPRPODT to reflect the document remaining balance.
November 2010
2-223
If the purchase order does not pass the approvals process, the system deletes the record in FPRBLAO, and removes the document amounts from the blanket order balances that remain. Once the purchase order is complete, the system inserts a record into FPRBLAO.
Note Remaining balances that display on blanket order, purchase order and change order windows display in foreign currency, not base currency, if you use currency codes. Remaining balances display specific to document total control and item control.
You can review the activity for the blanket order or the purchase order on the Blanket Order Activity Form (FPIBLAR).
Commodity Level Accounting With a Purchase Order

When you assign requisition line items to a purchase order, the accounting distributions are brought forward based on the amounts. Based on these amounts, the system computes percentage relationships. Since commodities are brought forward as individual line items on the purchase order, then the amounts and percentages are exactly the same as the requisition.
Assigning Requisitions to a Purchase Order

Commodity codes affect how you transfer commodities from requisitions to purchase orders. When you enter a requisition, a detail commodity code represents the specific item you intend to purchase and ensures that the commodity transfers to the purchase order as a unique item. If you use a high level commodity code, the text feature can explain the specific item you intend to purchase. This text ensures that a unique item appears in the purchase order, provided that you exercise the Copy Text option in the Purchase Order Assignment Form (FPAPOAS). If you do not use a commodity code, then you should probably enter a description and possibly additional text. This free form description ensures, in most cases, that a distinctly identified item appears in the purchase order. The Purchase Order Assignment Form provides the capability for a buyer to select items from a single requisition or multiple requisitions for inclusion in a particular purchase order.
2-224
November 2010
Opening and Closing Items on a Purchase Order or Requisition

Use this procedure to open/close one or more items on a purchase order document or a requisition document. You can also use this procedure to open or close the entire document.
1. Access the Encumbrance Open/Close Form (FPAEOCD). 2. Enter the code for a document in the Document Number field. If you want the
system to generate a document code for you, enter NEXT.

Note All document codes created by this form begin with an asterisk (*). 3. Perform a Next Block function. 4. Select the action you want to perform from the untitled pull-down list. 5. (Optional) Enter a new Document Transaction Date. 6. Perform a Next Block function. 7. Enter the document number of the purchase order or requisition. 8. (Optional) Select the Close All Items check box if you want to close all items
associated with the specified requisition or purchase order. The title of this check box depends on the action you selected in Step 4. Select the Reopen All Items check box if you want to reopen all items associated with the specified requisition or purchase order.
9. (Optional) Select the Change Encumbrance check box if you want to change the
encumbrance amount for the document. If you want to close all of the items on a requisition or purchase order document or you want to close the last open item on a document, you must select the Change Encumbrance check box and enter the appropriate encumbrance change amounts.
10. Perform a Next Block function to access the Commodity Information window and
other windows required to perform the action you selected in Step 4. These windows will be stacked and visible simultaneously.
November 2010
2-225
11. Select the check boxes of the items you want to reopen or close.
If you selected the Close All Items or Reopen All Items check box in Step 8, Banner automatically select the check boxes of the appropriate items.
12. (Optional) Perform a Next Block function to access to Accounting Information
window. This window appears only when you select the Change Accounting check box on the main window. You must fill out the Accounting Information window if you want to close an entire purchase order or requisition document, or if you want to close the last open item on a document.
13. Click Complete in the Options menu to complete the document and submit it for
posting.
Procurement Card (PCard) Processing

PCard processing integrates Procurement Card transactions with Banner Finance. Institutions that use this process can perform the following tasks. Credit card assignment (default FOAPAL, Cardholder, Business Manager, and Account Manager for each PCard). Payment cutoff schedule for different credit cards such as American Express, Visa, Discover, and MasterCard. Override default FOAPAL and date fields and change vendors on the Purchase Card Transaction: Document Information Form (FAAINVT). This section highlights the types of information you will need to enter into Banner to set up PCard. For additional information about specific PCard processes, such as the Purchase Card Transaction Process (FAPCARD) and the Invoice Feed Process (FAPINVT), please refer to the Reports and Processes chapter.
Considerations Before Using PCard Processing

You must create a process (such as SQL*Loader or Pro*C) that reads a bank PCard flat file containing credit card company information, then loads data into the Banner Temporary Purchase Card Transaction file (FATCARD). It is recommended that only one bank file be loaded into FATCARD for processing at any one time. Taxes are not used. The transaction detail is at the total dollar level and is not itemized. If you use taxes, the NT tax group code is inserted automatically into the invoice for tax purposes. The Finance Refund Checks Interface (FURAPAY) process
2-226
November 2010
already handles this, as does the Invoice Generation Process (FAPINVT) modeled after FURAPAY. Currency conversion is not used. Conversion information is passed into the bank files. Because the base currency transaction amount is always loaded, there is no need to include the converted information for the foreign amount.
PCard Setup Process Flow
1. On FOMPROF, you can select the Purchase Card Override check box to establish
authority for a user to update the information on FAAINVT. Although an account manager or business manager must have a user profile established on FOMPROF, they do not require this override authorization since this would not limit the transactions they can process.
2. On FTMCARD, you can assign the account manager and create the relationship
between the cardholder and the PCard, default FOAPAL information, establish daily limits, etc. You can also associate text and important information to individual cards.
3. On FTMPCSH, establish the payment schedule for the card.
November 2010
2-227
4. You can use the System Data Maintenance Form (FTMSDAT) to create Seed Data on
the System Data Validation Form (FTVSDAT). Refer to the Configure Banner on page 2-228 section for additional information.
Initializing PCard
The following steps are required to enable PCard Processing.
1. Configure Banner on page 2-228 2. Load PCard Data on page 2-232 3. Run PCard Process on page 2-233
Configure Banner
Configuration and implementation of the PCard interface requires initial data entry to include credit card definition, payment scheduling, cardholder information and defaults, and PCard override capabilities by user ID. You also need to translate the company numbers provided on the bank flat file into campus codes The following Banner objects are involved in PCard setup: Purchase Card Maintenance Form (FTMCARD) Payment Cutoff Schedule Maintenance Form (FTMPCSH) User Profile Maintenance Form (FOMPROF) System Data Maintenance (FTMSDAT) Company Numbers and Campus Codes (FTMSDAT) These numbers are user defined; a different company number can exist for each campus. A liability fund, monthly liability clearing account, and daily liability clearing account are defined for each company/campus. These are used to generate liability journal vouchers from the Purchase Card Transaction Process (FAPCARD).
SDAT Entry to Identify Liability Fund by Campus Column Name Value
Entity/Usage Code (FTVSDAT_Sdat_Code_Entity) Attribute Code (FTVSDAT_Sdat_Code_Attr)
FAPCARD
LIABILITY_FUND
2-228
November 2010
Column Name
Value
Optional Code #1 (FTVSDAT_Sdat_Code_Opt_1) Chart of Account (FTVSDAT_Coas_Code) Title (FTVSDAT_Title) Short Title (FTVSDAT_Short_title) Data (FTSDAT_Data)
COMPANY/CAMPUS CODE (user defined) B (user defined) Campus Liability Fund Campus Fund 1105 (user defined)
SDAT Entry to Identify Monthly Liability Account by Campus Column Name Value
Entity/Usage Code (FTVSDAT_Sdat_Code_Entity) Attribute Code (FTVSDAT_Sdat_Code_Attr) Optional Code #1 (FTVSDAT_Sdat_Code_Opt_1) Chart of Account (FTVSDAT_Coas_Code) Title (FTVSDAT_Title) Short Title (FTVSDAT_Short_title) Data (FTSDAT_Data)
FAPCARD
MONTHLY_LIABILITY_ACCT
COMPANY/CAMPUS CODE (user defined) B (user defined) Campus Monthly Liability Acct Month Clear Acct 2111 (user defined)
November 2010
2-229
SDAT Entry to Identify Daily Liability Account by Campus Column Name Value
Entity/Usage Code (FTVSDAT_Sdat_Code_Entity) Attribute Code (FTVSDAT_Sdat_Code_Attr) Optional Code #1 (FTVSDAT_Sdat_Code_Opt_1) Chart of Account (FTVSDAT_Coas_Code) Title (FTVSDAT_Title) Short Title (FTVSDAT_Short_title) Data (FTSDAT_Data) Processing Options
FAPCARD
DAILY_LIABILITY_ACCT
COMPANY/CAMPUS CODE (user defined) B (user defined) Campus Daily Liability Acct Daily Clear Acct 2211 (user defined)
You can configure PCard processing to produce one of three different types of output: Liability journal vouchers and zero payment invoices Liability and direct charge journal vouchers only Direct payment invoices and no journal voucher
Liability Journal Vouchers and Zero Payment Invoices
Set up this option as follows: Set the FAPCARD_System_ID in SDAT to C. Set the FAPINVT _System_ID in SDAT to A or N and Z (for example, AZ or NZ). The journal voucher debits the daily clearing account and credits the monthly clearing account in the liability fund as defined on the SDAT records for the company/campus. The zero payment invoice debits the expense FOAPAL on the Purchase Card Transaction: Document Information Form, FAAINVT (defaults from the Purchase Card Maintenance Form, FTMCARD) and credits the daily clearing account. Payment to the bank is made using a normal invoice to debit the monthly clearing account.
2-230
November 2010
Monthly clearing acts to provide the total outstanding liability on all PCard transactions at any point in time. The daily summary from the activity is credited to this account. The sum of the daily summary activity represents the total amount due the bank on all received transactions, month to date. Posting the invoiced amount from the bank as received and due clears this account to the system accounts payable account from where the check or wire is cut. The daily clearing account acts to relate the number of transactions that have yet to post to the operating ledgers. This is the debit side of the monthly clearing entry. All individual items ultimately relieve the daily summary debit as they post, generating a credit from the individual transaction whose debit is the appropriate department's expense as entered/ defaulted on the Purchase Card Transaction Maintenance Form (FAAINVT).
Liability Journals Only
Set up this option as follows: Set the FAPCARD_System_ID in SDAT to S. Do not execute the Invoice Feed process (FAPINVT). The journal voucher debits the expense FOAPAL defined on the cardholder record on the Purchase Card Maintenance Form (FTMCARD) and credits the monthly clearing account defined on the SDAT record for the company/campus. Invoices are not processed. Payment to the bank is made using a normal invoice to debit the monthly clearing account.
Invoices Only
Set up this option as follows: Set the FAPCARD_System_ID in SDAT to N. Set the FAPINVT_System_ID in SDAT to A or N and N (for example, AN or NN). The Purchase Card Transactions process (FAPCARD) does not produce a journal voucher. Normal direct pay invoices are generated by the Invoice Feed process (FAPINVT).
November 2010
2-231
These invoices debit the FOAPALs entered on the Purchase Card Transaction: Document Information Form, FAAINVT (defaults from the Purchase Card Maintenance Form, FTMCARD) and credit the normal accounts payable account. These invoices also generate checks payable to the vendor specified on FAAINVT. If payment is to be made to the bank, verify that the bank is either the vendor or the check vendor on FAAINVT.
Load PCard Data

PCard control and detail records are transmitted to you daily by the bank of record. Data received varies according to credit card type: Visa, Master Card, American Express, or Discover. It is expected that you will populate the Temporary Purchase Card Transaction file (FATCARD) with your own process, such as SQL*Loader, C, etc. It is recommended that only one bank file be loaded into FATCARD for processing at any one time. The following diagram shows the process flow for loading PCard data:
2-232
November 2010
Start
Bank
Daily PCard Distribution
Flat File
External Load Process
FATCARD
End
Run PCard Process

PCard processing involves the following steps.
1. Validate data. 2. Generate invoice. 3. Post payment.
Data Validation and Journal Voucher Generation The following Banner objects are involved in PCard data validation: FAAINVTPurchase Card Transaction Maintenance Form FABINVTPurchase Card Transactions Header Table
November 2010
2-233
FAPCARDPurchase Card Transactions Process FARINVTPurchase Card Transactions Accounting Table FATCARDTemporary Purchase Card Transactions Table FTVPCSHPurchase Card Payment Cutoff Schedule Table FTVSDATSystem Data Validation Table GUAMESGGeneral Message GURFEED Finance Transaction Input Table
FAPCARD Process Flow
FATCARD Validation
The Purchase Card Transaction Process (FAPCARD) validates the FATCARD table for sum and duplication errors.
2-234
November 2010
If errors are found, a report is produced and the transactions are not processed. If errors are not found, the transactions are loaded into the FABINVT and FARINVT tables, and the appropriate journal voucher, if any, is entered into the GURFEED table for standard interface processing (SYSTEM ID equals FAPCARD). The FATCARD population step does not have to be performed if you only want to create invoices. FABINVT and FARINVT tables can be populated directly. You can also set up parameters that do not generate a journal voucher and still populate the FATCARD table using the Data Validation feature. The system calculates the payment due date using data found in the payment schedule table (FTVPCSH). The account manager is notified via GUAMESG as soon as the FATCARD table has been validated and processed. If you have access to the Purchase Card Transaction: Documentation Information Form (FAAINVT), you can perform the following actions. Correct transactions that are missing FOAPAL elements. Change the feed to finance date. Change the vendor. Split account distributions. The system also analyzes the one-time vendor status. The Vendor ID can be linked on this form to allow a feed to a real vendor instead of a one-time vendor. Quick Navigation is allowed to the Vendor Maintenance Form (FTMVEND) to create a vendor.
Journal Voucher Generation
Liability journal vouchers are generated for GURFEED population based on the SYSTEM_ID in SDAT as follows: Generate liability JV with pre-defined fund and clearing accounts in SDAT. Generate liability JV with expense FOAPAL as defined on the cardholder record (Purchase Card Maintenance Form, FTMCARD) and liability account defined in SDAT. Do not generate liability JV. Invoice Generation The following Banner objects are used in PCard invoice generation: FABINVHInvoice Header Table FABINVTPurchase Card Transactions Header Table FAPINVTInvoice Feed Process
November 2010
2-235
FARINVAInvoice Accounting Table FARINVTPurchase Card Transactions Accounting Table FGRTRNRTransaction Error Report FOBAPPDApproved Document Table FOBUAPPUnapproved Document Table FORAPPLApproval Process FTVSDATSystem Data Validation Table The following diagram shows the process flow for FAPINVT:
2-236
November 2010
November 2010
2-237
The batch Invoice Feed Process (FAPINVT) is used to generate invoices in Banner Finance. Transactions are extracted from FABINVT/FARINVT and populated directly into the invoice tables FABINVH, FARINVC, and FARINVA. This is done based on feed date. Run this job nightly via standard sleep/wake functionality. This program is modeled after the FURAPAY process without the Accounts Receivable requirements and provides the ability to perform the following functions: Create a normal payment voucher. Create a zero payment voucher. The Zero Payment Invoice/Credit Memo does not generate a check to the merchant. This feature is intended for clients who pay the bank at the end of the month but who do not pay the merchant. This process records information by vendor to track purchasing information via a setting on the System Data Validation Form (FTVSDAT). Initiate bank payment via a check run or ACH. When an ACH vendor is attached to the purchase transaction, ACH information defaults into the invoice table (FABINVH). Use approvals processing. Populate the payment due date, invoice date, and transaction posting date fields. Use one-time vendors. Provide data for the reconciliation of daily suspense accounts that are first debited by a journal voucher and credited by the invoice transaction. Payment Posting The Posting Process (FGRACTG) identifies and manages zero payment invoices. This process posts the debit and credit side of the invoice accounting lines and marks the zero payment invoice as paid. No check is ever attached to zero payment invoices marked as Paid. A zero payment invoice is required to use the processes associated with the INNI, INNC, and DNNI rule class codes. The invoice must be marked as P (paid). This prohibits the invoice from being picked up on the invoice selection report. Since the Zero Payment invoice ultimately has a zero dollar amount-with a positive amount reflected in the expense line and a minus amount for the campus fund and liability account-such an invoice would remain in perpetuity as never being paid or selected for check processing, especially one-time vendors. The process, Mark Zero Payment Invoices as Paid, values the following indicators to P (Paid):
2-238
November 2010
FABINVH_OPEN_PAID_IND FARINVC_OPEN_PAID_IND FARINVA_OPEN_PAID_IND
The Posting Process processes the Zero Payment Invoice as if it had been selected for checks processing/accounting and marked as paid.
PCard Forms
This section includes high-level descriptions of each form used in PCard processing. For detailed information about each form, please refer to the online help.
Purchase Card Transaction Maintenance Form (FAAINVT)

This form's security should be managed via normal Oracle role security. Two levels of control are provided using this form, one for account or business managers, and the other for specially designated users. Any user can view any PCard Transaction through normal role security. However, only the account/business manager can make changes, such as to correct FOAPALs or redistribute FOAPALs, for those PCard Transactions that belong to them. Additional security is added to provide specially designated users (FOMPROF override check box) the ability to change anything on the PCard Transaction that can be changed. Account/Business Managers Account/business managers can perform all of the following functions Correct transactions missing FOAPAL elements. Change the feed date. Split account distributions. Determine vendor status. Use quick navigation to FTMVEND to create a vendor. Specially Designated Users Specially designated users, with an override capability assigned on the User Profile Maintenance Form (FOMPROF), can perform all the functions of account or business managers.
Purchase Card Maintenance Form (FTMCARD)

This form stores and associates the cardholder for each card issued, default FOAPAL information, an account manager (person to be notified), and other key information. Most of this form's stored data is informational only.
November 2010
2-239
Remember the following: Both the account manager and the business manager must be pre-defined on the User Profile Maintenance Form (FOMPROF) but do not need the override box checked. Cardholder ID and Sponsor ID must be pre-defined in the SPRIDEN table. The use of Fund/Orgn security is not enforced on this maintenance form for setup. Standard defaulting logic applies for all FOAPAL elements.
Payment Cutoff Schedule Maintenance Form (FTMPCSH)

PCard payment cutoff schedule information is managed on this form using the FTVPCSH table. The key to this form is the credit card company defined on the System Data Maintenance Form (FTMSDAT), and the calendar year. Payment cutoff schedule information for credit card companies is entered using date per month.The system uses this information with the PCard Interface Process (FAPCARD) to calculate the payment due date on the invoice (that is, the cutoff date plus the cycle days defined on SDAT). A copy function is provided in the form's Key Block to duplicate an existing payment schedule from a prior year or credit card company to a new year or credit card company. The system calculates the difference in the year being copied from into the year being copied to and adds the appropriate year to the Start Date, End Date, and Payment Cutoff Date. This form is modeled after the Fiscal Year Maintenance Form (FTMFSYR) and permits different payment schedule cutoff dates per year for American Express. This format is based on a calendar year, not a fiscal year, which allows for any changes in cutoff dates during the year(s). This should be a highly secured form using normal Oracle role security.
Purchase Card Query Form (FAICARD)

This form displays much of the same information maintained through the Purchase Card Maintenance form (FTMCARD) but, for security purposes, excludes the Mothers Maiden Name field. It also includes transaction history information about the card.
Merchant Category Code Validation Form (FTVMCAT)

This form is used to establish valid merchant category codes and their descriptions. To access the values from this form, request an LOV in the Merchant Category field on the Purchase Card Maintenance Form (FTMCARD).
2-240
November 2010
User Profile Maintenance Form (FOMPROF)

This form includes a check box for Purchase Card Override authority (the FOBPROF table). Normally, only an account manager can adjust the accounting distribution to correct or redistribute amounts on the Purchase Card Transaction form (FAAINVT). This override feature allows the specified user ID to perform account manager functions, including changes to the feed date, vendor, and expense account distribution on any PCard transaction. Account and business managers entered on the Purchase Card Maintenance Form (FTMCARD) do not require this override authorization, since this would not limit the transactions they can process.
Entity Name/ID Search Form (FTIIDEN)

When this form is called from either the Purchase Card Maintenance Form (FTMCARD) or the Purchase Card Transaction: Document Information Form (FAAINVT), the All check box in the Key block is selected. This enables the system to search for all records in SPRIDEN.
Bid Processing
The first step in creating a bid from a requisition is to create a bid with the Bid Creation Form (FPACTBD). You do this by consolidating information from existing requisitions.
1. Enter a buyer code in the Buyer Code field. Click Buyer Code or select List to
display a list of buyer codes. You may only select a buyer that has open requests. Select Exit with Value to retrieve a buyer.
2. Select Next Block. 3. In the Bid Number field, type NEXT to generate a new bid number or click Number
or select List to select from a list of existing bids. To continue the bid process, access the Bid Header Form (FPABIDH).
1. Enter the bid number you established on the Bid Header Form (you can click Bid
Number or select List to view a list of existing bid numbers) and enter a bid description.
2. Verify that the Buyer and Commodity windows default from FPACTBD and that the
Effective Date defaults to the system date.

3. Enter the Effective Date (if different from system date) and the Termination Date.
November 2010
2-241
4. Enter Y in the Approved/Printable field.
Continue the bid process using the Prospective Bidders Form (FPAPRBD).
1. Verify that the Bid Number and Description fields default from FPABIDH. 2. Verify that the commodity information associated with this bid defaults into the
commodity information on this form.

3. From the Vendor field, click Vendor or select List to enter a vendor code. 4. Additional prospective vendors are added in the same manner as the first vendor;
enter the bid number and vendor code for each additional vendor. Continue the bid process using the Process Submission Control Form (GJAPCTL).
1. In the Process field, enter FPTBIDD (Print Bid Form Test Patterns Process). Verify
that List Fields, Execute Query, and Exit with Value are available.
2. Select Submit on the Hold/Submit indicator. 3. Enter Alternate User ID and Alternate Password. 4. Verify that a bid test pattern is printed. 5. Using GJAPCTL, enter FPABIDD (Bid Form Print Process) in the Process field.
Verify that List Fields, Execute Query, and Exit with Value are available. Select Submit on the Hold/Submit indicator. Enter Alternate User ID and Alternate Password.
6. Verify that you printed the Requests for Bids (RFB).
Receiving Processing
Creating a Receipt of Goods
Enter a receipt of goods on the Receiving Goods Form (FPARCVD). To enter a receipt of goods, perform the following steps:
1. Access FPARCVD from the Receiving Process Menu (*FINRECV). Use this form to
enter or update receiving header and detail information on a packing slip.

2. Enter the receiver document code number or type NEXT to have the system generate
a number for you. Click the search button or request a List to select an existing receiver document and packing slip number.
2-242
November 2010
3. To create or view comments associated with the receiver document, click the View
Receiving Text link to access the General Text Entry Form (FOATEXT).
4. Select Next Block. 5. The Receiving Method and Carrier fields are optional. The Date Received and the
Received By fields automatically default into the form. Enter the Date Received. This is a required field.
6. Select Next Block to enter packing slip information.
Entering Packing Slip Information

1. Enter the Packing Slip number. All purchase orders on the packing slip must have the
same vendor. You may use the Search feature or request a List to select from a list window. Bill of Lading is an optional field.
2. To create or view comments associated with the packing slip, select the View Packing
Slip Text link to access the General Text Entry Form (FOATEXT).
3. Select Next Block to enter purchase order information.
Entering Purchase Order Information

Purchase orders are not required to be closed out prior to invoicing. As a result, invoicing may be performed before receiving.
1. Enter the Purchase Order number for the purchase order associated with the packing
slip. This is a required field. You can navigate to one of the following areas from the Purchase Order field: To access the Purchase Order Validation Form (FPIPOHD) click on the search button, or select List. To view the open purchase orders click on the search button or select Next Set of Records to access the Open Purchase Orders by Vendor Form (FPIOPOV). To access the Purchase/Blanket/Change Order Query Form (FPIPURR), click on the search button or select Count Hits. This form enables you to view a specific purchase order document.
2. Click Receive All Purchase Order Items link if all the items on the purchase order are
being received for the first time all at once. Receiving detail records are then created for all the items on the purchase order. In addition, the system creates or updates all temporary fixed asset tags at this time.
3. Select Next Record to enter another purchase order.
November 2010
2-243
4. If you only receive a few items from this packing slip or if you are unaware of the
item number, click Select Purchase Order Items link to access the Receiving Goods PO Item Selection Form (FPCRCVP). This form displays all the items on the purchase order that you have not yet received on this packing slip.
5. To select the desired items, select Next Block and select the Add Item check box
next to the items you wish to receive.

6. The system creates detail items with a blank quantity. The Quantity/Amount and
Quantity/Amount Accepted fields on FPCRCVP are updated once the corresponding fields are updated in the Commodity Window of FPARCVD.
7. Identify whether receiver document is to Receive Items or Adjust Items by selecting
the appropriate radio group button. Receive Items functionality enters the receiver information into the system as normal positive transaction. The Adjust Items functionality enters receiver information into the system as a reverse or negative transaction to allow for correction of previously received amounts. This functionality may only be used when a previously received amount exists and may not be for an amount greater than the previously received amount.
Entering Commodity Information

All records that have been selected to exist on the packing slip display in the Commodity window of the Receiving Goods Form (FPARCVD). Use the scroll bar or Next Record and Previous Record to scroll through the existing records. The Commodity Window is displayed in one of two formats based on the Purchase Order Type of the purchase order document selected to be received. When the purchase order is a Regular Type the Commodity window is displayed based on quantity. When the purchase order is a Standing Type the Commodity window is displayed based on dollar amount. To enter information on the receiving detail record in the Commodity Window of the Receiving Goods Form (FPARCVD):
1. Scroll through the items to find the commodity you are receiving. 2. Select Next item to navigate to the FOB field. 3. Select the Final Received check box in order to indicate this receiver document is
intended to be the final receiver entered against the referenced purchase order. This indicator is carried forward and displayed on the Invoice/Credit Memo Form (FAAINVE).
4. Select Next Item and enter the Current - Quantity - Received field. If receiver
document is against a Standing Type purchase order, enter the Current Amount Received in the field.
2-244
November 2010
5. The U/M (Unit of Measure) default value comes from the purchase order. If the unit
of measure for the goods being received is different than that of the purchase order, enter the received quantity and the received unit of measure. The form converts the quantity into the unit of measure from the purchase order, as long as you make an equivalency entry on the Equivalency Maintenance Form (FTMEQUL). If no entry exists, an error message displays to notify you when you attempt to enter the quantity.
6. If items are rejected at delivery time, enter the Current - Quantity - Rejected and
the corresponding unit of measure for the rejected quantity. If the receiver document is against a Standing Type purchase order this field is not displayed.
7. The Suspense indicator appears selected when the received quantity exceeds the
tolerance specified in the Receiving Overage Tolerance field on the User Profile Form (FOMPROF).
8. If you have override authority (refer to the Receiving Override field on FOMPROF
to verify this), select the Override box and click or select Save. The Suspense indicator then appears cleared and you can use the record in the Receiving/Matching Process. If the commodity received is a stock item from an inventory purchase order, you must enter the primary location; you may also enter the sublocation. Otherwise, the Primary Location and Sub Location fields are not enterable. You can also refer to the following fields: The To Date - Quantity - Received field shows the total quantity received across all packing slips. If the receiver document is against a Standing Type purchase order, the To Date Amount Received is displayed in the field. The To Date - Quantity - Rejected field shows the quantity rejected at the time of delivery across all packing slips. If the receiver document is against a Standing Type purchase order, this field is not displayed. The To Date - Quantity - Returned field indicates the quantity returned at a later date across all return codes. If the receiver document is against a Standing Type purchase order, this field is not displayed. The To Date - Quantity - Accepted field shows the total quantity accepted across all packing slips. If the receiver document is against a Standing Type purchase order, this field is not displayed. The To Date Quantity Ordered field shows the original ordered quantity from the purchase order. If the receiver document is against a Standing Type purchase order, the To Date Amount Ordered is displayed in this field. To enter returns, use the Returned Goods Form (FPARTRN).
November 2010
2-245
Accounts Payable
The Banner Finance System enables you to reconcile the checks, deposits, and bankrelated transactions that you have processed to records that your installation maintains. All checks produced through the Check Processes update the Check Table (FABCHKS). All entries (including checks and deposits) produced through the system are stored in the Transaction Detail Table (FGBTRND).
Running Banner Bank Reconciliation

When you execute the Bank Reconciliation Report (FARBREC), it produces an outstanding check and deposit register. Although checks exist in both FGBTRND and FABCHKS, checks are not displayed twice on this report because they exist as values in the System Data Maintenance Table (FTVSDAT) that tell the system to exclude them. Anytime a bank code is used on a journal voucher (that is, interfaces), these entries will appear as deposits on this report unless you have excluded them on FTVDSAT (see Preventing Inclusion of Journal Voucher Rule Classes on page 2-248). You can manually enter the records that your installation maintains, or the records can be interfaced via electronic media. A description of the reconciliation process and the appropriate forms and reports follows.
1. Access the Bank Tape Reconciliation Form (FAABREC).
Use FAABREC to manually enter bank activity information from the bank statement or to view information downloaded to the bank tape table. If bank activity is interfaced via electronic media, the interfaced information appears on this form.
2. Enter information into the Bank Tape Reconciliation Form by indicating the Bank
code for the bank account you need to reconcile. Click Bank or select List to select a bank code from a list window. The system automatically retrieves the bank account number for both this bank account and your cash account.
3. Select Next Item to go to the Status Selection field. 4. Select All, Reconciled only, or Not reconciled in the Status Selection field.
All displays all check and deposit entries. Reconciled only displays the entries from the bank which reconciles to your institutions records. Not reconciled only displays entries for which there is no corresponding bank or institution matches.
2-246
November 2010
5. Select Next Block to enter detail information.
Before entering data, make sure that the Bank Account Number matches the bank account number on your bank statement.
6. Beginning with the first row of the Document column, enter data from the bank
statement as follows: Document - The document number for the transaction that appears on the bank statement. Transaction Type - Each transaction type is categorized as follows: Check, Deposit, Other, or Unknown. Use the appropriate transaction type to indicate the type of entry. Transaction Date - The transaction date that appears on the bank statement. Description - A description of the transaction. Amount - The amount of the transaction that appears on the bank statement. Internal Document Code - This is the document number that appears in your own records. For checks, this should be the same document number. Other transaction types may have different numbers. The system is able to reconcile transactions with differing internal and external document codes. The system copies the Document number into the Internal Document Code. Note that this references the Deposit field for cash receipt transactions on the Journal Voucher Entry Form (FGAJVCD). If you enter cash receipts without a value in the Deposit field on FGAJVCD, you cannot reconcile your receipts without processing an adjusting journal. The same is true if you use the Journal Voucher Quick Form (FGAJVCQ) to process cash receipts, as this field does not exist on the form. This value defaults if left blank. Status indicator - An unenterable field. The system displays an R as you reconcile items.
7. After you enter all the information, run the Bank Reconciliation Report Process
(FARBREC). This process matches records, updates the Status indicator field on the Bank Tape Reconciliation Form (FAABREC) with an R as appropriate, and then prints a report (FARBREC). FARBREC contains fields similar to those on the Bank Tape Reconciliation Form, with the addition of a column to indicate the bank amount. Also the Status indicator field displays as Recon Ind. The system does not enter a value in this field for items that you reconcile. Items that you do not reconcile show an indicator value of: G - If your amount is greater than bank amount. L - If your amount is less than bank amount. N - If there is no matching record.
November 2010
2-247
8. After each iteration of this job, make the appropriate adjustments on the Bank Tape
Reconciliation Form and/or your records, until you reconcile all your items.
9. Run the Bank Reconciliation Balance Report (FARBBAL) to produce a summarized
statement.
10. Run the Bank Reconciliation Activity Aging Report (FARAAGE). This report
provides an aging of reconciling items. For additional information on each of the reports mentioned above, refer to the reports documentation in the Reports and Processes chapter.
Preventing Inclusion of Journal Voucher Rule Classes

You can prevent certain journal voucher rule classes from being included in bank reconciliation by creating a record in the FTVSDAT table. Create this record by following these steps:
1. Enter FABCHKA in the Entity/Usage Code field. 2. Enter EVENT_CODE in the Attribute Code field. 3. Enter the names that you have assigned for each rule class in the Option Code #1
and #2 fields. For example: You may want to use OMIT1 or OMIT2 in the Option Code #1 field and a single alpha character, such as D, in the Option Code #2 field.
4. Type Omit_from_Bank_Reconciliation in the Description/Title field. 5. Make sure that the rule class that you wish to exclude is displayed in the Data field.
Populating the Bank Tape Table

When you feed information electronically, you must populate the Internal Document field with an appropriate value. Although this field is not required in the Bank Tape Table (FABBKTP), it is required in the Collector Table (FABBRCC).
Creating a New Vendor

Access the Vendor Maintenance Form (FTMVEND) from the Accounts Payable Table Menu (*FINAPTAB). This form enables you to create new vendors, or to modify existing vendor data (except for vendor name).To change the vendor name, use the Identification Form (FOAIDEN).
2-248
November 2010
To add a new vendor, perform the following:

1. Enter the assigned Vendor number or select Generate ID to access GOAMTCH. 2. Enter the name of the Corporation or the Last Name Prefix (if applicable), Last
Name, and First Name of the individual.

3. Select Next Block to enter detail information.
The default Procurement Type Code and the Accounts Payable Type Code fields are optional fields which streamline data entry on the procurement documents. If specified, the default Procurement Type Code defaults when you select the vendor for a requisition or purchase order. The Accounts Payable Type Code defaults on the Invoice/Credit Memo Form (FAAINVE). These fields only specify that a default exists; you need to create these addresses in the Address Window of the Vendor Maintenance Form (FTMVEND).
4. Select Collects All Taxes, Collects No Taxes, or Collects Selected Taxes from the
Collects Taxes pull-down list.

5. The Owner ID and owner name (unlabeled) fields are used to establish owner vendor
information for Doing Business As (DBA) vendors. If a vendor operates multiple business under the heading Doing Business As, the owner vendor is created as a 1099 vendor. When the DBA vendor is subsequently created, the owner vendors ID number is entered in the Owner ID field. The owner vendors name and tax identification number will now be referenced on the vendor records and 1099s of the affiliated DBA vendors.
6. Select Next Block to access the Vendor Types Window or Additional Information to
access the Additional Information Window.
Additional Information Window

1. Enter the Tax ID number for the vendor. The Federal Withholding and State
Withholding fields are optional. For the amounts you enter in the withholding fields to be effective, rule classes DDWI, DTWI, CDWI, and CTWI must be updated with a posting modifier on the G010 processing code for your sites withholding liability account. A withholding fund may also be entered.
2. The Income Type and Base Currency code fields are optional. Use the Search
feature or select List to view a list of valid codes for each field.
3. You may classify the vendor as a Domestic Carrier or a Foreign Carrier, as an In
State Vendor or Out of State Vendor, and may select One invoice per check or Many invoices per check.
November 2010
2-249
Vendor Types Window

The Vendor Types Window of the Vendor Maintenance Form specifies the vendor type codes associated with the vendor. A vendor may have multiple vendor types.
1. Use the Search feature for the Code field or select List to select from a list of vendor
type codes.
2. Select Save. 3. Select Next Block to access the Address Window.
Address Window
The Address Window enables you to define the appropriate vendor address and phone number information. A specific vendor may be assigned multiple address codes and sequences.
1. Enter the desired Address Type and Sequence Number, and enter the address
associated with these codes.

2. If you specified either of the optional Address Type Codes in the main window of
FTMVEND, enter the address information for those defaults in this window. To delete an address, use the Identification Form (FOAIDEN). The City field and either the State or Province or the Nation field is required. When you enter State or Province, the ZIP or Postal Code field is also required. In addition, Telephone Type and telephone number fields are available. The Telephone Type field defaults from the address type, but is enterable.
3. Use the Search feature for Telephone Type or select List to view a list of valid codes.
You can enter the primary phone number in the telephone number fields; however, to view or add additional phone numbers for an address code and sequence, you must access the Telephone Validation Form (STVTELE).
4. Select Save and select Next Block to access the Taxes Collected Window.
2-250
November 2010
Taxes Collected Window

Use the Taxes Collected Window to define which taxes you wish to collect. This window is only accessible when you define a vendor that Collects Selected Taxes on the header window.
1. Enter the appropriate tax code(s). Select the Search feature for the Tax Code field or
select List to select a valid tax code. The invoice process uses these values to determine which tax amounts to pay to the vendor and which tax amounts to pay to the Taxing Authority.
2. Enter the Effective Date, which is a required field. 3. Save. Note To validate the newly created information, use the Entity Name/ID Search Form (FTIIDEN).
Establishing Tax Information

To control tax calculations in Banner Finance on a system-wide basis, select the Tax Processing field on the System Control Maintenance Form (FOASYSC) and supply a Default Tax Group Code in the Tax Processing Information Window. If you set these values, the system calculates all taxes on all purchase orders and invoices. Access both the Tax Rate Code Maintenance Form (FTMTRAT) and the Sales/Use Tax Group Maintenance Form (FTMTGRP) from the Accounts Payable Table Menu (*FINAPTAB).
Using the Tax Rate Code Maintenance Form (FTMTRAT)

Use the Tax Rate Code Maintenance Form (FTMTRAT) to establish the individual tax rates applicable to your installation. The Tax Rate, Description (Unlabeled), Rate, Priority, and Pay Tax To fields are required. The Active Status box defaults from the system. When the Active Status box is unchecked (inactive), the Last Activity Date field defaults. The Effective Date defaults to the system date. Explanations for several tax parameters you may set on this form appear below.
Note After you enter all of the desired data on this form, remember to click or select Save.
November 2010
2-251
Compounding Taxes
To support cases in which the system calculates taxes in a compounded manner, there is a Priority field, which is required. To compound taxes, assign a number to each tax rate. This number should denote the order in which the system calculates taxes. For example, if you compute Duty first, the priority number is 1. Another tax rate, Federal Sales Tax, is to include Duty in its calculation. Therefore, the Federal Sales Tax priority is 2.
Including Additional Charges

Ordinarily, the system only calculates taxes for the Approved Amount (quantity x unit price). However, if you check the Include Additional Charges box, the additional charges will be added to the Approved Amount to compute taxes.
Including Discounts
Ordinarily, the system calculates taxes for the Approved Amount (quantity x unit price). However, if you check the Include Discount box, the discount amount will be deducted from the Approved Amount to compute taxes.
Establishing a Taxing Authority ID

In cases where the vendor does not collect taxes, but you remit them directly to a governing body instead, you can establish a taxing authority identification code. Enter this ID number in the Taxing Authority ID field. You maintain valid values as vendors. If the Pay Tax To? value is either C (Pay Vendor if a Collector) or T (Always Pay Tax to Taxing Authority), you must enter a Taxing Authority ID.
Identifying to Whom You Pay Taxes

Use the Pay Tax To field to specify to whom you intend to pay taxes, and when. To pay taxes to the vendor in all cases, enter V. To pay taxes only to those vendors who are tax collectors, enter C. Finally, to pay only to the taxing authority, enter T. If you specify either C or T, be sure to enter a valid Taxing Authority ID.
2-252
November 2010
Specifying a Liability Accounting Distribution

When you pay taxes to a taxing authority, specify an accounting distribution to record the liability when the invoice or direct cash receipt posts. For an invoice, the system draws the tax amount that awaits payment to the taxing authority out of the accounts payable account and records it in the liability account that you create for this purpose. For a direct cash receipt, this process is reversed. To specify this type of accounting distribution:
1. Click Accounting Information or select the menu option to access the Tax Rate
Accounting Information Window.

2. Enter the Chart of Accounts and Fund codes in the respective fields. 3. Enter the Liability Account field if the Pay Tax To field displays either a C or a T.
Specifying a Default Rebate Accounting Distribution

You can enter the default rebate percentage and accounting distribution for the system to calculate rebates at the time the invoice is created. If you have more than one rebate percentage associated with the same tax rate, you must enter the multiple rebate percentages using the Rebate Maintenance Form (FTMREBT) and associate each rebate percentage with individual or combined FOAP (Fund, Organization, Account, Program) attributes. The FOAPAL on the Invoice/Credit Memo Form (FAAINVE) or the Direct Cash Receipt Form (FGADCSR) will be matched with the data on FTMREBT to retrieve the appropriate rebate percentage; if there is no match, the rebate percentage on the Tax Rate Code Maintenance Form (FTMTRAT) will be used as the default rebate percentage to calculate rebate amounts.
Establishing Multiple Rebate Percentages

Using the Rebate Maintenance Form (FTMREBT)
The default rebate accounting distribution on FTMTRAT must be set up before you can insert records on FTMREBT for the tax rate. Use the Rebate Maintenance Form (FTMREBT) to establish multiple rebate percentages for a tax rate and associate each rebate percentage with individual or combined FOAP
November 2010
2-253
attributes. An invoice or direct cash receipt will use the rebate percentage that most closely matches the transaction FOAP.
1. Enter the Tax Rate code in the Key block and select Next Block. 2. The Effective Date defaults to the system date. 3. The Tax Rate Code Description and the Tax Rate Code Percent will default from
the Tax Rate Code Maintenance Form (FTMTRAT), and they cannot be overridden.
4. Rebate Percent is a required field. 5. The Chart of Accounts related to the FOAP attributes for this percentage should be
entered.
6. The rebate accounting distribution will default from FTMTRAT and can be
overridden.
Specifying Distribution Information

The FOAP ranges associated with the Rebate Percent entered on the header block are entered in the Distribution Information Window. If a value is entered in the From field and if the To field is left blank, then the To field is the same as the From field. When a rebate percentage must be determined for an invoice or a direct cash receipt, the data on FTMREBT is scanned and the Rebate Percent is selected whose FOAP best matches the documents FOAP. On FTMREBT, any FOAP specification that has a single element (with nothing in the To field) is considered a better match to the document than a range specification; a narrow range produces a better match than a wide range. The Fund is checked first; if more than one row qualifies with the same priority, the Organization is checked. If this does not result in a unique selection, the Account is then checked. Finally, if necessary, the Program is checked. Once an FTMREBT row is chosen in this way, any remaining FOAP elements in that row that were not needed for selection are scanned to make sure that they do not conflict with the documents FOAP. For example, an invoice with a Fund of 1000 and an Organization of 120 cannot match an FTMREBT row where the Fund is 1000 but the Organization is 250. Nested ranges can be specified on FTMREBT. A nested range is one whose From and To values fall on or within those of another range. Examples of nested ranges are 1000-1500 and 1100-1300. Any number between 1000-1099 and 1301-1500 should match the 10001500 range, but any number from 1100-1300 would match the narrower 1100-1300 range. Overlapping ranges can also be specified on the form, but this is not recommended because it leads to ambiguities that are not necessarily resolved in the desired way. Examples of overlapping ranges are 1000-1500 and 1300-1700, where the numbers from
2-254
November 2010
1300-1500 could fall into either group. Any set of overlapping ranges can be specified for clarity. In the above example, you should decide which group the numbers between 13001500 belong to, and respecify the ranges as either 1000-1300 and 1301-1700 or as 10001500 and 1501-1700.
Example:
The Tax Rate TR1 has eight different rebate percentages. The default rebate percentage on FTMTRAT is 70%, and there are seven different rebate percentages on FTMREBT associated with the FOAP attributes.
Rebate Percentage
Fund From To From
Orgn To From
Acct To From
Prog To
57.14 52 50 45 42 60 65
1000 1000 1000 1000
1020 1020
111 6000 111 6100 6170 125 165
100
120
2222
100
120
The following table shows the percentages that are retrieved by the form based on the FOAPAL on the invoice:
FOAPAL on the Invoice or Direct Cash Receipt Fund Orgn Acct Prog
Rebate Percentage
1000 1000 1010 1010 2000 2010 2422
120 120 111 111 125 120 120
6000 6111 6120 6160 7120 6160 7220
100 100 115 145 100 125 150
50 57.14 52 45 60 42 70 (default)
Creating Tax Groups

Once you establish the tax rates, you can create the tax groups. The first tax group you should establish is for items that are not taxed.
November 2010
2-255
To create a tax group:

1. Establish a tax group, and check the Non-Taxable indicator on the Sales/Use Tax
Group Maintenance Form (FTMTGRP). You should reference this group on documents or items for which you do not have the system calculate taxes.
2. Uncheck the Non-Taxable indicator for all other tax groups. 3. Once you create the tax group, select Next Block to enter the rates appropriate for this
tax group.
4. Enter the Tax Group code, or click Code or select List to select a valid code from a
list window. Enter the tax rates associated with this tax group as established on the Tax Rate Code Maintenance Form (FTMTRAT).
5. Once you establish the tax groups, update the System Control Maintenance Form
(FOASYSC) with the default tax group.
Associating Tax Groups

You can associate tax groups with the Ship To Codes on the Ship To Address Maintenance Form (FTMSHIP) and/or with Commodity Codes. On a given document, the system retrieves the tax group from the Ship-To Code. If there is no tax group for the Ship-To Code, the system uses the Default Tax Group from FOASYSC. For a given commodity, the first source of a tax group is the commodity record (maintained on FTMCOMM). If there is no commodity tax group, the form uses the tax group from the header. You can override tax groups at the header and commodity levels.
Invoice Processing
Selecting the Invoice Type
When you create an invoice, you need to specify which type of invoice you wish to use. To do this, select Direct Pay, Regular, or General Encumbrance from the Invoice Type pulldown list (unlabeled).You must also specify if you want to use the vendor invoice consolidation functionality to enter more than one vendor invoice per Invoice Document by checking the Multiple check box.
2-256
November 2010
Direct Pay - Use a direct pay invoice when you do not reference a purchase order. Direct pay is the default invoice type. Regular - Use a regular invoice when you reference a purchase order created previously through the Purchase Order Form (FPAPURR). Vendor invoice consolidation may only be utilized if purchase order is defined as Regular type. General Encumbrance - Use a general encumbrance invoice when you reference a General Accounting Encumbrance created previously through the Encumbrance/ Reservations Maintenance Form (FGAENCB). Vendor invoice consolidation may not be used when processing General Encumbrance invoices.
Choosing Document or Commodity Level Accounting

You have two options when you enter accounting information for an invoice. If you issue an invoice created from a purchase order, you must use the accounting method used on the purchase order throughout the document. Document Level Accounting enables you to assign account distributions to an invoice document in total. To use Document Level Accounting, check the Document Level Accounting box in the Invoice/Credit Memo Header Window of the invoice form. Document Level Accounting has two significant advantages: Reduces the amount of time it takes to enter data. Reduces the number of records that the system stores in the invoice accounting and transaction history tables. Use Commodity Level Accounting to assign account distributions to individual commodities, if necessary. To use Commodity Level Accounting, uncheck the Document Level Accounting box.
Using the Invoice/Credit Memo Form (FAAINVE)

Purchase orders are not required to be closed out prior to invoicing. As a result, invoicing may be performed before receiving. The Invoice/Credit Memo Form (FAAINVE) provides the basis for all Accounts Payable processing activities. The form accommodates Direct Pay (an invoice that does not involve a purchase order), Regular (an invoice that involves a purchase order), and General Encumbrance (a general accounting encumbrance created through FGAENCG is referenced on the invoice). This form also accommodates additional charges or discounts, currency conversion, and taxes. Access this form from the *FININVS Menu.
November 2010
2-257
Key Information for the Invoice

To enter the Key Information:
1. Enter the invoice Document Number or enter NEXT to have the system generate
one. Click Document Number or select List to select an existing invoice document from the Invoice/Credit Memo List Form (FAIINVL).
2. Select Next Item to specify if vendor invoice consolidation will be utilized in
processing the invoice. Check the Multiple check box if you wish to use this functionality.
3. Select Next Item to specify the type of invoice you wish to create. 4. If a regular invoice is being created without using the vendor invoice consolidation
functionality, enter Y in the Select POs box to select items from the purchase order for invoicing. Selection of items to be paid on a regular invoice with vendor invoice consolidation will be done later in the invoice process.
5. Select Next Block to access the Invoice/Credit Memo Purchase Order Selection Form
(FAQINVP).
6. To pay the entire purchase order referenced without using the vendor invoice
consolidation functionality, enter Y in the Invoice All box. This creates the invoice from the entire purchase order, including the Commodity and Accounting records. If the transaction is a Credit Memo, and you do not want to Invoice All items, leave the Select POs and Invoice All fields blank in the Key Information. Instead, proceed with the remainder of the Key Information and Header windows. Purchase Order items may then be selected in the Commodity Information (Regular) Window by entering a Y in the Select PO field and selecting Next Item.
7. Enter the Vendor Number for Direct Pay invoice. Field defaults for Regular and
General Encumbrance invoices and may not be changed. To enter a one-time vendor, leave the Vendor number field blank, and enter the vendor's name.
8. Select Count Hits from the Vendor field to access the Vendor Maintenance Form
(FTMVEND).
9. Select Next Block to go to the Invoice/Credit Memo Header Window.
2-258
November 2010
Invoice/Credit Memo Header Window

1. The Invoice and Transaction Date fields default to the system date but may be
changed.
2. The Document Level Accounting box defaults to checked. You may alter this field if
the invoice is not based on a purchase order or a General Accounting Encumbrance. Check the Document Level Accounting box to assign the accounting distributions to the invoice document in total rather than to individual commodities. Uncheck this box to assign the account distributions to specific commodities.
3. The invoice Check Vendor defaults from the vendor entered in the Key Information.
You may also enter a Discount Code.

4. The system calculates the Payment Due date if Discount Code is entered. You can
use this date or enter a payment due date equal to or greater than the invoice date.
5. The Bank code is optional in this window; however, the Bank code is required in the
Accounting Distribution Window if left blank here. The 1099 Vendor box defaults from FTMVEND.
6. If applicable, you can enter the Vendor Invoice Number.
You can navigate to one of the following areas: To access the General Text Entry Form (FOATEXT), select the Document Text link. Use this form to enter text or change existing text for an invoice document. To go to the appropriate Commodity Information Window (either the Direct Pay/ General Encumbrance Commodity Information Window or the Regular Commodity Information Window), select Next Block.
Document Indicators Window

1. Check the Recurring Payables box if you wish this invoice to be paid to the vendor
on a regular recurring basis. To modify this information, refer to the Recurring Payables Form (FAARUIV). Refer to Setting Up a Recurring Payable on page 2-268.
2. Check the Installments box if the invoice will be paid on an installment basis. This
indicator is used by the Fixed Assets module to capitalize the purchase order amount when checked.The Installments indicator can be checked only if the Recurring payable indicator is also checked.
3. The NSF On/Off box defaults from the Non-Sufficient Funds Checking box on the
System Control Maintenance Form (FOASYSC). You may check this box if it is unchecked, but you may not uncheck it.
November 2010
2-259
4. Check the Deferred Edit box to activate the Deferred Editing feature. This speeds up
your system processing time. However, it also disables the system from displaying online errors immediately. If you use Deferred Editing, you cannot view your errors until you run the Editing feature in the batch processes FGRTRNI and FGRTRNR.
5. The Grouping pull-down list indicates whether you wish to group related invoices.
This indicator defaults from the Vendor Maintenance Form (FTMVEND). Select M to combine many invoices on one check. Select 1 to use one check per invoice.
6. Check the Hold box if you wish to save your changes to this invoice, but not pay it
immediately.
7. Select Next Block to access the Commodity Information Window (for the specified
invoice type). To access one of the other Header Information windows, select the corresponding menu option.
Commodity Information Window

If you selected Direct Pay or General Encumbrance in the Type of Invoice field, navigate to the Direct Pay/General Encumbrance Commodity Information Window. To use this window for a Direct Pay or General Encumbrance invoice:
1. Enter the Commodity code or the desired Description. A button and List are
available for both fields.

2. Enter the approved amount, discount, and tax if appropriate. The system calculates
discount and tax amounts if you enter the discount code and/or tax group.
3. Select Next Block to navigate to the Invoice Accounting Distribution Window.
If you selected Regular in the Type of Invoice field, navigate to the Regular Commodity Information Window. The commodity information defaults from the purchase order, but this information may be changed. The system increments the item number. To use this window for a Regular invoice:
1. Enter the commodity information or create a new commodity if necessary.
If you pay against a purchase order, the commodity items display.

2. Enter the approved unit price and quantity. 3. The Ordered Quantity amount defaults from the purchase order. The accepted
quantity displays if the receiving process receives the item. If the approved quantity equals the ordered quantity, the Final Payment Ind field defaults to F. Clear this field if you anticipate more invoices for the item. If this is the final payment, even though the approved quantity is less than the ordered quantity, enter F in this field.
2-260
November 2010
Both Commodity Information Windows include an Access Completion box that enables you to redistribute accounting amounts based on changes to commodity amounts. Therefore, you do not have to re-enter the Invoice Accounting Distribution Window. When you first enter the Commodity Information Window, you cannot access the Access Completion box until accounting records exist. When accounting records exist for the commodity, the box defaults to checked. If you make a change to the commodity amount and select Next Block while this box is checked, the form opens the Balancing Completion Window. The Wrap-up process recalculates the accounting amounts based on the new commodity amount, corrects any rounding problems, and calls the Available Balance Process. If you choose to access the Invoice Accounting Distribution Window instead of the Balancing Completion Window, uncheck the Access Completion box and select Next Block. You can navigate to one of the following areas: To access the Accounting Tax Distribution Window, select Next Set of Records. You can only access this window when you use the Tax Processing feature. To access the Commodities for Review Query Form (FOICOMM), click Commodity Query or select Block Menu. To access the Currency Conversion Window, select Count Hits from the Approved field. You can only access this window when you use a foreign currency.
Invoice Accounting Distribution Window

The commodity Item and Commodity description fields differ depending on whether Document Level Accounting or Commodity Level Accounting was selected. This difference exists because Document Level Accounting distribution(s) pertain to the entire invoice document, rather than to an individual commodity. If Document Level Accounting was selected, the commodity Item field appears blank or null, and the Commodity description field reads Document Acctg Distribution. For a Commodity Level invoice, the Item field is populated with an item number and the Commodity description field displays that item's description. If this is a regular invoice, the accounting information defaults from the purchase order. It can be corrected in this window. Enter accounting distributions that relate to either each commodity item or to the invoice in total. Select Next Item to go to the Approved Amount field, and enter the dollar amounts or use percentages to calculate the accounting amounts. If you pay against a purchase order, confirm each accounting sequence, and make any changes to the required amount. The following options are available when you enter accounting information:
November 2010
2-261
Check the Document Level Accounting box in the Invoice/Credit Memo Header Window and save the record without entering the amounts. When you execute the redistribution function from the Commodity Information Window, the system assigns the extended amounts equally among the account distributions you enter. If the Document Level Accounting box is unchecked, enter the accounting amounts. Manually enter the dollar amounts. Enter the percentages and allow the form to calculate the amounts.
If the Document Level Accounting check box is checked:
Select Next Block from the Commodity Information Window to execute the redistribution function. The system redistributes the total of all commodity items to the accounting records that use the percentages you previously entered for each account distribution.
If the Document Level Accounting box is unchecked:
The system redistributes specific commodity amounts among the assigned accounting sequences that use the percentages you previously entered for each account distribution. Use either all dollar amounts or all percentages on the account sequences. If you do not use a percentage to derive the amount originally, the system redistributes the commodity amount equally among its account distributions. You can navigate to one of the following areas from this window: To view additional account distributions, select Next Record. To access the Balancing Completion Window, click Completion or select Next Block. To access the Commodities and Accounting for Review Query Form (FOICACT), click Accounting Query or select the menu option. To access the Currency Conversion Window, select Count Hits. You can only access this window when you use a foreign currency. To access the Budget Availability Form (FGIBAVL), click Budget Availability or select Block Menu. This enables you to view the available budget for the account distribution which you enter.
Balancing the Invoice

The system executes Available Balance checking after you enter and save all the accounting records for a commodity or a document (depending on whether the Document Level Accounting box is checked or unchecked). The system sets the NSF Suspense indicator to A while you enter accounting records. To move from one accounting sequence to another, select Next Record.
2-262
November 2010
After you enter all commodities and accounting records, select Next Block to access the Balancing Completion Window. This form invokes the Wrap-Up routine, which allocates the accounting amounts (if these are blank), corrects any rounding problems, and calls the Available Balance Process. If you receive an insufficient funds message and have authorization to override the budget, enter Y in the NSF Override box and recommit the record. For Document Level Accounting Invoices, the system allocates the sum of all the commodities. For Commodity Level invoices, the system only allocates the amounts for each specific commodity. To process multiple commodity items and their associated accounting distributions:
1. Select Previous Block from the Invoice Accounting Distribution Window to return to
the Commodity Information Window.

2. Select Next Record on the Commodity Information Window to enter the next
commodity item. When the Document Level Accounting box is checked, Wrap-Up does not occur at this time. For a Commodity Level Accounting document, Wrap-Up occurs when you select Previous Block at this point. When you return to the Commodity Information Window, the Access Completion box is checked. This means that when you create commodity records, if you select Next Block, the system executes the Wrap-Up routine and opens the Balancing Completion Window.
3. If you need to enter additional accounting records or reallocate the amounts manually,
uncheck the Access Completion box and select Next Block to access the Invoice Accounting Distribution Window. Once you complete the accounting records, select Next Block to access the Balancing Completion Window.
Entering Taxes
This feature only displays for installations that use the tax process. If the tax process is in use, you may wish to see how the system distributes the paid taxes to the taxing authorities based on the invoice's tax group. Select the menu option from the Invoice Accounting Distribution Window to access the Accounting Tax Distribution Window. This window displays the tax distribution which you can change, as long as the total tax distribution does not exceed the tax amount on the accounting distribution. Select Next Block to access the Balancing Completion Window.
November 2010
2-263
Balancing Completion Window

Use the Balancing Completion Window to determine if the document is in balance before you try to complete the document. If the document is in balance and you are ready to mark the document complete, click or select Complete. The cursor returns to the Invoice Document Number field in the main window so that you may enter new invoices. To save the data and exit the document, click or select In Process and complete it at a later date. If you want the FAAINVE form to retain the document code in key-block, after clicking Complete or In Process, you will need to set up a new FTMSDAT record. The new FTMSDAT record is as follows: Entity = INVOICE Attribute = RETAIN_DOC_CODE Data = RETAIN This FTMSDAT record is optional, and is needed only if your site wants the document code to be retained in the Invoice key-block. If the optional FTMSDAT record does not exist, the document code will not be retained in the key-block, when you complete the Invoice or leave the Invoice in process.
Currency Codes and Conversion

Unless you specify otherwise, the amounts that you enter appear in the installation's base currency referenced on the Installation Control Form (GUAINST). When you deal with a foreign vendor, you can enter a currency code in the Currency Code field in the Additional Information Window, if the vendor's currency has not defaulted from the vendor record or if the purchase order currency does not match the requested reimbursement currency. Click Currency or select List to display the valid currency codes. For regular invoices, the currency code default value comes from the purchase order. This ensures that the currency for the payment matches the currency on the order. You can change the currency code in the invoice from the code used on the purchase order. If you change the currency code, you receive a warning message that the invoice currency does not match the purchase order currency.If you change the currency on the invoice so that it is not the same as the currency on the purchase order, you will need to calculate the conversion for input manually, since automatic currency conversion calculations do not occur in this uncommon situation. For example, if a purchase order is in US dollars and the vendor wants to be paid in euros, you must manually calculate the exchange rate from dollars to euros. There are many currency converters available on the Web to simplify this process, when needed.
2-264
November 2010
For direct pay and general encumbrance transactions, the currency default value comes from the vendor record. A warning message appears if a direct pay is processed and the default vendor currency is changed to another currency. At the commodity and accounting levels, the system calculates the converted amount (input amount divided by the exchange rate). From either the Approved field in the Commodity Information Window or from any field in the Invoice Accounting Distribution Window, select Count Hits to view the amounts converted to base currency in the Currency Information Window. Remember, the base currency amount is used for available balance checking, and this is the amount that posts to the ledgers.
Invoices for Purchase Orders

You can process invoices against a purchase order even when prior invoices for the same purchase order are in the posting queue. Invoicing is permitted until the purchase order is closed. If a prior invoice is determined to be a total liquidation, any subsequent invoices will roll back in posting. The invoice process is prohibited only when any of the following occur. The purchase order or encumbrance has not been posted or is closed. The purchase order has been cancelled. The document references a blanket order that is not complete or is terminated. A warning message displays after the purchase order is referenced in the Key Block when other invoices are in process, or when other invoices are in matching for the referenced purchase order. Previously invoiced columns are updated for invoices that are in approvals, matching, or both. When these prior invoices have been completed, the net quantity remaining to be invoiced becomes the default value in the invoiced and approved columns. The calculation used is as follows:
Order Quantity - Previously Invoiced Quantity = Net Quantity
If a purchase order has been fully invoiced, but not closed, the values in the previously invoiced columns default to zero.
Bank Code Edits

An accounting sequence must have a bank code or it cannot be saved to the database. If you try to save an accounting sequence without a bank code, you receive an error message stating that the bank code is required.
November 2010
2-265
If the bank code indicated is different than the default bank code for the currency established on the Currency Maintenance Form (GUACURR) and no disbursing agent is indicated, a warning message displays when the invoice is completed or put in process. You can either cancel the completion and return to the invoice to update the bank code(s), or complete the invoice. Mismatches between the bank code on the header record and accounting records are flagged as errors when you navigate to the Completion block (either from the Accounting block or from the Commodity block) when the Access Completion check box is checked. This helps you to avoid potential problems when posting check batches. If a bank code exists on the header, all accounting sequences must have the same bank code. If a bank code is not on the header, each accounting sequence can have a different bank code. If the bank code on the header has changed, bank codes on all the accounting records can be updated to the new code.
One-time Vendors
You have the option to create invoices and write checks to vendors without having to create a permanent vendor record on the Vendor Maintenance Form (FTMVEND). Ordinarily, you enter a vendor number in the Vendor field of the Key Information. However, to indicate a One-Time Vendor, follow these steps:
1. Enter the vendor name.
The absence of a value in the Vendor field cues the system to handle all the updates and restrictions appropriately.
2. Select Next Block.
The cursor bypasses the Address Code and Sequence Number fields, and goes directly to the Address Line 1 field.
3. Enter the street address (Address Lines 1/2/3/4, City, State or Province, and ZIP or
Postal Code). The form updates new columns on the Invoice Header Table (FABINVH).
Note If your site updates the ZIP/PC Code Validation Table (GTVZIPC), then you may leave the City and State or Province fields blank. Enter a valid ZIP or Postal Code and the form defaults the City and State or Province.
2-266
November 2010
Follow the instructions for the remainder of the direct pay invoice process. The following restrictions apply: If your site uses Tax Processing, a One-Time Vendor can collect all taxes or no taxes, but cannot collect selected taxes. The only place to define which taxes you wish to collect is in the Vendor Table, which necessitates a permanent vendor record. Pay a One-Time Vendor in base, not foreign, currency. A One-Time Vendor cannot be a 1099 vendor.
Viewing Vendor Invoice Detail Information

1. Access the Vendor Invoice Query Form (FAIVINV). 2. Enter a vendor ID code in the Vendor field. A list is available if the vendor ID code is
not known.
3. Perform a Next Block function to navigate to the Document Information block. The
block is placed in query mode upon entry.

4. Enter any known document information. All fields accept query criteria including
wildcards (% and *), the greater than sign(>), and the less than sign (<). All fields may be left blank to query all vendor invoices for the specified vendor ID code.
5. Perform an Execute Query function. Invoice document detail information will be
returned based on query criteria. If multiple records are returned, use the Next Record function to scroll through records. The Commodity Detail block will update with appropriate information as you access each record.
6. Perform a Next Block function to access the Commodity Detail block. 7. Click Vendor Invoice Commodity Detail in the navigation frame to view additional
information regarding a commodity on the Vendor Invoice Commodity Detail window.

8. To perform another query, navigate to the Document Information block, perform an
Enter Query function, and enter the new search criteria.
Viewing Vendor Invoice Information

1. Access the Multiple Vendor Invoice Query Form (FAQMINV). 2. (Optional) Perform a Next Record function when multiple vendor invoices exist to
select the desired record.

3. Perform a Next Block function to access the commodity records.
November 2010
2-267
4. Click Commodity Detail in the navigation frame to view additional information about
the commodity on the Multiple Vendor Invoice Commodity Detail window.
Recurring Payables
Create a recurring payable in Banner Finance to pay the same amount to the same vendor at regular intervals. For instance, rent or an annuity are types of recurring payables.
Setting Up a Recurring Payable

1. Create the recurring invoice with the Invoice/Credit Memo Form (FAAINVE). 2. Create a header record as you would for any other invoice. 3. Check the Recurring box in the Document Indicators Window. 4. Enter the commodity and accounting data and complete the invoice.
The recurring payable posts as a normal invoice in the next posting run. If you use approvals, it proceeds through the approvals process as any other invoice.
5. Specify the submission parameters.
Access the Recurring Payables Form (FAARUIV) to enter the submission criteria which determine when you create and post checks for the recurring payable. Once you complete the invoice, a record exists on the Recurring Payables Form with the invoice Document Number, Vendor code and name, and the Next Submission Date. This record displays the Payment Due date as entered on the invoice.
6. Enter the submission parameters:
Submission Days allows you to enter a number to represent the number of days between submissions. For example, if you need to generate your recurring payable every ten days, you would enter 10 in this field. Alternatively, you can select Monthly, Quarterly, Yearly, Semi-Annually, Bi-Weekly, or Weekly from the Submission Indicator pull-down list. For example, you usually pay rent monthly, so you would select Monthly in this field. You may enter either Submission Days or the Submission Indicator, but not both.
7. Enter the maximum number of submissions in the Maximum Submissions field.
For example, the maximum number of submissions for rent is likely to be 12, because you pay rent once a month (12 times a year).
2-268
November 2010
Subsequent Processing
When you run the Check Selection Process (FABCHKS), the system adheres to the parameters established on the Recurring Payables Form (FAARUIV) as you select invoices for payment. When you cut a check for your recurring payable, the check process produces the check. Then, submit the next invoice for posting. In addition, the check process updates the Submissions to Date field on the Recurring Payables Form (FAARUIV). If the Submissions to Date equal the Maximum Submissions, the system marks the invoice as P (Paid), so that the online check processing feature no longer selects the invoice for checks.
Cancelling a Recurring Payable

If you create a recurring payable but do not process any checks, you should cancel the invoice with the Invoice/Credit Memo Cancel Form (FAAINVD) as you would any other invoice. This cancellation transaction does not update the Recurring Payables Form (FAARUIV). Therefore, you should update the Maximum Submissions number on that form to reflect that there should be no more submissions. To cancel a check associated with a recurring payable, use the Check Cancellation Form (FAACHKS). When you cancel the check, the form does not permit you to select the Reestablish Payable? option. To ensure that all the accounting transactions related to this process are correct, you must cancel the recurring invoice as well as the check.
Creating a Zero Amount Payable

For a Direct Pay Invoice, you may enter a commodity with a negative amount. However, the total amount of the payable must be zero or greater than zero. If you have one commodity with a negative amount in the Net Amount field, then you should have another commodity with a positive value in the Net Amount field which will make the total amount of the payable zero or greater than zero.
Stores Inventory
The procurement process within Banner Finance provides the Requisition Form (FPAREQN) for you to order commodity items. Alternatively, the Stores Requisition Form (FSAREQN) allows you to enter stock type commodities only in order to make direct requests for stores items. Both of these forms share the same database tables. When you create a requisition document on the procurement Requisition Form (FPAREQN), an indicator is set that defines this document as a procurement requisition.
November 2010
2-269
This document is then processed through the normal functions of bids, buyer assignment, and purchase order assignments. When you generate a request for stores items from the Stores Requisition Form (FSAREQN), the document is defined as a stores request. This prevents the system from using the stores request in both the bids process and the buyer assignment process.
Issues
The Stores Issue/Return Form (FSAISSU) enables you to issue stock items from the stockroom or inventory warehouse. You may issue two kinds of issues: an issue against a stores request or a direct issue without a user-requested stores requisition. After the goods are issued, the departmental budget reflects this issue by means of a debit to the expense account entered in the issue. The stockroom reduces the onhand quantity by location with the issued quantity of the item, and the inventory account is credited appropriately.
Returns
Frequently, you need to return goods to a stockroom either because you order the wrong item, order too many items, or an item is defective. You want the departmental budget to reflect this return by means of a credit to the expense account charged in the original issue. Additionally, the stockroom needs to update the onhand quantity with the returned quantity of the item and to have the inventory account debited appropriately. The Stores Inventory Issue/Return feature enables both of these processes to occur.
Entering Cost Adjustments to Physical Inventory

Before you can adjust quantities or unit costs in the Stores Inventory system, you must restrict the system so that it does not post issue, transfer, invoice, and receipt documents for the stores item until you complete and post the adjustment. To restrict the system in this way, you will need to perform the following steps.
1. Access the Inventory Adjustment System Control Form (FSASYSA). 2. Enter or select a Primary Location or a Commodity Code, or both, in the Key
Information.
3. Select Next Block to go to the Inventory Adjustment Action Information. 4. Select Cost for cost adjustments in progress, Quantity for inventory quantity
adjustments in progress, or End to end adjustments in progress.

5. Select Next Block to view the adjustment history for the commodity.
2-270
November 2010
At this point, all stores inventory items selected in the Key Information are restricted from creating issue, transfer, invoice, and receipt documents.
Determining Inventory Adjustment Status

The system date defaults into the Adjustment Start Date field to indicate when to process adjustments. Also, the system sets the Status indicator on the Stores Commodity Location List Form (FSISTKL) to a status of I for Inventory Quantity Adjustments In Progress or T for Cost Adjustments in Progress. Before you can create any stores documents, the system checks this indicator. You can create documents only when the Status indicator is null. After you complete and post all adjustments to quantity and/or cost, the stores item accepts issues, transfers, invoices and receipts. When you create these documents, the system resets the Status indicator on FSISTKL to null. To complete this function, choose End (for End adjustments in progress) in the Inventory Adjustment Action Information on FSASYSA. The system date defaults into the Adjustment End Date field to indicate when adjustments for the inventory selected can no longer occur.
Adjustment Requirements
The system can only process adjustments when all stores items for selected inventory have a null status. This means that all prior adjustments have been completed, posted, and returned to a null adjustment status. Likewise, before a stores items or location can end adjustments, all stores items must have been R (Reconciled) or must still have an I (Inventory Quantity Adjustments in Progress) status or Cost(T) Adjustments in Progress status. An item can have a status of R (Reconciled) if a quantity adjustment has occurred, and the document for the adjustment has been completed and posted from the Adjustment to Quantity/Inventory Reconciliation Form (FSAADJQ). You can also adjust an item to I (In progress) status if it has never been counted, or a Cost (T) adjustment has been created and posted. Refer to the adjustment status listed on the Physical Inventory Discrepancy Report (FSRPIDR) in the Reports and Processes chapter. You can only start an adjustment period again when the prior adjustment system control record (FSASYSA) has an adjustment end date. Multiple adjustment periods display with the most recent period first. Once you choose Quantity or Cost from the Adjustment Action radio group to insert records; you may not delete them. For physical inventory adjustment for all stock items, use the Physical Inventory All indicator on the Inventory System Control Maintenance Form (FSASYSC) to set the status to I (Inventory Quantity Adjustments in Progress) on all stock items.
Note You can only start adjustments to a stores item for a primary location, for a commodity code, or for a specific commodity code at a primary location. However, if you select the latter and you wish to view just the adjustment
November 2010
2-271
periods for that primary location, the periods that the system displays only represent prior entries to this form by primary location.
Processing Status Changes During Cost Adjustment

Processing Status
Access the Inventory Adjustment System Control Form (FSASYSA) and choose Cost from the Adjustment Action radio group.
Status updated to T
Use the Cost Adjustment Form (FSAADJC) to adjust the unit cost for the item.
Status updated to C
the system cannot process issues, transfers, or receipts
Run the Posting Process to create adjusting entries and update the total value of the item.
Status updated to T
Access the Inventory Adjustment System Control Form (FSASYA) and choose End from the Adjustment Action radio group. This indicates that the adjustment is complete.
Status changes to null. The system can now process issues, transfers, and receipts.
2-272
November 2010
Processing Status Changes During Physical Inventory Adjustment
Access the Inventory Adjustment System Control Form (FSASYSA) and choose Quantity fro the m Adjustment Actio radio group. n
Processing Status
Count quantities for specified commodities/locations.
Status updated to I
Enter counts on the Stores Physical Inventory Count Recording Form (FSAPHYC).
Status updated to Q
Run the Physical Reconciliation Process (FSRPHYR).
the system cannot process issues, transfers, or receipts
Is the entered amount equal to or within tolerance?
Yes
Status updated to R (Reconciled)
Use the Adjustment to Quantity and Inventory Reconciliation Form (FSAADJQ) to enter adjusted quantities.
No
Status updated to A
Run the Posting Process to process adjustments .
Status updated to R
Access the Inventory Adjustment System Control Form (FSASYSA) and choose End from the Adjustment Action radio group. This indicates that the Inventory is complete.
Using Stores Issues and Returns

The Stores Issue/Return Form (FSAISSU) functions in the same manner as the Credit Memo in the Accounts Payable module. The Return check box on this form functions in the same way as the Credit Memo indicator on the header of the Invoice/Credit Memo Form (FAAINVE). Select the Return check box on the Stores Issue/Return Form to flag the current document as a return. The check box defaults to unchecked. You may return goods against a requisition or return them directly without reference to a requisition.
November 2010
2-273
If you reference a requisition, the Key Information provides an edit to ensure that the requisition is open. If the requisition is closed, you receive a message stating that the requisition is closed and that you may not proceed. This applies to both issues and returns. If the requisition is open, you may select all items or selected items from FPIRQST. All open items display here, and you can select Exit with Value to select the appropriate items to return. Those items already closed through full issue activity do not display in this form. A Direct Return is a return in which no requisition is referenced. Use a Direct Return if the original requisition is not known or if that requisition or the relevant item on that requisition is closed. Indicate which commodity to return in the Issue/Return Commodity Information on the Stores Issue/Return Form.
Entering ABC Classification Tolerances

ABC classification is an industry-defined classification associated with inventory. Use ABC classifications to classify items within inventory valuation. For example, an A classification not only represents 20% of the inventory items within a site, but also represents 80% of the entire value of the inventory within this same site. These representations are strictly user-defined. Typically, the top 20% of inventory items comprise approximately 80% of the inventory investment. When you classify items based on their relative value, you can support various kinds of inventory analysis. If you use this optional classification system, the system reflects it in the Physical Inventory report sort features. You can also assign a percentage of tolerance for physical inventory processing to the ABC classification code on the System Data Maintenance Form (FTMSDAT). Use A, B, or C for each field to get the corresponding FTMSDAT entry. Enter the tolerance percentage in the Data field of FTMSDAT. Use this tolerance percentage when you run physical inventory to determine if you wish to have the system automatically reconcile these percentage amounts when you run the batch physical inventory process. The system then reconciles any items that are counted and found to be within this tolerance percent of the system count.
Using the Valuation Process

The current philosophy of valuations is that the current unit price is always a running weighted average of the cost of goods received to-date. If you know the invoice price at the time you receive the goods, the system uses this price to calculate the new net unit price. If the invoice price is not available, the system uses the
2-274
November 2010
purchase order net unit price to determine the new unit price of inventory, and makes an adjustment when the invoice is processed, if necessary. Issued goods always use the current unit price, regardless of whether the goods are invoiced yet. Any unit price adjustments which take place after you issue goods only affect the unit price of future issues. They do not affect any issues which have already taken place.
Posting Processes for Stores Inventory

Purchasing Inventory from Outside Vendors
Example 1:
The Stockroom or Purchasing Department requisitions the purchase of stockroom inventory. Use the procurement Requisition Form (FPAREQN) to create a requisition document. Based on the fact that the commodity selected is identified as a Stock item on the Commodity Validation Form (FTVCOMM), the Inventory Fund and Acct default in the following order: FTVINVM, FTVSHIP, FSBSYSC. If you use Document Level Accounting, the first commodity is searched for a fund and account. Since these are G/ L accounts, the system treats the requisition as an inventory or G/L requisition, and no accounting entries take place. If you decide to override the account with an expense account, the requisition produces the normal accounting entries (Rule code = REQP). This requisition eventually becomes a purchase order with the same type of accounts as on the requisition. If G/L accounts are referenced on the purchase order, there are not accounting entries.
Example 2:
The Purchasing Department chooses to enter purchase orders without requisitions. The Purchase Order Form (FPAPURR) recognizes that the item is a stock item based on the Stock indicator on FTVCOMM. The accounting defaults the Inventory Fund and Account from FTVINVM, then FTVSHIP, then FSBSYSC. If document level accounting is in effect, then the first commodity is searched for a fund and account. As was true with the requisition, G/L accounts on the purchase order result in no postings to the ledgers.
November 2010
2-275
Purchasing Inventory Within a Department

Follow these steps:
1. Use the Stock Requisition Form (FSAREQN) to reserve stock quantities and the
associated amounts.
2. Enter the expense FOAPAL to charge against your budget.
The accounting on this form does not default from any Stores related tables.
Example:
When this document posts a Stores request for $300.00, it results in the following General Ledger postings: DR: $300.00 Budgeted Reservations Control CR: $300.00 Offset to Budgeted Reservations Control A sum of $300.00 posts to the encumbrance ledger with that expense account, and a $300.00 budget reservation posts to the operating ledger. A rule class code REQS for the Stores Requisition contains the same process codes as REQP. The two rule classes provide additional flexibility (for example, you could choose to debit Encumbrance Control with Procurement Requisitions and Budgeted Reservations Control with Stock Requisitions) which allows analysis on posted entries.
Issuing Stock Against a Requisition

When the stockroom issues the stock, access the Stores Issue/Return Form (FSAISSU). The expense FOAPAL defaults into this form from the Stores Requisition Form (FSAREQN). The system posts the following General Ledger entries: Operating Fund: DR: Expenditure Control (for requisitioner org) CR: Interfund Due/To Acct. DR: Offset to Budgeted Reservations Control CR: Budgeted Reservations Control In addition, the system updates the OPAL and Encumbrance ledgers as follows: Inventory Fund: DR: Interfund Due/From Acct (extended quantity X unit cost) CR: Inventory Account
2-276
November 2010
If you apply an external rate and the warehouse is a profit center, the General Ledger entry is: Operating Fund: DR: Expenditure Control (quantity X unit cost) DR: Expenditure Control (quantity X external rate) CR: Interfund Due/To Acct.(same as Debit amount) DR: Offset to Budgeted Reservations Control (Requisition amount) CR: Budgeted Reservations Control (Requisition amount) In addition, the OPAL and Encumbrance ledgers are updated: Inventory Fund: DR: Interfund Due/From Acct (quantity X unit cost) DR: Interfund Due/From Acct (quantity X external rate) CR: Inventory Account (quantity X unit cost) CR: Revenue Control based on Stockroom Income (quantity X external rate)
Note You cannot use an external rate if the location is not defined as a profit center.
Issuing Stock Directly With No Requisition

When the stockroom issues the stock, follow these steps:
1. Access the Stores Issue/Return Form (FSAISSU). 2. Input the FOAPAL values.
The system posts the following General Ledger entries: Operating Fund: DR: Expenditure Control (for requisitioner org) CR: Interfund Due/To Acct. In addition, the OPAL ledger is updated: Inventory Fund: DR: Interfund Due/From Acct (extended quantity X unit cost) CR: Inventory Account
November 2010
2-277
If an external rate has been applied and the warehouse is a profit center, the General Ledger entry is: Operating Fund: DR: Expenditure Control (quantity X unit cost) DR: Expenditure Control (quantity X external rate) CR: Interfund Due/To Acct.(same as Debit amount) In addition the OPAL ledger is updated: Inventory Fund: DR: Interfund Due/From Acct (quantity X unit cost) DR: Interfund Due/From Acct (quantity X external rate) CR: Inventory Account (quantity X unit cost) CR: Revenue Control based on Stockroom Income (quantity X external rate) The rule class for this activity must contain an Operating Ledger (OPAL) routine to record the expense (routine process code O030), but no liquidation process code. In addition, a process code exists in the G (General ledger) series to select the appropriate Inventory Fund and Account based on the established values on FTVINVM, FTVSHIP, and FSBSYSC. The routine to recognize revenue might be a user-defined modification to the existing O030 process code since this is an OPAL rather than G/L activity.
Returning Stock Against an Open Requisition

Perform the steps in the following list.
1. Use the Stores Issue/Return Form (FSAISSU) to return stock. 2. Select the Return check box.
The expense FOAPAL defaults into this form from the Stores Requisition Form (FSAREQN). The system posts the following General Ledger entries: Operating Fund: DR: Interfund Due/To Acct. CR: Expenditure Control (for requisitioner org) DR: Budgeted Reservations Control CR: Offset to Budgeted Reservations Control The system also updates the OPAL and Encumbrance ledgers as follows:
2-278
November 2010
Inventory Fund: DR: Inventory Account CR: Interfund Due/From Acct (extended quantity x unit cost) If you apply an external rate, and the warehouse is a profit center, the General Ledger entry is: Operating Fund: DR: Interfund Due/To Acct.(same as Debit amount) CR: Expenditure Control (quantity x unit cost) CR: Expenditure Control (quantity x external rate) DR: Budgeted Reservations Control (Requisition amount) CR: Offset to Budgeted Reservations Control (Requisition amount) The system also updates the OPAL and Encumbrance ledgers as follows: Inventory Fund: DR: Inventory Account (quantity x unit cost) DR: Revenue Control based on Stockroom Income (quantity x external rate) CR: Interfund Due/From Acct (quantity x unit cost) CR: Interfund Due/From Acct (quantity x external rate)
Note The Request Return Rule Class ISEC supports this activity and is the opposite of the rule class you use when you issue against a requisition.
Returning Stock Directly With No Requisition

Perform the steps in the following list.
1. Access the Stores Issue/Return Form (FSAISSU) to return stock. 2. Check the Return box. 3. On a direct return, enter the expense FOAPAL.
The system posts the following General Ledger entries: Operating Fund: DR: Interfund Due/To Acct. CR: Expenditure Control (for requisitioner org)
November 2010
2-279
The system also updates the OPAL ledger as follows: Inventory Fund DR: Inventory Account CR: Interfund Due/From Acct (extended quantity X unit cost) If you apply an external rate, and the warehouse is a profit center, the General Ledger entry is: Operating Fund: DR: Interfund Due/To Acct.(same as Debit amount) CR: Expenditure Control (quantity X unit cost) CR: Expenditure Control (quantity X external rate) The system also updates the OPAL ledger as follows: Inventory Fund: DR: Inventory Account (quantity X unit cost) DR: Revenue Control based on Stockroom Income (quantity X external rate) CR: Interfund Due/From Acct (quantity X unit cost) CR: Interfund Due/From Acct (quantity X external rate)
Note The rule class for this activity is the opposite of the rule class for a direct issue.
Transferring Stock Locations

When you move stock from one location to another, you may not know if an accounting entry should occur. An accounting entry should contain a debit to the location that receives the stock and a credit to the location that loses the stock with an offset to the interfund accounts in each fund. To transfer the location of stock, your account records must meet one of the following conditions: Inventory Fund and Inventory Account are specified on FTVINVM. No accounting entry is required. Inventory Fund and Inventory Account are null on FTVINVM. Look at the two location codes on FTVSHIP: If the Primary locations are the same, no accounting entry is required. If the Primary locations are different and if the Inventory Fund and Inventory Account for both locations are null, no accounting entry is required.
2-280
November 2010
If the Primary locations are different, and if the Inventory Fund and Inventory Account for each location is populated, the accounting entry is: DR: Inventory Fund and Account for Location receiving Stock CR: Inventory Fund Inventory Transfers In Account DR: Inventory Fund Inventory Transfers Out Account CR: Inventory Fund and Account for Location losing Stock If the Primary locations are different, and if the Inventory Fund and Inventory Account for one location is populated and the other is null, the accounting entry uses the Inventory Fund and Account from FSBSYSC for the location that has null in these fields. For example, if the receiving location Inventory Fund and Account is null, and the losing location is populated, the accounting entry is: DR: Inventory Fund and Account from FSBSYSC CR: Inventory Fund Inventory Transfers In from FSBSYSC DR: Inventory Fund Inventory Transfers Out CR: Inventory Fund and Account from FTVSHIP
Note You must expand these conditions to take into account the options of having either the Inventory Fund or the Inventory Account, but not both, populated in each case.
Receiving Inventory at the Dock

When the dock receives goods, the system completes a receiving document. The Inventory Fund and Account are known by the system because you specify them on the purchase order. The Ship Code defaults from the purchase order into the receiving document, but you can override it. The Inventory Fund and Account appear in the accounting entry, based on the Receiving location. The accounting entry is: DR: Inventory Fund and Account (Purchase Order Extended Amount) CR: Valuation Clearing (from FSBSYSC) (Purchase Order Extended Amount)
Paying for Inventory in Accounts Payable

When you invoice goods in Accounts Payable, follow these steps:
1. Calculate any difference between the net purchase order amount and the net invoiced
amount. The accounting entry is: DR: Valuation Clearing Account for the net invoice amount CR: Accounts Payable for the net invoice amount
November 2010
2-281
2. Debit or Credit the Inventory Fund and Account for the difference between the net
purchase order price and the net invoice amount.
Making Adjustments to Cost

When you make adjustments to the unit cost of an item, the adjustment process determines every location for the item, and at each location, calculates the change in value at that location.
Example:
An item has a unit cost of $2.00. Location A has a quantity of 10. Location B has a quantity of 5. The cost is adjusted to $1.90. This effect on the value of the inventory is: Location A changes from $20.00 to $19.00. Location B changes from $10.00 to $9.50. The resulting entry is:
Location A
Inventory Fund
DR: Valuation Clearing CR: Inventory Account
$1.00 $1.00
Location B
Inventory Fund
DR: Valuation Clearing CR: Inventory Account
$.50 $.50
If the resulting value increases rather than decreases, then the entry is a debit to the inventory account and a credit to the valuation clearing account.
Budget Development
Some Budget Development tasks can be performed with Banner Finance Self-Service. For details, refer to the Banner Finance Self-Service User Guide.
2-282
November 2010
Maintaining a Budget
Once you approve an operating budget and roll it into Banner Finance, use the following two methods to maintain the budget:
1. Through the entry of journal voucher transactions, either through the Journal Voucher
Form (FGAJVCD) or the Journal Voucher Quick Form (FGAJVCQ), directly into Banner Finance to increase/decrease or otherwise adjust the budget dollars. In this case, only the financial ledgers reflect the budget changes. The budget files remain intact with the approved data.
2. Through the use of the Budget Maintenance Form (FBABDMN) which updates the
budget files and provides these changes to the financial ledgers using a journal voucher transaction.
Budget Maintenance Form (FBABDMN)

This form enables you to update the budget amounts for the current fiscal year in the Budget Line Item Table (FBBBLIN) and the Distributed Budget Table (FBRDIST) while at the same time maintaining the budget amounts in the operating ledger for budgets that are already in effect. The Budget Maintenance Form enables you to create and edit standard journal voucher transactions with budget rule classes. FBABDMN displays the budget amounts currently in the Distributed Budget Table (FBRDIST) and in the Operating Ledger Account Table (FGBOPAL). The system creates journal voucher transactions for all budget changes and writes those changes to the Journal Voucher Transaction Table (FGBJVCD). When you complete a document, the system applies the journal voucher budget transaction amounts to both budget tables (FBBBLIN and FBRDIST). The journal voucher document is then ready for the approval process and posting to the financial ledgers. Edit and process the journal vouchers the same way you enter the vouchers on the Journal Voucher Form (FGAJVCD). Since a separate form is used to maintain the budget, the Security Administrator can employ additional security for FBABDMN to limit which users can change the actual budget tables. For additional information, refer to Security on page 2-1 and related procedures in this chapter.
Note Use of FBABDMN is entirely optional. FBABDMN enables you to maintain the budget during the fiscal year using the Budget Development Module and not just through Banner. Once you roll a budget and phase to Banner Finance and close the phase, begin the maintenance stage for the budget using the Budget Maintenance Form.
November 2010
2-283
Key and Header Information

1. Enter a document number in the Document field or enter NEXT to have the system
assign a document number. Select Next Field. The system checks the document number to verify that it was created on the Budget Maintenance Form. FBABDMN does not allow you to view or update documents created on the Journal Voucher Entry Form (FGAJVCD) and the Journal Voucher Quick Form (FGAJVCQ).
2. Populate the Description (Unlabeled) field. The system uses the description for each
of the journal voucher detail records created. All of the detail records are updated when this field is changed.
3. Enter the Document Total. The system uses the document total at completion time to
ensure that the document is in balance. The document total is a hash total of all the amounts and does not consider the sign.
4. Enter the Transaction Date. The system uses the transaction date for each journal
voucher detail created. When the date changes, the system re-checks the available balance for all detail records based on the new transaction date.
5. Populate the Budget ID, Budget Phase, and Duration Code fields. Once these fields
are entered, you may not modify them for this document. Enter a closed phase for the budget. The budget must have already been rolled to the operating ledger.
6. The Document Text Exists field contains Y if the document has associated text. To
view or add text, click Document Text or select the menu option. The system writes a journal voucher transaction header record. If you delete the record, the system deletes the header and all of the document details.
Transaction Detail Information

1. Enter the Journal Type. The journal type you enter must support the Duration Code
selected in the header.

2. The Reference number field is optional. 3. The COA (Chart of Accounts), Index, Fund, Organization, Account, Program,
Activity, and Location values are entered and edited here. You cannot proceed to the next window unless these values are validated by the system. All of the journal voucher transactions created for this document use these same FOAPAL values. You may change any of these values at any time and all of the detail transactions will be updated when you select Next Block. One document will contain only the changes for all budget periods for a single line item. Multiple budget line items will not be contained in a single document.
2-284
November 2010
Budget Maintenance Window

These fields are display only and show the Adjusted Budget, Year to Date expenditures, Commitments, and the Available Budget for this line item in the Operating Ledger Account Table (FGBOPAL) for the current fiscal year. Values in the Budget, Adjustments, and the Total Budget fields are displayed from the Distributed Budget Table (FBRDIST). The Period (Budget Period), Transaction Amount, +/- indicator (Debit/Credit Indicator), Override (Available Balance Override), and the Status (Transaction Status) indicators are displayed from the Journal Voucher Transaction Table (FGBJVCD). You may update the Transaction Amount, +/- Indicator, and the Override fields. One line displays in these fields for each Period that currently exists in the Distributed Budget Table for this line item. You may then enter transaction amounts to increase or decrease the budget for any or all of these periods. You may enter new periods and amounts for any valid periods (13 or 14, depending on whether the fiscal year is divided into months or into four week periods) in the current fiscal year. You may add new budget periods but you may not change an existing period to another. You must adjust the existing period so the net of the change is zero and add a new period. For each period record entered or adjusted, an available balance edit will be performed. You can override a non-sufficient fund edit by entering Y in the Override (Available Balance Override) field. The Status (Transaction Status) field displays a P for Postable or an N for Non-Sufficient fund error. If you select Remove Record on a transaction record, the system does not delete the record. Instead, the system zeroes out the transaction amount. When you complete the document, the system automatically deletes journal voucher details with transaction amount of zero. Click Completion or select Next Block to access the Balancing/Completion Window.
You may complete a document if all the transactions have a P (Postable) status and the total of the transaction amounts, regardless of sign, match the Document Total in the main window. When you complete a document, the system applies the journal voucher transaction amounts to the Budget Line Item and Distributed Budget Tables. Click or select Complete to have the system edit the document and submit it to posting. Click or select In Process to have the system save the work done on this form but not submit the document to posting. Selecting the In Process function allows you to research the document for any open issues before sending it to posting.
November 2010
2-285
Navigation
When you open FBABDMN, you are positioned in the Document Number field. Enter a document number or type NEXT, and select Next Field to enter the Document Header fields. From the Document Header, Next Block takes you to the Transaction Detail Information fields. From the Transaction Detail Information, select Next Block to access the Budget Maintenance Window to enter journal voucher details or Previous Block to return to the Document Header. Click Completion or select Next Block from the Budget Maintenance Window to access the Balancing/Completion Window. Approve documents from the User Approval Form (FOAUAPP), and the Document Approval Form (FOAAINP). Click Rollback or select Clear Form in FBABDMN to return to the Key Information fields. The system uses an edit with the Journal Voucher forms that prohibits you from accessing a document created from the Budget Maintenance form. Journal vouchers you create through the Budget Maintenance form carry the budget ID for which the change is applicable. If you try to access a document through the journal voucher forms that contains the budget ID, the system denies access to the document through FBABDMN and following error message is displayed: Document was created on Budget Maintenance (FBABDMN). Cannot update here. FBABDMN accumulates saved and unsaved budgets. The FTVOBPH_ACCUM_PY_BUDG_IND is accessible on the Operating Budget Phase Table (FTVOBPH). Valid entries are as follows: Y (Yes), accumulate both committed and uncommitted budgets N (No), accumulate only uncommitted budgets blank, do not accumulate budgets
Additional Information
The FBABDMN form does not support deferred edit based upon the unique updating requirements of the budget and finance tables. The system automatically edits the distribution components in the Transaction Detail fields so that you may update the records to Budget Line Item Table (FBBBLIN) and the Distributed Budget Table (FBRDIST) before navigating to the Journal Voucher Detail information fields. FBABDMN performs available balance and transaction edit processing. The edits use work pages 90 through 92. The available balance process uses work page 99. If you use the print feature to obtain a hard copy of this form, the system asks if you want to print all pages of the form. Be particularly careful in answering this
2-286
November 2010
question. If you enter Y (Yes), the system prints all 99 pages of the form, most of them blank.
Budget Development Cycle

This section describes the sequence of events to enter and maintain a budget in the Budget Development module. An example depicting the sequence of these events is displayed in the Budget Development and Maintenance Time Line.
1. Establish budget IDs and phases for the new budget year on the Operating Budget
Maintenance Form (FTMOBUD). Create new phases as necessary throughout the budget process.
2. Create an approved phase and enter an activation date.
The activation date enables the system to calculate what the budget year is for that budget ID. You may create a base for your new budget phases by rolling budget information from the Operating Ledger (OPAL) or from any other existing budget phase.
3. To roll into a budget you must enter parameters on the Budget Process Control
Parameters Form (FBABPRC).

4. Execute the Budget Build Process (FBRBDBB) to build or change line items for a
budget phase.
5. Generate the Budget Worksheet Report (FBRWKSH).
FBRWKSH displays up to three phases of budget information as well as current and prior fiscal year budgets.
6. Enter and update the budget using the Budget Request Form (FBABDRQ). 7. Review budget items online using the Budget Query Form (FBIBUDG).
You may perform mass change operations over all or part of a budget phase. You may change budget amounts by a percentage or a fixed amount. Populate these parameters using the Mass Budget Change Form (FBAMCHG).
8. Execute the Mass Change Process (FBRMCHG) to update the budget line items.
You may delete specific account and fund types from a budget phase.
9. Set up parameters using the Budget Process Control Parameters Form (FBABPRC).
List all the account and fund types you want the system to delete.
November 2010
2-287
10. Execute the Budget Parameter Update Process (FBRBDBB).
FBRBDBB deletes the selected account and fund types from both the Budget Line Item Table (FBBBLIN) and the Distributed Budget Table (FBRDIST).
11. Repeat steps 1 through 10 as necessary, updating and adjusting the budget until you
have one phase that is your approved budget.

12. Verify that the activation date and finance rule class is in your approved budget phase. 13. Generate the Approved Budget Report (FBRAPPR). 14. Distribute approved budget phase amounts over selected periods. 15. Create parameter cards to distribute the budget using the Budget Distribution
Parameter Form (FBABDDS).

16. Execute the Budget Distribution Process (FBRBDDS) to distribute amounts in the
Line Item Table (FBBBLIN) and into the Distributed Budget Table (FBRDIST). You need to execute the Budget Distribution Process (FBRBDDS) since the system rolls the budget into OPAL from the Distributed Budget Table.
17. Generate the Approved Distributed Budget Report (FBRAPPD).
FRAPPD displays your distributed budget amounts and compares them to current and prior fiscal year amounts.
18. Adjust the distributed amounts in the Period fields on the Budget Distribution by
Amount Form (FBABDDA). FBABDDA updates both the distributed amounts (in the Distributed Budget Table, FBRDIST), and the annualized amount (in the Budget Line Item Table, FBBBLIN). This ensures that the amounts in both these files match.
19. Repeat steps 15 through 18 until the distributed budget is correct and ready to be
rolled into the General Ledger System.

20. When you are ready to roll your budget into the Operating Ledger, create a parameter
card using the Budget Process Control Parameters Form (FBABPRC) to activate the approved budget.
21. On the Phase Activation Data Window, populate the Permanent Rule Code,
Temporary Rule Code, and Description fields. You can enter a percentage if you wish to roll less than 100%. Leave the Rerun Budget Roll field blank unless the transactions on the previous budget roll failed the transaction edits and you are rerunning that roll. When re-running a budget roll, enter R in the Rerun Budget Roll field.
2-288
November 2010
The system calculates the transaction amount based on the percentage entered; multiplied by the budget line item amount; less any amount that you successfully rolled to the ledgers.
Example:
You have a budget line item for $100.00.Roll 15% of the budget. A transaction is created for $15.00 and successfully updates the ledgers. Roll the budget a second time with 40%. The transaction created is for $25.00. This is 40% of 100.00, which is $40.00; less the previous transaction of $15.00; yielding a total of $25.00.
22. Execute the Budget Roll to General Ledger Process (FBRBDRL) to create the budget
roll transactions on the Transaction Input Table (FGBTRNI).

23. Execute the Transaction Process (FGRTRNI), which reads and edits the transactions
on FGBTRNI.
24. Generate the Transaction Error Report (FGRTRNR). 25. If there are any errors in the budget transactions, correct the line items in the budget
and then rerun the Budget Roll Process (FBRBDRL).

26. When you repeat the roll process due to a failed transaction, enter R in the Rerun
budget roll field. This indicates that the last budget roll was not successful and that you are repeating the budget roll. If the Rerun budget roll field does not display R, the system generates incorrect transaction amounts on your budget roll transactions. You can rerun the budget roll as many times as is necessary until all your transactions are valid. You can run or rerun the budget roll as many times as necessary. If you do roll the budget in several steps, remember your final roll must equal 100%.
27. When the Budget Roll Process completes, navigate to FTMOBUD and enter C
(Closed) in the Status field in the Budget Phase data fields.Populating Status with C prevents you from running the roll process against this phase and allows you to start using the Budget Maintenance Form (FBABDMN) if you need to maintain your budgets during the current year.
28. To keep the budget tables current with the OPAL ledgers, enter original budget and
budget adjustment transactions on the Budget Maintenance Form (FBABDMN) instead of on the Journal Voucher Form (FGAJVCD). FBABDMN updates OPAL, the operating ledger and the Budget Line Item Table (FBBBLIN), and the Distributed Budget Table (FBRDIST).
November 2010
2-289
Budget Development and Maintenance Time Line Example
2-290
November 2010
Establishing Initial Budget Phases

There are three ways to load the initial budget phase: Use the Journal Voucher Entry Form (FGAJVCD) or the Journal Voucher Quick Form (FGAJVCQ). Use the Budget Request By Account Form (FBABDRA) or the Budget Request Form (FBABDRQ). Provide current budget detail or summary data to Banner Finance through the Generic Feed Table (GURFEED) and/or the Finance Feed Table (FGBTRNI).
Establishing Subsequent Fiscal Year Budget Phases

You can create subsequent years budget phases from two different sources: the Operating Ledger or the Budget Phase data.
Operating Ledger
1. Roll Prior or Current Fiscal Years Operating Ledger Budget Balances into Future
Fiscal Year Budget Phase (Action Indicator on FBABPRC equals O (Opal)). The following steps are guidelines and may change according to site policies and procedures.
2. Create a new budget phase using the Operating Budget Maintenance Form
(FTMOBUD).
3. Using the Budget Process Control Parameter Form (FPABPRC), establish the
appropriate action for the budget phase (Action Indicator equals O (Opal)). Enter the required Opal Source Data on FPABPRC that includes the Chart of Accounts and the Fiscal Year. Enter the additional parameters on FPABPRC. Use caution when you check the Overwrite File box.
4. Execute the Budget Build Process (FBRBDBB). 5. Query the results on the Budget Query Form (FBIBUDG).
Budget Phase Data

1. Roll Prior or Current Fiscal Years Budget Phase into Future Fiscal Year Budget Phase
(Action Indicator on FBABPRC equals B (Budget Line)). The following steps are guidelines and may change according to site policies and procedures.
(FTMOBUD). Define the Base Budget ID and Base Budget Phase from which the new phase is being created.
November 2010
2-291
appropriate action for the budget phase (Action Indicator equals B (Budget Line)). Budget Source Data will default to FPABPRC from the values entered on FTMOBUD. Enter the additional parameters on FPABPRC. Use caution when you check the Overwrite Files box.
Rolling Phase to Phase Within Budget IDs

Create and roll new budget phases within a budget ID through the budget life cycle as required, or create new phases to generate budget models under different conditions (Action Indicator on FBABPRC equals B (Budget Line)). The following steps are guidelines and may change according to site policies and procedures.
(FTMOBUD). Define the Base Budget ID and Base Budget Phase from which the new phase is being created.
appropriate action for the budget phase (Action Indicator equals B (Budget Line)). Budget Source Data will default to FPABPRC from the values entered on FTMOBUD. Enter the additional parameters on FPABPRC. Use caution when you check the Overwrite File box.
Changing Line Item Within a Phase

You can change a single budget line item within any phase using either the Budget Request By Account Form (FBABDRA) or the Budget Request Form (FBABDRQ). You may change the line by a dollar amount or percentage. Using a percentage requires the combination of the percentage amount entered in the Change Amount field in combination with a P (Percent) in the Percent field. If you leave the Percent field blank, you are indicating to the system a change in dollar amounts. The system does not require you to execute an update process after you change the line item record. Click or select Save to record the changes.
2-292
November 2010
Mass Change Budgets Example
Execute the Budget Mass Change Process (FBRMCHG). FBRMCHG provides you with the hardcopy results of the mass budget change based on the parameters entered on FBAMCHG. The Banner Finance System does not delete the parameter records entered on FBAMCHG. These records remain in the database and you may use them again to mass change budgets. You must review, update, or delete these parameter records before FBRMCHG executes again.
Note The Banner Finance System performs all the changes from the prior set of parameter records defined to FBRMCHG when you save a new set of parameter records. This is why it is so important to review and delete unwanted parameter records. Example:
Define parameter record #1 to increase a fund and its associated organizations by $100.00. Execute the change without deleting parameter record #1. Parameter record #1 remains in the database. If you increase that fund and its associated organizations by $50.00 using mass budget change parameter records, the total effect to that funds budget will be an increase of $150.00. To view existing FBAMCHG records, clear the form and select Enter Query and then Execute Query. Scroll through existing parameter records. Delete a parameter records as necessary. Modify existing parameter records when they display. Click or select Save to record the modifications to the database. Query the results on the Budget Query Form (FBIBUDG). If the Change all the budgets within check box is unchecked, the system applies the budget change ONLY to line items that match Org 220, Fund 103000, Account 6010,
November 2010
2-293
Program 610, and Activity 10. Refer to line item #2 since that is the only item to match all the FOAPAL values that you enter. If the Change all the budgets within check box is checked in this example, the system changes the budget line items 2, 3, 4, 6, 7, and 8. The system changes the budget items since these funds and organizations are equal to the hierarchy for the FOAPAL values that you enter. The mass change does not affect Line items 1 and 5. These two line items are part of Organization 200, which is outside (above) Organization 220. The parameter record definition contains Organization 220. Generate the following Budget reports to provide information on budget changes. To review sample output, refer to the Reports and Processes chapter.
FBRAPPR
Approved Budget Report - Displays the approved budget phase along with the prior year, current year, and the variance of the approved budget to the current amounts. Budget Mass Change Process - Use this process to change budget line items by an amount or a percentage. Create parameters used to execute this process from the Mass Budget Change Form (FBAMCHG). Budget Worksheet Report - Displays up to three budget phases with current year and prior year budget amounts from the budget file.
FBRMCHG
FBRWKSH
Merging Budgets
You may establish fraction phases (that is, multiple phases) during the development cycle and merge phases into the final phase in pieces (Action indicator on FBABPRC equals B (Budget Line)). You have the option to insert new records from multiple phases into the final phase of the budget without overwriting records or overwriting the budget table records.
1. On FPABPRC, enter the budget ID, phase, and chart of accounts. 2. Set the Action Indicator to B (Budget Line). 3. Enter the base budget ID in the Budget Source Data parameters. Use these parameters
to enter the existing budget phase information.

4. Enter the base budget ID. An example would be an operating or general ledger.
2-294
November 2010
5. Enter the base budget phase. This is one of your fraction or individual phases. 6. Enter the base chart of accounts.
Rolling Approved Budget Phase to OPAL

You can roll the approved budget phase to the new fiscal years OPAL budget ledger when needed. Enter A (Activate) in the Action Indicator on FBABPRC. The following steps are guidelines and may change according to site policies and procedures.
1. Execute the Approved Budget Report (FBRAPPR). 2. Build the Budget Distribution Parameter Form (FBABDDS) to define the budget roll
distributions for the Operating Ledger.

3. Execute the Budget Distribution Parameter Report (FBRBDDS) to distribute budget
amounts in the Line Item Table (FBBBLIN) into the Distributed Budget Table (FBRDIST).
4. Execute the Approved Distributed Budget Report (FBRAPPD). 5. Using the System Control Fiscal Year Set-Up Form (FTMFSYR), verify the period
into which you want to roll the budget exists and has an Open Status.
6. Verify on the System Data Maintenance Form (FTMSDAT) that Entity or Usage
Code is set to FGBTRNI and the Optional Code Number 1 is equal to BUDGET for the Attribute Code SYSTEM_ID.
7. Verify on the Sequence Number Maintenance Form (FOASEQN) that the Document
Type code and Document Prefix code fields equal L. L specifies Budget Line Item. Be sure to enter a value in the Maximum Sequence 7 field.
8. Close all open budget phases except the final phase in the Operating Budget
Maintenance Form (FTMOBUD). Confirm that the final phase contains an activation date and valid Finance Budget Rule Class Code BD01. You can roll future dated activation dates. For example, on June 30 you roll July 1 effective dated budget detail. If you closed a phase and you need to make corrections, change the Status back to Open.
9. Use the Budget Process Control Parameter Form (FBABPRC) to establish the
appropriate action for the final budget phase. Set the Action indicator to A (Activate). Enter the permanent rule code, temporary rule code, percentage rolled, and description on FBABPRC. Leave rerun budget roll blank unless a document from a previous roll failed and you are rerunning the budget.
10. Execute the Budget Roll to General Ledger Process (FBRBDRL).
November 2010
2-295
11. Execute the Transaction Interface Process (FGRTRNI). 12. Execute the Transaction Error Report (FGRTRNR). This report displays the error
messages for those transactions that do not successfully pass edits or available balance processing.
13. If required, correct errors in the Budget Development module using the Budget
Request By Account Form (FBABDRA) or Budget Request Form (FBABDRQ). Most errors will be caused by one or more of the FOAPAL elements being non-data enterable or one or more of the FOAPAL elements reaching its termination date.
14. To rebuild the Distributed Budget Table (FBRDIST), repeat Steps 1 through 4 and 10
through 13. When you have completed your budget entries, set the Action Indicator on the Budget Process Control Parameter Form (FBABPRC) to A (Activate) and initiate the Budget Roll Process (FBRBDRL).
15. Repeat Steps 9 through 12. 16. Execute the Posting Process (FGRACTG) and confirm the posting(s) using Budget
Availability Status Form (FGIBAVL) or the Organization Budget Status Form (FGIBDST).
Deleting a Phase by Account Type and Fund Type

You can delete segments of any budget phase. The system organizes these segments into the chart of accounts defined fund types and account types (Level 2 only). This enables building of budget models by funding source or account for easier global phase manipulations and projections. The following steps are guidelines and may change according to site policies and procedures.
appropriate action for the budget phase, Set the Action Indicator to D (Delete). Delete Options parameters require Type Indicator F (Fund) and/or A (Account) in conjunction with the Level 2 fund type and account type being deleted.
2-296
November 2010
Fixed Assets
The Fixed Assets module includes transfer, history, and reporting capabilities to enable you to establish and maintain a record of your fixed and moveable assets.
Establishing Commodity and Accounting Structure

The key to taking full advantage of the Fixed Assets module lies in the extent to which you define the supporting structure of the Commodity, Fund, and Account records. This section shows you how to create the appropriate records in the recommended sequence. The development of the record structure consists of three segments: Account Code connection Fund Code configuration Commodity Code setup
Account Code Connection

You create the appropriate Account Code connections on the Account Code Maintenance Form (FTMACCT) in the initial segment of defining the record structure for Commodity, Fund, and Account records. This step is required if you intend to use the Automatic Capitalization Process.
1. Establish account codes for Accumulated Depreciation and Depreciation Expense.
This step is required only if you intend to use the Depreciation Process.The Accumulated Depreciation account codes must have an Internal Account Type of 10 and an Account Class of F. The Depreciation Expense account codes must have an Internal Account Type of 40, 60, 70, 90, or 95. This set-up makes it possible to use an Equity, Labor, Direct Expense, Fund Addition, or Fund Deduction account code for posting the offset to the Accumulated Depreciation account code entry.
2. Create the Fixed Asset account codes for your fixed and moveable assets. The Fixed
Asset Account codes must have an Internal Account Type of 10 and an Account Class of F. You may enter both the Accumulated Depreciation and Depreciation Expense account codes in the appropriate fields while you are creating the Fixed Asset Account code, or you may add them later. This step links the Accumulated Depreciation and Depreciation Expense account codes directly to the Fixed Asset account code.
3. Establish your Capital Expenditure account codes. The Capital Expenditure account
codes must have an Internal Account Type of 60, 70 or 80. You may enter a Fixed Asset Account Code in the Asset Account field while you are creating the Capital Expenditure account code or after the record is established. This step links the Fixed Asset account code to the Capital Expenditure account. The Automatic Capitalization
November 2010
2-297
Process uses this link between the Capital Expenditure account code and the Fixed Asset account code to determine the debit account code for the capitalization transaction.
Example
Assume you created the following account code records: Account: 1831 - Accumulated Depreciation (Account Class: F) Account: 7631 - Depreciation Expense Account: 1830 - Vehicles (Account Class: F) Account: 7530 - Capital Expenditure - Vehicles The account code record for the Fixed Asset account code establishes the connection between the Fixed Asset account code and the related Accumulated Depreciation and Depreciation Expense account codes as follows: Account: 1830 - Vehicles Account Class: F Accumulated Depreciation Account: 1831 Depreciation Expense Account: 7631 The link between the Fixed Asset account code and the Capital Expenditure account code is created on the account code record of the Capital Expenditure account code as depicted in the following example: Account: 7530 - Capital Expense - Vehicles Asset Account: 1830 - Vehicles
4. Complete the account code segment of the set-up is to create account codes for the
Equity Account offset to the capitalization debit entry and Gain/Loss on Sale/ Disposal. A distinguishing characteristic of these remaining account codes is that they are used in developing the fund code configuration. It is important to create these account code records before the fund code records are established because they are an integral part of the fund code configuration. Once the account codes for the debit side are in place, the focus shifts to the account codes for the credit portion of the automatic capitalization transaction. The credit entry is typically charged to an Equity, Fund Addition, or Fund Deduction Account Code. Therefore, these accounts must have an Internal Fund Type of 40, 90, or 95. The last item in the account code creation phase is to set up account codes for Gain on Disposal/Sale and Loss on Disposal/Sale. These account codes will be used when the Sale of Asset function is performed in the Adjustment Process. You may create a single account code for both Gain and Loss, or you may establish a separate account code for each. These accounts must have an Internal Account Type of 40, 50, 60, 70, 90, or 95.
2-298
November 2010
Fund Code Configuration

The next phase of the commodity and accounting structure is to define the fund code configuration. You must define the elements of the configuration that apply to your situation if you intend to use the Automatic Capitalization, Origination Tag Extraction, Adjustment, or Depreciation Processes. This configuration is in reality a hierarchy composed of (in order of precedence) the Fund Code Maintenance Form (FTMFUND), the Fund Type Maintenance Form (FTMFTYP), and the Fixed Asset System Control Form (FFASYSC). It is a hierarchy because these default values are more global in nature than the account codes. These values may be unique to individual funds, to groups of funds at the fund type level, or to an entire chart of accounts. Thus, you may adjust the Fund Code configuration to conform to the unique qualities of your chart of accounts.
1. Begin defining the fund code configuration for the Fixed Assets module on the Fund
Code Maintenance Form (FTMFUND). Each Fixed Asset process that requires values from the fund code configuration looks to the fund code first to find these values. Therefore, any values established on the fund code override similar values created on the Fund Type Maintenance Form (FTMFTYP) and the Fixed Asset System Control Form (FFASYSC). First, create your Capitalization or Plant Fund codes. This step is essential because these funds will be connected to the source fund codes where the original acquisitions will take place in the next step. You may establish this connection by selecting the appropriate value from the Capitalization Fund Ind (Indicator) pull-down list. The valid values for this indicator are as follows: Cap Different or No Cap The source fund code does not equal the Capitalization fund code. This is the usual case for most fund accounting applications. The fund code entry in the Capitalization Fund field must have an Internal Fund Type of 96 when this option is selected. This selection also applies to situations where Capitalization is not used. The system assumes that you will not be using the automatic defaulting features and processes of the Fixed Assets module when you select this option and do not to make an entry in the Capitalization Fund field. The Capitalization Fund field is automatically set to the Fund Code of the Fund Code record when the Cap Fund Same As Source Fund selection is made. All other funds should have the Capitalization Fund Ind indicator set to Cap Different or No Cap (the default value), and values for the Capitalization Fund and Cap Equity Account fields should be entered as needed. You can leave the Capitalization Fund and Cap Equity Account fields blank if you do not intend to use the automatic capitalization feature for a particular fund or group of funds. Failure to follow this recommendation may result in inappropriate transaction postings from the Fixed Asset Adjustment Form (FFAADJF).
November 2010
2-299
Cap Fund Same As Source Fund The source fund code and the Capitalization fund code are the same. This option is intended primarily for those funds that exist on self-generated revenues and therefore have the option to account for fixed and moveable asset acquisitions within their own funds. The Capitalization fund code is automatically set to the source fund code when this selection is entered. It is recommended that you do not set the Capitalization Fund Ind indicator to Cap Fund Same As Source Fund on any funds with an Internal Fund Type of 96 on the Fund Code Maintenance Form (FTMFUND). Funds with an Internal Fund Type of 96 are typically used for Plant/General Fixed Asset Account Group funds. You should also not enter a value in the Capitalization Fund and Cap Equity Account fields for these funds. Only Auxiliary Enterprise/Proprietary funds should have the Capitalization Fund Ind indicator set to Cap Fund Same As Source Fund, and then the value for the Cap Equity Account field should be provided accordingly.
2. Enter the Capitalization Equity Account. This account is created in the account code
definition phase and must be valid for the Capitalization fund code. The Capitalization Equity Account is the credit or offset account for the automatic capitalization asset entry. This account code must have an Internal Account Type of 40, 90, or 95.
Example:
This example illustrates how the fund code values work with the account code values. Assume the following values for the fund and account codes: Fund Code: 3101 - Central Maintenance Fund Capitalization Fund Code Indicator: Source Fund different from Capitalization Fund Capitalization Fund: 9601 - Plant Fund Capitalization Equity Account: 3801 - Investment in Fixed Assets Account: 1830 - Vehicles Account Class: F Accumulated Depreciation Account: 1831 Depreciation Expense Account: 7631 Account: 7530 - Capital Expense - Vehicles Asset Account: 1830 - Vehicles The accounting distribution on the Invoice/Credit Memo Form (FAAINVE) appears as follows:
Fund Organization Account Program
3101
125
7530
21
Assuming an asset cost of $1,000.00, the Automatic Capitalization posting would appear as follows:
2-300
November 2010
Fund
Organization
Account
Program
Amount
DR/CR
9601 9601
1830 3801
1,000.00 1,000.00
D C
Notice how the fund and account code records work together to supply the Automatic Capitalization Process with the necessary data to complete the capitalization posting. In this example, the Capitalization Fund (9601) and Capitalization Equity Account (3801) are taken from the Source fund code record (3101), while the Fixed Asset account code (1830) is taken from the Capital Expense account code record (7530).
3. The remaining fields to be defined on the Fund Code Maintenance Form for the
capitalization funds are located in Window 6. These values deal strictly with the Depreciation and Adjustment Processes. The Depreciation/Posting Indicator allows you to select from three possible values: You can elect to record depreciation in the Fixed Assets module and the General Ledger. You can choose to record memo depreciation in the Fixed Assets module only. You can choose not to allow depreciation. This is a default value for all fixed or moveable assets that only need to be established on the Capitalization or Plant Fund code records. You are not required to establish this value on each capitalization fund code record. Any value established here may be changed on the Fixed Asset Depreciation Form (FFADEPR) for each individual fixed or moveable asset. The Expense/Equity Account Default Indicator only applies when you choose to depreciate and post to the General Ledger. It allows you to select whether the Depreciation Expense account code or the Capitalization Equity Account will default to the Fixed Asset Depreciation Form (FFADEPR). You are not expected to enter those account values here on the Fund Code Maintenance Form (FTMFUND).
4. The Gain Account and Loss Account codes, which were created previously in the
account code creation segment, also apply to the source fund codes. These codes also apply to the Capitalization fund code if it is the same as the source Fund Code. The Adjustment Process uses these account codes when the Sale of Asset function is selected. The gain or loss on sale is automatically calculated by the Adjustment Process, which looks for these account codes for posting that gain or loss. You may create a single account code for both Gain and Loss, or you may establish separate values for each account code. As previously stated, the account codes must have an Internal Account Type of 40, 50, 60, 70, 90, or 95.
5. The default Orgn (Organization), Prog (Program), Actv (Activity), and/or Locn
(Location) codes are used by both the Depreciation and Adjustment Processes. The Depreciation Process takes these values from the Capitalization fund code record and
November 2010
2-301
uses them as defaults for the Depreciation Expense Account distribution on the Fixed Asset Depreciation Form (FFADEPR). You may override these values on an asset-by-asset basis on FFADEPR. The Adjustment Process takes these values from the source fund code records and uses them to complete the accounting distribution for the Gain or Loss account codes for the Sale of Assets adjustment function. The same values may be defined on the Level I and/or Level II Fund Type Codes on FTMFTYP. The fund type values override any similar values that are established on the Fixed Asset System Control Maintenance Form (FFASYSC). The only exceptions that affect establishing the fund type records is that there is no Capitalization Fund Indicator and the Capitalization Fund must have an Internal Fund Type of 96. Any values defined on a fund type apply to all the fund codes for that fund type, except when the values are defined at the fund code level.
6. Complete the Fixed Asset System Control Maintenance Form (FFASYSC). The
values defined here take precedence only when no similar values are defined on the fund code and fund type records.You must complete the Fixed Assets System Control Maintenance Form for each Chart of Accounts record you employ. The only exceptions that affect establishing this record is that there is no Capitalization Fund Indicator and the Capitalization Fund must have an Internal Fund Type of 96 only.
Commodity Code Setup

The creation of the Fixed Asset commodity codes on the Commodity Maintenance Form (FTMCOMM) is the last piece of the commodity and accounting structure. Be aware that commodity codes alone cannot force the Automatic Capitalization Process to create capitalization entries, but they may trigger the establishment of Fixed Asset Master Origination Tag records. Only a properly designed account code structure can produce both capitalization postings and Fixed Asset Master Origination Tags. If you want to emphasize the use of commodity codes over accounts, you can devise a simpler structure of accounts than those who use the reverse strategy. The Fixed Assets module is flexible enough to accommodate either approach. An origination tag initially serves as the identifier for the temporary master record of any fixed or moveable asset. The origination tag is an automatically-generated or manually-created unique number. Origination tags refer to individual units, so if a quantity of 20 is invoiced on one item, each item has a unique origination tag number. The origination tag number remains with the asset record even after it is turned into a permanent record and provides an internal reference point/index. To designate a commodity code as a Fixed Asset commodity, check the Fixed Asset indicator. When such a commodity code is used in the Procurement or Payable Processes, a record is automatically inserted in the Origination Tag Collector Table (FFBOTAG) as soon as the payable is posted. This entry will be converted into a Fixed Asset Master Origination Tag when the Fixed Asset Origination Tag Extraction Process is run.
2-302
November 2010
The Fixed Asset Origination Tag Extraction Process (FFPOEXT) provides a consistent method of creating origination tag entries for the Asset Master record from the Procurement and Payables modules. Refer to the Reports and Processes chapter for more information about FFPOEXT. You can enter a value in whole years in the Default Useful Life field. This default value is designed to act as a standard value for useful life and is defaulted into the Fixed Asset Depreciation Form (FFADEPR) at the time it is created. This value may be overridden on FFADEPR on an asset-by-asset basis. You may also specify a default Expense Account Code value in the Default Account Code field. This value defaults into the accounting structure and will be used each time the commodity code is used in the Procurement or Payable Processes. The Finance System Control Maintenance Form (FOASYSC) contains a value and an indicator that must be set to enable the Automatic Capitalization and Origination Tag Extraction Processes. The Minimum Asset Value field allows you to establish the floor or threshold value for the creation of capitalization amounts. It is invoked when an invoice involving a Fixed Asset is posted. The other field is an indicator which determines when Origination Tag Extract records will be created. You may elect to create Origination Tag Extract records only at the time invoices are posted, or you may elect to allow creation of the Origination Tag Extract records when either invoices or receiving documents are posted. You may also elect on this form to submit your Fixed Asset Adjustment documents through the approvals process. The approval queues and levels may be established alone or as part of a system-wide document approvals structure.
Note If you chose to allow creation of the Origination Tag Extract records when either invoices or receiving documents are posted, receiving documents will not be considered for the Automatic Capitalization Process. Also be aware that Origination Tag Extract records created from receiving documents cannot be directly converted into a Permanent Tag record. A permanent tag is the unique user-created or system-generated asset tag identifier which is permanently assigned to the asset. Only Origination Tag Extract records created from invoices can be capitalized and converted into Permanent Tag records.
Integrating Fixed Assets With Procurement and Payable Processes

The most significant impact of Fixed Assets on the Procurement Process occurs when Fixed Asset-related commodities and accounting distributions are mixed with commodities and accounting distributions that are not related to Fixed Assets on any of the procurement documents (requisition, purchase order, etc.). The system displays a warning message telling you that invoicing will not produce complete Origination Tag data or Automatic Capitalization entries. You can avoid this by choosing one of the following options:
November 2010
2-303
Use commodity-based accounting. Complete the Origination Tag records on the Fixed Asset Master Maintenance Form (FFAMAST) and capitalize the records on the Fixed Asset Adjustment Form (FFAADJF). Use a General Encumbrance document (on FGAENCB) to feed Fixed Asset data to the Payable Process. To do this, enter a Fixed Asset-related accounting distribution on the document, then reference the encumbrance on an invoice. The invoice will use the information to produce the appropriate Origination Tag data and, if applicable, the Automatic Capitalization entries. The Payable Process is tightly coordinated with two different processes: the Origination Tag Process and the Automatic Capitalization Process. The Origination Tag Process is a two-stage process that creates the temporary Fixed Asset Master records. The Automatic Capitalization Process records the appropriate entries in the General Ledger to recognize the acquisition of capital assets. The initial stage of the Origination Tag Process and the Automatic Capitalization Process is invoked when an invoice is posted. These processes are triggered by the use of Fixed Asset-related commodities and/or accounting distributions. An invoice with an appropriate Fixed Asset-related accounting distribution can produce both Origination Tag records and Automatic Capitalization entries. Conversely, the use of Fixed Asset-related commodity codes alone can only produce Origination Tag records. A Fixed Asset-related accounting distribution is required for Automatic Capitalization to take place. If your emphasis is on commodity-based accounting, you only need to establish a very simple accounting structure to take full advantage of the Automatic Capitalization Process. The product of the Automatic Capitalization Process is merely a companion entry to the invoice posting. The effect of the Matching Process on this process is to produce collector table entries only as invoices and receiving documents are matched and posted.
Origination Tag Process

The two-stage Origination Tag Process is more sophisticated. Part 1 - Origination Tag Creation Matrix The first stage is set in motion when an invoice is posted. The process automatically examines the invoice commodity and accounting records and applies the Origination Tag Creation Matrix to see if any fixed or moveable assets are present. This process also uses the Origination Tag Creation Matrix to determine the type and composition of the Origination Tag records to be created. The first stage then completes its task by making the appropriate entries in the Origination Tag collector table (FFBOTAG). Each of these entries carries an Invoice Capitalization Tag Indicator which will direct the second stage of the process as to how to handle the entry.
2-304
November 2010
Table 1:
Origination Tag Creation Matrix
Available Account Code Choices Fixed Asset Commodity Code (For Creating Origination Tag Records)
Minimum Number of Accounting Distributions on the Invoice
Fixed Asset Related Expense Account Code
Fixed Asset Related Asset Account Code
NonFixed Asset Account Code
Minimum Asset Value* (For Creating Capitalization Entries)
FARINVC Cap Tag Indicator
1 1 X N/A >= C 2 1 X N/A < T 3 1 X N/A N/A C 4 2 X X N/A >= C 5 2 X X N/A < I 6 2 X X N/A N/A I 7 2 X X N/A N/A I 8 3 X X X N/A N/A I 9 1 X Y N/A T 10 1 X N N/A N 11 1 X N/A N/A M 12 1 X N/A N/A M 13 2 X X N/A N/A M 14 2 X X N/A N/A M 15 2 X X N/A N/A M 16 3 X X X N/A N/A M 17 1 X Y N/A M N/A - Not Applicable C - Create Capitalization Entries and Origination Tag Records T - Create Origination Tag Records Only I - Create Origination Tag Records Only with Incomplete Funding Source and/or Capitalization Information * The absolute value applies to the commodity unit price, including any discounts, additional amounts, and/or taxes. An absolute value is an amount for which the minus or plus sign is ignored.
Part 2 - Origination Tag Extraction Process The Origination Tag Extraction Process (FFPOEXT) is the second of the two stages and may be executed on demand. It scans the Origination Tag collector table (FFBOTAG) and creates Origination Tag records based on the Invoice Capitalization Tag Indicator contained in each invoice record, as illustrated in the Origination Tag Extraction Matrix shown on the following page. Individual Fixed Asset Master Origination Tag records are created for each unit of a commoditys quantity. For example, assume the following Fixed Asset-related commodity information is on an invoice:
November 2010
2-305
Commodity Code
Description
Quantity
Unit Cost
COM1 COM2
Desk Chair
3 2
$2,000.00 $1,000.00
The Origination Tag Extraction Process would produce five Fixed Asset Master Origination Tag records as follows:
Origination Tag # Description Cost
T00000001 T00000002 T00000003 T00000004 T00000005
Desk Desk Desk Chair Chair
$2,000.00 $2,000.00 $2,000.00 $1,000.00 $1,000.00
Although not illustrated here, the Origination Tag Extraction Process includes Taxes, Tax Rebates, Discounts, and Additional Amounts in calculating the unit cost assigned to be the cost in each Fixed Asset Master Origination Tag record. The only exception to this calculation occurs when recurring payables and the installments feature are used. Tax Rebates are not included in the cost calculation under these circumstances because the Extraction Process obtains the unit price information from the purchase order instead of the invoice. The purchase order unit price does not include the tax rebate because it is not calculated until you reach the invoice stage. It is easy to reflect the tax rebate as an adjustment to the resulting Permanent Tag records on the Fixed Asset Adjustment Form (FFAADJF).
Table 2:
Origination Tax Extraction Matrix
Information Derived From Invoice/Extraction Process Available Account Code Choices Fixed Asset Related Expense Account Code Fixed Asset Related Asset Account Code NonFixed Asset Account Code Origination Tag Information Populated In Master Record (FFBMAST, FFRMASF, & FFRMASA) Funding Source Window (FFAMAST)
FARINVC Cap Tag Indicator
Fixed Asset Commodity Code (For Creating Origination Tag Records)
Master Record Capitalization Window
Capitalization Direct Asset Indicator
1 2 3 4 5
T N C C I
N/A N/A X X
N/A N/A X
N/A N/A
N/A N/A N/A N/A N/A
COST NONE COST COST COST
ZERO $ NONE COST COST ZERO $
N/A N/A N/A Y N/A
2-306
November 2010
Table 2:
Origination Tax Extraction Matrix
6 I X N/A COST COST Y 7 I X Y COST ZERO $ N/A 8 I X N NONE NONE N/A 9 M X N/A COST ZERO $ N/A 10 M X N/A COST COST Y 11 M X Y COST ZERO $ N/A 12 M X N NONE NONE N/A N/A - Not Applicable C - Create Capitalization Entries and Origination Tag Records T - Create Origination Tag Records Only I - Create Origination Tag Records Only with Incomplete Funding Source and/or Capitalization Information M - Used only for Credit Memos that are related to Fixed Asset Account Codes or Commodity Codes. See the Origination Tag Extraction Process Matrix for more details on how this indicator code affects the creation of Origination Tag Records. * The absolute value applies to the commodity unit price, including any discounts, additional amounts, and/or taxes. An absolute value is an amount for which the minus or plus sign is ignored
Miscellaneous Information
This section describes additional Fixed Asset related payables topics. Credit Memos Credit memos are synchronized with the Fixed Assets module. You may reference a credit memo to an open Fixed Asset-related purchase order to allow a reference to any previously created origination tag records. However, once the credit memo becomes an origination tag, it is your responsibility to attach the new origination tag record to the existing origination tag asset record. Cancellation of Checks and Invoices The cancellation of checks and invoices will cause the system to change the System Status of origination and permanent tag records to C (Cancelled). This enables you to track and report these items separately. These asset records can also be deleted on the Fixed Asset Master Delete Form (FFAFDEL) if they have not been capitalized or adjusted. Direct Capitalization Direct Capitalization occurs when an invoice containing an asset account (Account Class F) is posted. The system ignores the minimum asset value and recognizes this as a capitalization entry. The Automatic Capitalization Process does not attempt to create additional capitalization postings. The impact on the Fixed Asset master record (FFBMAST, FFRMASF, FFRMASA) of the origination tag is two-fold. A Y is displayed in the Cap Ind (Capitalization Indicator) in the Master Information Window to signify that a capitalization entry is present for the asset. The second effect occurs in the Capitalization Information Window. There, the
November 2010
2-307
Direct Asset Ind (Indicator) is also set to Y. This window allows you to fill in any missing capitalization values by using the New Sequence function. Click the button and add any missing values. Multiple Tax Rebate Distribution and Capitalization The Multiple Tax Rebate Distribution feature for the Tax Rate Maintenance Form (FTMTRAT) poses an issue for the automatic capitalization process. The automatic capitalization process obtains the appropriate per unit cost, discount, additional amount, tax amount, and tax rebate amount from the Commodity block of the Invoice/Credit Memo Form (FAAINVE). Therefore, the tax rebate used for capitalization may differ from the tax rebate used to arrive at the expensed amount, since the rebate may vary for different accounting distributions. You can make the appropriate adjustments to the capitalized amounts using the Write Up/Down Adjustment function on the Fixed Asset Adjustment Form (FFAADJF).
Attachments and Components

The Fixed Assets module allows you to append additional asset records to existing permanent tags in order to identify a subordinate asset as an attachment or component of the parent asset. An Origination Tag record can be designated as an attachment to indicate an integral relationship between the parent and subordinate assets. An attachment is combined with the Primary Asset record and is accounted for and depreciated along with the Primary Asset tag.
Note An uncapitalized attachment can only be combined with an uncapitalized Primary Tag record. Likewise, only capitalized origination tag records can be attached to a capitalized Permanent Tag record.
You can also associate one Permanent Tag record to another by appointing the subordinate record as a component of the primary record. A component is associated with a Primary Asset record but is separately accounted for and depreciated. The following diagram illustrates the relationship between a parent asset and its attachments and components. Note that, although you can append an attachment to a component, you cannot append a component to another component or an attachment to another attachment.
2-308
November 2010
Parent Asset (Permanent Tag)
Component (Permanent Tag)
Attachment (Origination Tag)
Attachment (Origination Tag)
Depreciation in the Fixed Assets Module

Implementation Procedures for Depreciation of Fixed Assets
You must create Depreciation Maintenance records on FFADEPR for any fixed or movable assets that are depreciable. This helps ensure that the appropriate accounting treatment (Nonprofit or Proprietary) will occur for depreciable assets on the Fixed Asset Adjustment Form (FFAADJF). This is particularly important when using the following adjustment functions: Sale of Asset, Write Off, Write Up/Down Adjustment, Depreciation Adjustment, and Record Past Depreciation. Each of these functions look for the existence of a Depreciation Maintenance record to make decisions about recording the adjustments directly against the General Ledger asset accounts or as Operating Ledger revenues or expenses. The Accumulated Depreciation amounts and the Salvage Value displayed in the Capitalization Window of the Fixed Asset Master record (FFAMAST) and the Depreciation Maintenance record (FFADEPR) are maintained only as current values. This means that no history, aside from the accounting transactions, is maintained for any changes made to these values. Any change to Accumulated Depreciation and/or Salvage Value will not affect calculations of depreciation for a prior period. Changes will only be considered for current or future depreciation runs.
Creating the Framework for Depreciating Assets

It is recommended that you perform the following steps:
1. Create your depreciation method codes. On the Fixed Asset Depreciation Code
Maintenance Form (FTMDEPR), you can assign two-character codes to the desired combinations of Internal Depreciation Code [Straight Line (SL), Sum-of-the-yearsdigits (SY), Declining Balance (DB), or Double Declining Balance (DD)], and First
November 2010
2-309
Year Option [First half half/Second half none (HN), Full Year (FY), Half Year (HF), or Proportional (PR)]. The Title field, which is required, allows you to provide your own descriptive title for the depreciation method. For example, you may choose to create a depreciation method code SP that combines the Straight Line (SL) depreciation method with the Proportional (PR) first year option. Valid combinations are displayed in the following table.
Internal Depreciation Code First Year Option
DD, DB, SL SY
HN, FY, HF, PR HN, FY, HF
2. You may choose to establish standard default values for Depreciation Method Code
and Useful Life (in whole years) on the Fixed Asset Type Code Maintenance Form (FTMASTY). The Commodity Code Form (FTMCOMM) also contains a field for specifying a default Useful Life (also in whole years). If specified, these default values appear when you open the Fixed Asset Depreciation Form (FFADEPR) to complete your depreciation information. If you establish default values for Useful Life on both FTMASTY and FTMCOMM, the value entered on FTMCOMM takes precedence on the Fixed Asset Depreciation Form (FFADEPR).
3. Use the Fixed Asset Depreciation Form (FFADEPR) to define depreciation attributes
for each asset, where appropriate. This step enables you to take advantage of the Fixed Assets modules defaulting capabilities to automatically populate the Depreciation Method code, Useful Life, and depreciation account distributions from the Chart of Accounts structure and the Capitalization Information Window on the master record (FFRMASA). You may also override any of the default values at the time you are creating a record or at any time prior to running the Depreciation Process. The remaining necessary information is the Frequency Factor (select Monthly, Quarterly, Semi-Annual, or Annual), Salvage Value, and Start Date. The Remaining Periods field is system-calculated after you enter values in the Frequency Factor and Useful Life fields. While the Useful Life is always reflected in whole years, the Remaining Periods value is calculated using the Useful Life, First Year Option, Start Date, and the Frequency Factor and subtracting depreciation periods that have already occurred.
Note Depreciation records that contain account distributions split across two or more charts of accounts cannot be automatically depreciated. You may use the Depreciation Adjustment function on the Fixed Asset Adjustment Form (FFAADJF) to handle this situation.
2-310
November 2010
You can override any default values in the Asset Depreciation Expense Distribution information, except for the COA (Chart of Accounts) and Fund codes. These default values come from the Capitalization Information Window of the Fixed Asset Master Maintenance Form (FFAMAST). You must use the appropriate General Ledger adjustment function on the Fixed Asset Adjustment Form (FFAADJF) to change the COA and/or Fund code values.
4. Run the Depreciation Process (FFPDEPR). A variety of parameters enable you to
limit the records that will be considered for the process. You can run the process in audit or update mode. Both modes will produce a report, but only the update mode will amend the appropriate depreciation-related records. The Chart of Accounts is a required parameter. You may enter one or more charts, but the Chart of Account records must have identical Fiscal Year records (FTVFSYR). The process will calculate depreciation for any open periods from the Last Depreciation Date up to the Depreciation Date you specify in the process parameters, with the exception of prior period or catch-up depreciation. In this case, you must run the Depreciation Process to calculate and (where appropriate) post this prior depreciation before the asset record will be considered for current depreciation. This date can only be entered in the form of month and year.
Note Only one year of prior period depreciation can be calculated and posted per run. This limitation applies because the accounting usually differs for postings in either the prior year or in the current year.
Any depreciation record that is incomplete or is split across two or more charts will be flagged for errors by the Depreciation Process. The process will proceed to completion for all of the other records. All of the depreciation calculations are calculated on a monthly basis. The resulting depreciation charges are converted to the appropriate quarterly, semi-annual, or annual values. The Proportional (PR) first year option will take the appropriate number of months in the first year of depreciation, based on the Depreciation Start Date (FFADEPR), regardless of the frequency factor selected. The remaining proportional number of months from the first year will provide for an additional depreciation period to be added to the assets Remaining Life, in the case of the Annual frequency factor. This will allow for the final depreciation period. You must run the Posting Process (FGRACTG) to post the depreciation entries in the form of a journal voucher. The depreciation journal entries are treated as Adjustment transactions in the Fixed Assets module and are therefore prefixed with an M. The Depreciation Process will update the Remaining Periods and Last Depreciation Date and display them on the Fixed Asset Depreciation Form (FFADEPR), and the Accumulated Depreciation Amount on FFADEPR is updated by the Posting Process. The Accumulated Depr (Depreciation) field for each account distribution in the Capitalization Information Window of the Fixed Asset Master Maintenance Form (FFAMAST) is updated at this time.
November 2010
2-311
Transfers in the Fixed Assets Module

The Fixed Asset Transfer Form (FFATRAN) is used when it is necessary to create a replacement Permanent Tag for an existing Permanent Tag master record. Initiate the creation of the replacement tag on the Fixed Asset Transfer Form (FFATRAN) by selecting the Transfer option for the existing Permanent Tag number. Then select the Additional option and you may enter the new Permanent Tag number. You will be able to view both the old Permanent Tag record and the new Permanent Tag record on the FFATRAN form.
Adjustments in the Fixed Assets Module

Twelve adjustment actions or functions are available on the Fixed Asset Adjustment Form (FFAADJF). Some of these functions are equipped with additional features designed to accommodate special situations involving those functions. This section explains each of the functions and illustrates how the special features work. All of the functions, except for the Record Past Depreciation function, create journal voucher documents that are posted to the operating and/or general ledgers. The Record Past Depreciation function only creates adjustments to the Fixed Assets module because it assumes such a posting has already taken place in the ledgers. The Fixed Asset Adjustment Form consists of five separate windows: Main Window (header information) Adjustment Accounting Distribution Window Accounting Defaults Window Adjustment Revenue Distribution for Sale of Asset Window Adjustment Balancing/Completion Window Most of the functions use only the main window and the Balancing/Completion Window. The Adjustment Revenue Distribution for Sale of Asset Information Window applies only to the Sale of Asset function. The Adjustment Accounting Distribution Window and the Accounting Defaults Window only apply to the General Ledger adjustment functions.
Header Information
The Fixed Asset Adjustment Form is capable of accepting adjustments to many assets on a single adjustment document. The only limitation is that all asset tags entered on the same adjustment document must use the same adjustment function.
2-312
November 2010
In the first two blocks of the main window, the navigation is the same for all of the functions.
1. Enter the adjustment document number or NEXT for a system-generated number in
the Document Code field. This field is required.

2. Select the desired Function Type from the pull-down list. This field is required. 3. Select Next Block and enter the document Description or justification and the Trans
(Transaction) Date, which are required fields.

Note Adjustments cannot be dated prior to the capitalization date of any asset on the adjustment document. 4. The Text Exists indicator notifies you whether additional text exists for the
adjustment. If you wish to add text, click Document Text or use the menu option.
5. You may enter a user-defined cross-reference document number in the optional
Document Reference field. It is only necessary to complete the entries in these first two header blocks once per adjustment document. The Asset Data block enables you to make a nearly unlimited number of entries on a single document. The navigation in the Asset Data block and the subsequent windows in the Fixed Asset Adjustment Form will vary depending on the function you selected. Notice that the number of fields as well as some of the field names will change dynamically from function to function. This provides the necessary flexibility to accommodate the unique circumstances of each kind of adjustment. The Fixed Asset Adjustment Form works on a concept similar to that of commodity-based accounting used in the Procurement/Payable forms. The impact is that it primarily affects navigation and form handling. You must provide all of the necessary information for an asset adjustment before using the Next Record function to enter the next asset record to be adjusted. You may need to use the Next Block function to navigate to the Accounting Distribution and/or Revenue Distribution windows of the Fixed Asset Adjustment Form (FFAADJF). The system will not prompt you to use the Next Block function to complete the information for the asset record that you are adjusting. If you attempt to complete the adjustment document without completing the information necessary for the asset records, you will receive an error or warning message as appropriate to indicate that your records are incomplete. The system will not allow you to complete an adjustment document which contains incomplete adjustment records. The following guidelines assume that you successfully completed entry in the appropriate fields of the first two blocks of header information in the main window. When you select Next Block, you navigate to the Ptag (Permanent Tag) Code field.
November 2010
2-313
The Balancing/Completion Window is the last window you will access in any adjustment document. This window is common to all adjustment functions. Navigation in the Balancing/Completion Window is the same for all functions. You may elect to complete the document, or mark it In Process to save the data and return to it later and complete it. Completed adjustment documents will go through the Approval Process (FORAPPL) if you elect to establish the requisite approval information. The Posting Process (FGRACTG) will accept the completed and approved adjustment documents, if applicable, and make the appropriate entries in the ledgers.
Note The Ptag field will display the name Otag (Origination Tag) only for the Capitalization of Origination Tag function. This is the only adjustment function available for Origination Tags.
Function Types on FFAADJF

The Fixed Asset Adjustment Form recognizes valid data for each specific adjustment type. Some adjustment types require very specific input. Refer to the Automatic Hint for guidance on unique issues that may apply to each adjustment type. Sale of Asset This function allows you to dispose of an asset when cash proceeds from the sale are involved. The function will produce entries to reverse the balances in the asset and accumulated depreciation accounts, calculate and record any gain or loss, and make the appropriate cash and interfund cash postings for the sale proceeds. This function is available only for capitalized assets.
1. The Ptag (permanent tag) field is the starting point and is a required entry. When you
enter an asset tag in this field, the assets Description and Net Book Value are displayed.
2. Select Next Item to move to the Disposal field, where you must supply a disposal
method code. Click the button or select List to select from a list of disposal method codes.
3. Select Next Item to move to the Amount field. Enter the selling price of the asset in
this required field. Notice that an Automatic Hint message appears to inform you that you cannot access the Balancing/Completion Window. This is a reminder to select Next Block.
4. Selecting Next Block saves the account distributions without the necessity of
navigating to the Adjustment Accounting Distribution Window and moves you to the Balancing/Completion Window, except in cases where the Source Fund and Capitalization Fund codes differ. If this is the case, the system moves into the
2-314
November 2010
Adjustment Revenue Distribution for Sale of Asset Window. The system focuses on this difference because this may indicate that the gain should be reflected in the records of the Source Fund or other funds rather than the Capitalization Fund. Reverting to this window allows you to decide where the gain will be recorded. Since there is no decision to make when the Source Fund and Capitalization Fund codes are the same, you will navigate directly to the Balancing/Completion Window.
Note The Adjustment Accounting Distribution Window is not accessible for the Sale of Asset function.
The Adjustment Revenue Distribution for Sale of Asset Window is divided into two blocks. The first block displays the default account distribution values and the pro rata share of the gain for each affected accounting distribution. Select an account distribution from this block and select Next Block to access the second block. In this block, you distribute the gain for the selected account distribution to any number of account distributions. Return to the first block and select the next account distribution until the gain is fully distributed for each of the originating default account distributions displayed in the first block. You must select Previous Block from the first (top) block if you intend to enter another Permanent Tag for the Sale of Asset function. Select the Complete Block button or menu option to access the Balancing/ Completion Window. The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date. Write Off This function handles write-offs with or without accumulated depreciation. The function produces entries that reverse the balances of the asset and accumulated depreciation accounts. This function is available only for capitalized assets.
1. The Ptag (permanent tag) is a required entry. When you enter an asset tag in this
field, the system displays the assets Description and Net Book Value. You cannot access the Amount field when using this function because the system assumes that the entire cost of the asset will be written off.
2. Select Next Record to save the header and accounting distribution records and enter
another Permanent Tag for the Write Off function, if necessary.

3. Select Next Block to save the header and accounting distribution records for the last
entry and to access the Balancing/Completion Window.
November 2010
2-315
4. Click or select Complete to complete the document.
The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. You must complete the Depreciation Method Code on the FFADEPR form before adjusting the asset. The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date. Write Up/Down Adjustments This function allows you to adjust the value of an asset up or down, whether accumulated depreciation is involved or not. This function is available only for capitalized assets.
Note A write down to an asset that depreciates is credited to accumulated depreciation. A write down to an asset that does not depreciate is credited to the asset cost. A write up, regardless of whether the asset is depreciable or not, is debited to the asset cost. 1. The Ptag (permanent tag) is a required entry. When you enter an asset tag in this
field, the system displays the assets Description and Net Book Value.
2. Select Next Item to move to the Amount field. Enter the amount by which you want
to adjust the asset in this field. Please note that a write down amount must be preceded by a minus (-) sign.
another Permanent Tag for the Write Up/Down Adjustments function, if necessary.

The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. You must complete the Depreciation Method Code on the FFADEPR form before adjusting the asset.
2-316
November 2010
The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date. Permanent Tag Capitalization This function allows you to capitalize an asset that either came through the Procurement Process as uncapitalized or was entered as a gift/donation. Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Permanent Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record.
field, the system displays the assets Description, Cost, and Net Book Value.
2. Select Next Record to save the header and accounting distribution records and select
another Permanent Tag for the Permanent Tag Capitalization function, if necessary.

The following restrictions apply to this function type: You cannot adjust a capitalized asset. The Trans (Transaction) Date should be less than or equal to the system date. Origination Tag Capitalization This function allows you to capitalize a preliminary asset record that either came through the Procurement Process as uncapitalized or was entered as a gift/donation. This function prepares an uncapitalized origination tag for attachment to a capitalized permanent tag.
Note Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Origination Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record. 1. The Otag (origination tag) is a required entry. When you enter an asset tag in this
field, the system displays the assets Description, Cost, and Net Book Value.
November 2010
2-317
another Origination Tag for the Origination Tag Capitalization function, if necessary.

The following restrictions apply to this function type: You cannot adjust a capitalized asset. You cannot adjust an Origination Tag with a Permanent Tag. The Trans (Transaction) Date should be less than or equal to the system date. Depreciation Adjustment This function allows you to adjust accumulated depreciation up or down for depreciable assets. This function is available only for capitalized assets.
field, the system displays the assets Description, Net Book Value, Salvage Value, and Net Depreciable Value.
2. Select Next Record to move to the Amount field, where you enter the amount by
which you want to adjust accumulated depreciation for the asset. Please note if you want to adjust accumulated depreciation down, the adjustment amount must be preceded by a minus (-) sign.
another Permanent Tag for the Depreciation Adjustment function, if necessary.


The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. You must complete the Depreciation Method Code on the FFADEPR form before adjusting the asset. You cannot Adjust Depreciation until you run the Depreciation Process (FFPDEPR).
2-318
November 2010
You cannot adjust an asset that does not have a Depreciation Post Code of P. The depreciation post code is used to determine whether depreciation entries are posted to both the Fixed Assets module and the General Ledger, posted to the Fixed Assets module only, or not posted at all. The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date must be greater than the Last Depreciation Date. The Trans (Transaction) Date should be less than or equal to the system date. Record Past Depreciation This function allows you to update an assets master record (FFBMAST) and depreciation maintenance record (FFBMAST) for past depreciation already recorded in the ledgers. This function is only available for capitalized assets that have not been previously depreciated or adjusted in the Fixed Assets module. It will not create postings for the ledgers. You can use the Depreciation Process (FFPDEPR) instead to post past depreciation to both the ledgers and the Fixed Assets module.
field, the system displays the assets Description, Net Book Value, Salvage Value, and Net Depreciable Value.
2. Select Next Record to move to the Amount field. Enter the amount of prior
depreciation you wish to record for the asset in this field.

another Permanent Tag for the Record Past Depreciation function, if necessary.

The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. You must complete the Depreciation Method Code on the FFADEPR form before adjusting the asset. You cannot adjust an asset which does not have a Depreciation Post Code of P. You cannot record Past Depreciation before the Capitalization Date.
November 2010
2-319
If the asset has previous adjustments or recorded depreciation, you cannot Record Past Depreciation. The Trans (Transaction) Date should be less than or equal to the system date. GL Change - Asset Account This function is the first of five functions that deal with reclassification of capitalization values for both the General Ledger and the Fixed Assets module. The function will reverse the asset balance in the original account and record the balance in the new asset account. Any accumulated depreciation for the asset will automatically be reclassified to the accumulated depreciation account associated with the new asset account. Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Origination Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record.
field, the system displays the assets Description, Cost, and Net Book Value. You may not access the Amount field because this function only allows you to reclassify the Asset Account code.
2. Select Next Block to move to the Asset Account Code field in the Adjustment
Accounting Distribution Window. Enter the new or destination asset account code. You can use the Options Menu or the Accounting Defaults button to access the Accounting Defaults Window. In this window, you may view the default capitalization accounting values prior to making any changes. You must acknowledge the OK button before you can perform any other actions.
3. From the Adjustment Accounting Distribution Window, select Previous Block to
return to the Ptag field in the Asset Data block of the main window.
another Permanent Tag for the GL Change - Asset Account function, if necessary.
5. Select Next Block from the Adjustment Accounting Distribution Window to save the
header and accounting distribution records for the last entry and to access the Balancing/Completion Window.
The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset.
2-320
November 2010
The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date. GL Change - Equity Account This function is the second of five functions that deal with reclassification of capitalization values for both the General Ledger and the Fixed Assets module. The function will reverse the asset balance in the original equity account and record the balance in the new equity account. Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Origination Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record.
field, the system displays the assets Description, Cost, and Net Book Value. You cannot access the Amount field because this function only allows you to reclassify the Equity Account code.
2. Select Next Block to move to the Equity Account Code field in the Adjustment
Accounting Distribution Window. Enter the new or destination equity account Code. You can use the Options menu or the Accounting Defaults button to access the Accounting Defaults Window. In this window, you may view the default capitalization accounting values prior to making any changes. You must exit from this window before you can perform any other actions.
4. Select Next Record to save the header and accounting distribution records and to
enter another Permanent Tag for the GL Change - Equity Account function, if necessary.

The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date.
November 2010
2-321
GL Change - Fund Code This function is the third of five functions that deal with reclassification of capitalization values for both the General Ledger and the Fixed Assets module. This function will reverse the asset account balances in the original fund and record the balance in the same account in the new fund. Any accumulated depreciation for the asset will be reclassified automatically to the same accumulated depreciation account in the new fund. Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Origination Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record.
field, the system displays the assets Description, Cost, and Net Book Value. You cannot access the Amount field because this function only allows you to reclassify the Fund code.
2. Select Next Block to move to the Fund code field in the Adjustment Accounting
Distribution window. Enter the new or destination fund code. You can use the Options menu or the Accounting Defaults button to access the Accounting Defaults Window. In this window, you may view the default capitalization accounting values prior to making any changes. You must exit from this window before you can perform any other actions.
another Permanent Tag for the GL Change - Fund Code function, if necessary.

The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date.
2-322
November 2010
GL Change - Fund and Equity This function is the fourth of five functions that deal with reclassification of capitalization values for both the General Ledger and the Fixed Assets module. The function will reverse the asset and equity account balances in the original fund and record the balances in the same asset account and new equity account of the new fund. Any accumulated depreciation for the asset will be reclassified automatically to the same accumulated depreciation account in the new fund. Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Origination Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record.
field, the system displays the assets Description, Cost, and Net Book Value. You cannot access the Amount field because this function only allows you to reclassify the Fund and Equity Account codes.
2. Select Next Block to move to the Fund code field in the Adjustment Accounting
Distribution Window. Enter the new or destination fund code.

3. Select Next Item to move to the Equity Account code field. Enter the new or
destination equity account code. You can use the Options menu or the Accounting Defaults button to access the Accounting Defaults window. In this window, you may view the default capitalization accounting values prior to making any changes. You must exit from this window before you can perform any other actions.
another Permanent Tag for the GL Change - Fund and Equity function, if necessary.

The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset.
November 2010
2-323
The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date. GL Change - Cap Amount/Account This function is similar to a general journal entry in that there are almost no restrictions. You may change the Fund, Asset Account, Equity Account, and/or the Cost, simultaneously or separately. Any change to an Asset Account will also cause the same change in the associated Accumulated Depreciation Account. Before you use this function, the Capitalization portion of the Fixed Asset Master record for each selected Origination Tag must be completed. Completion means that a fund, asset account, equity account, and cost amount must be present for each account distribution on each selected Master record. Any adjustment made to an assets cost amount using the GL Change - Cap Amount/ Account function (GLCE) updates the assets original cost. This function is unlike the other adjustments, which create new historical records to record the adjustment. The function should therefore not be used to update the cost amount of an asset after depreciation has commenced for that asset. The function will reverse the balances in the originating fund and/or accounts (Rule Class GLRE) and record the balances in the new fund and/or accounts (Rule Class GLCE). If you use the function to change only the asset cost and/or accumulated depreciation amount, only those changes will be reflected (Rule Class GLCE); no reclassifications will take place.
field, the system displays the assets Description, Cost, and Net Book Value. You cannot access the Amount field here; changes to the asset cost or depreciation amount must take place in the Adjustment Accounting Distribution Window.
2. Select Next Block to move to the Adjustment Accounting Distribution Window. You
may access the Fund, Asset Account, Equity Account, Amount, and Depreciation Amount fields and enter new values in any or all of them.
Note The entries you make in the Amount and Depreciation Amount fields are not the amounts by which you will adjust, but the amounts you will adjust to.
You can use the Options menu or the Accounting Defaults button to access the Accounting Defaults Window. In this window, you may view the default capitalization accounting values prior to making any changes. You must exit from this window before you can perform any other actions.
2-324
November 2010
another Permanent Tag for the GL Change - Cap Amount/Account function, if necessary.

The following restrictions apply to this function type: You cannot adjust a non-capitalized asset. You cannot adjust a disposed asset. You cannot adjust a Permanent Tag record that has attachments without first detaching the attachments. The attachments can be re-attached after the adjustment is completed using the Origination Tag - Update Asset option on the Fixed Asset Master Maintenance Form (FFAMAST). The Trans (Transaction) Date must be greater than the Last Adjustment Date. The Trans (Transaction) Date should be less than or equal to the system date.
Fixed Asset DTAG Processing Form (FFADTGP)

This section contains information about posting debits or credits to Fixed Assets, querying adjustment documents, and capitalizing non-invoice fixed assets expense accounting line items.
Posting a Debit to Fixed Assets - Available Options

1. Create an origination tag (Otag).
On the FFADTGP form, select the Create action, enter missing procurement information, then select Perform Action to create an Otag in the Fixed Assets module. The system inserts funding source records and capitalization records into the Fixed Assets module.
2. Update an Otag or Ptag.
On the FFADTGP form, select the Update action, enter the number for the tag, then select Perform Action to update data for the tag in the Fixed Assets module. The system will insert a new funding source record for a positive amount into the Fixed Assets module.
November 2010
2-325
If the Dtag has been capitalized, the system creates a new set of capitalization records by duplicating the existing records and inserting a new record based on the document source FOAPAL and the Dtag amount. If the Dtag has not been capitalized, then no capitalization changes will be made.
3. Clear/Offset a Dtag.
On the FFADTGP form, select the Offset action. Enter the offsetting Dtag and select Perform Action. This marks both Dtags as resolved and does not update any fixed asset records. The referenced Dtag must have a pending status (that is, not resolved or incomplete) and be for the same amount but with an opposite sign.
Posting a Credit to Fixed Assets - Available Options

1. Delete an Otag. Only uncapitalized Otags can be deleted.
On the FFADTGP form, select the Delete action, enter the Otag number, and reconfirm the deletion on the deletion form that pops up automatically. Select Perform Action to delete an uncapitalized Otag from the Fixed Assets module.
2. Inactivate an Otag or Ptag.
On the FFADTGP form, select the Inactivate action and enter the tag number. You can do this only if the tag is active and the sum of the net book value and the Dtag entry is zero. The system will insert a new funding source record for a negative amount. If the Dtag has been reverse capitalized, the system creates a new set of capitalization records by duplicating the existing records and inserting a new record for a negative amount based on the document source FOAPAL and the Dtag amount.
3. Update an Otag or Ptag.
On the FFADTGP form, select the Update action. Enter the tag number. Select Perform Action. The system will insert a new funding source record for a negative amount. If the Dtag has been reverse capitalized, the system will create a new set of capitalization records by duplicating the existing records and inserting a new record for a negative amount based on the document source FOAPAL and the Dtag amount.
4. Clear/Offset a Dtag.
On the FFADTGP form, select the Offset action, enter the appropriate Dtag, and select Perform Action. This marks both Dtags as cleared and does not update any fixed asset records. The referenced Dtag must have a pending status and be for the same amount but with an opposite sign (for example, debit vs. credit).
2-326
November 2010
Querying Adjustment Documents

Posted adjustment documents may be viewed on the Fixed Asset Adjustment Query Form (FFIADJF). A validation list of adjustment documents is available on the Fixed Asset Adjustment List Form (FFIADJL). Finally, a listing of adjustment documents by Permanent Tag or Permanent Tag adjustments by document is available on the Fixed Asset Adjustment History Form (FFIADJH). You may also view the posted journal entries on the Document Retrieval Inquiry Form (FGIDOCR). The adjustment documents are identified by an M prefix.
Capitalizing Non-Invoice Fixed Asset Expense Accounting Entries

You can enter a Journal Voucher (JV), Direct Cash Receipt, or Stores Inventory transaction to capitalize Fixed Asset expense accounting line items. See Process Flow on page 2-328. These transactions are processed through the FFBOTAG table if the following criteria are met.
Requirements for FFBOTAG Table Entries

The document tag feed indicator in the system control table (FOBSYSC) must be set to Y for the document type. The rule class for the accounting sequence must have a process code of O030 or O031. The account must be associated with a fixed asset account in the FTVACCT table. (That is, FTVACCT_ACCT_CODE_ASSET must be populated.)
Requirements for Capitalization

Capitalization can be either positive or negative, depending on whether the transaction amount is a debit or a credit. When any of the following conditions are met, the transaction amount on an accounting line item is capitalized, and the FFBOTAG Cap Indicator is set to Y. When the preceding requirements for FFBOTAG Table Entries are met, And the absolute value of the amount for the accounting sequence equals or exceeds the capitalization threshold amount set in the system control table (FOBSYSC), the amount is capitalized. And capitalization did not occur in the year-to-date posting because the absolute amount was less than the threshold amount, and the rule class includes a process code of G073, the amount is capitalized.
November 2010
2-327
When the preceding requirements for FFBOTAG Table Entries are not met, because the document tag feed indicator in the system control table is set to N but the account is associated with a fixed asset account, and if the rule class has a process code of G073, the amount is capitalized but no entries are recorded in the FFBOTAG table.
Process Flow
Capitalization
Journal Voucher (FGAJVCD) G /L
Working File
Direct Cash Receipts (FGADCSR)
FFBDTGH FFRDTGA FFRDTGD
Posting
FFBOTAG
Extraction
(FGRACTG)
(FFPOEXT)
Dtag Extraction
Otag Extraction Stores Inventory (FSAISSU)
FFBM AST
DTAG Processing (FFADTGP)
O tag = Origination tag Ptag = Permanent tag D tag = Document tag
1. Access the Finance System Control Form (FOASYSC) and select documents (such as
journal vouchers, direct cash receipts, and stores issues) for which a capitalization entry should be made and a Dtag working file record created. For all documents marked as include on FOASYSC, the Posting Process (FGRACTG) creates capitalization entries to the General Ledger with a process code of G073 for any transaction with a Fixed Asset expense account code. Capitalization takes place when the absolute value for the dollar amount of the transaction exceeds, or equals, the minimum capitalization amount and is for the amount of the transaction. Credit entries result in a capitalization reversal entry to the General Ledger when the absolute value of the transaction amount meets or exceeds the minimum capitalization amount specified on FOASYSC.
2-328
November 2010
2. Access one of the following forms: Journal Voucher, Stores Issues, and Direct Cash
Receipts.
3. Enter the required information. If the account code is a fixed asset expenditure
account, you may want to enter related purchasing information, such as purchase order number, invoice, or issue ticket, as document text.
4. Complete the documents, then post them by running the Posting Process
(FGRACTG). During the posting process, the system will make the appropriate capitalization entries and insert a record into the temporary tag table (FFBOTAG).
5. Run the Fixed Asset Origination Tag Extract Process (FFPOEXT). This process
inserts a record into the Dtag tables (FFBDTGH, FFRDTGA, and FFRDTGD) to create fixed asset working file entries known as document tags, or Dtags.
6. Access the Fixed Asset Dtag Processing Form (FFADTGP). You can perform the
following tasks: Create new origination tags (Otags) in the Fixed Assets module. Update existing tags with additional funding source records and a new set of capitalization records Clear/offset other Dtags. Delete existing Otags, if they are uncapitalized. Inactivate existing Ptags/Otags. Enter additional Dtag records and adjust the Dtag amount to create multiple fixed asset entries from one financial transaction. The sum of all Dtag amounts must equal the original transaction amount.
Warning Although it is possible to add non-capitalized Dtags to capitalized Otags, this is not recommended since this may create an out-of-balance condition between the Fixed Asset detail records and the General Ledger and can also impact depreciation calculations.
Cost Accounting
Cost Accounting Billing Process
The Cost Accounting Billing Process calculates customer charges and creates the appropriate transaction ledger entries for a project. These charges are based on the number of units (hours) that you recorded for this project in a particular billing cycle.
November 2010
2-329
This process also performs the following functions: Creates a charge to the customer expense account distribution that you define on the Project Charge Maintenance Form (FTMCHRG). It also liquidates part of the encumbrance (if one exists) and creates an income entries for a project. Calculates a charge for every customer account distribution. Creates journal table entries. Creates billing detail table entries. Updates the employee, inventory, equipment, and project/customer tables. Deletes the project detail records after the system updates the ledgers.
Before Running the Billing Process

Before you run the billing cycle, complete the Cost Accounting Batch Parameter Maintenance Form (FCAPARM) using BILL as the Process Code. You can select from the following options when you run the billing process: Selectively for a specific project For all projects for a specific chart of accounts For all projects for a specific organization This process also enables you to select and process project detail entries by date. Enter the parameters you wish to use to control this billing run. Check the box to activate the Update Database indicator on the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). When this box is unchecked, the billing process runs in an audit mode. You may view the results of this audit run using the Cost Accounting Billing Report (FCBBILL). This enables you to determine the results of the cost accounting billing process without updating the database.
Running the Billing Process

To run the billing process and update the ledgers:
1. Complete another entry on FCAPARM. 2. Check the Update Database box. 3. Enter a Document Number. 4. Run the batch billing process, using the following guidelines.
2-330
November 2010
Certain functions require the Update Database box on the Cost Accounting Batch Parameter Maintenance Form (FCAPARM) to be checked. The Cost Type and Unit fields also influence these functions. Enter this information on the Cost Accounting Maintenance Form (FCAACCT). The system calculates a charge for each customer account distribution associated with a percentage of the project. This calculation is a result of selected project detail table entries created for this project's billing cycle. The system calculates this charge as follows: The cost type from the project detail is used to access the defining table for the association of internal rates to a cost type for the Rate Code/Cost Type Maintenance Form (FTMRTCT). The rate codes are used to access the defining table for the internal rate value for an organization. The Project/Customer Rate Maintenance Form (FTMCRAT) defines any external rate values for the customer for this project in place of the internal rate code. If an external rate exists, the system applies it to the base rate, then multiplies it by the number of units to derive a total amount charge. If an external rate is not present, the system multiplies the internal rate value by the number of units to derive a total amount charge. These charges appear on three tables which are entered by project. These tables are: Project/Customer Charges Table (FCBPRJC) The system summarizes and stores charges as an amount and number of units by rate type by customer. Project History Table (FCBPHST) The system stores charges as a rate and number of units by internal rate code by billing date. Project/Customer Charges Validation Table (FTVCHRG) The system summarizes and stores charges as a billed amount by account distribution. The system creates journal table entries with a rule class code of BILL, BILE, or BILI for processing by FGRTRNI. If the customer's account distribution is encumbered, the rule class is BILE. Otherwise, it is BILL. The system accepts a rule class code of BILI for the income account distribution defined on the Project Maintenance Form (FTMPROJ). The document number for these transactions is the Document Number entered on the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). The accounting processes for the rule class codes partially liquidate the encumbrance set aside for the customer(s) account(s) if previously encumbered, and debit their expense account(s). The servicers account receives a credit to record revenue, defined on the Project Maintenance Form (FTMPROJ). The transaction description for the debit entry is Customer Charge from CA Billing and the transaction description for the credit entry is Project Recovery from CA Billing. If the
November 2010
2-331
Memo Project box is checked, the system does not create any transactions for the general ledger. The system creates transaction entries for the Billing Detail Table (FCTBDTR). You can then run the Billing Detail Report (FCRDBTR) at your discretion. The system deletes the project detail records, as they represent the units to bill for this billing cycle and deletes the Cost Accounting Parameter Table (FCAPARM) for the billing process to conclude the billing cycle process. The Billing Detail Report (FCRBDTR) displays all detailed transactions posted against a specific customer's accounts from the first billing run to the last billing run. The Billing Summary and Billing Detail Reports are informational reports only. The billing process does not produce an actual bill but instead provides data with which you create a bill. The billing process actually bills the customer's account distribution as it creates ledger transactions.
Setting up Rates for Cost Accounting

The Cost Accounting module has several different forms to maintain rates and support both manual and automatic rate calculations. The forms listed in this section are used to establish rates. Refer to the following process flow to see how these forms integrate in the cost accounting rates process.
2-332
November 2010
1 FTMRTYP
FTMINRT
2 FTMINVT FTMRRUL
9 7 FTMCTYP FTMIRTO 10 6 FCAEMPL FTMCSTO
FTMEQPT
13
FTMRTCL
8 FCAINRT
11 FTMRTCT
FTMCLAS
12
B
14
FTMARAT
FTMRTYP Rate Type Code Maintenance Form

This form enables you to establish the high level rate definitions required at an installation. The rate types delivered with the system (such as DL for Direct Labor) have sequence numbers associated with them. The automatic rate programs use these sequence numbers. Leave the seed data on this table as delivered; do not alter this data.
November 2010
2-333
FTMRRUL Rate Type Rule Maintenance Form

This form maintains the rate types which form the core of the Cost Accounting rate facility. It sets various flags used by the automatic rate calculation jobs and also forces specific fields required on input forms depending on the rate (for example, Labor Codes require Employee ID numbers). Do not change any data on this form. This maintenance form is comparable to the System Data Maintenance Form associated with the General Ledger module.
FTMINRT Internal Rate Code Maintenance Form

Internal Rate codes specify the kind of rate associated with a cost. For example, internal rate codes could be assigned to distinguish clerical and system analyst labor. Internal rate codes are linked in this form to the rate types already established in the Rate Type Code Maintenance Form (FTMRTYP). In this example, both the clerical and system analyst internal rate codes would be associated with the Direct Labor rate type.
FTMINVT Inventory Code Maintenance Form

This form establishes inventory codes which can be associated with a servicing organization. The Unit Price, Estimated Units Used, and Actual Units values are used in the automatic rate calculation program for inventory.
FTMEQPT Equipment Tag Maintenance Form

Use this form to create equipment tags to use with cost types that relate to equipment rentals. The automatic rate calculation program uses the detail in this form for equipment.
FCAEMPL Employee Maintenance Form

Use this form to establish an employee ID to use on work orders. The ID must exist on the system prior to being referenced on this form. Use the hours, wages, benefits and classification information in the automatic rate calculation program for Direct Labor and Indirect Labor rate calculations.
FTMIRTO Rate Code by Organization Maintenance Form

Use this form to establish the valid rate codes (established on FTMINRT) used with the servicing organization.
2-334
November 2010
FCAINRT Internal Rate Maintenance Form

This form enables you to create the actual rate value associated with a rate code and organization.
Note Establish a rate of $1.00 for direct charges (Internal Rate Code DGCL) for all your organizations from the financial ledgers. The system requires this form if you do not use automatic rate calculation. If you use automatic rate calculation, the system populates this form.
FTMCTYP Cost Type Code Maintenance Form

Cost types are the codes used to input actual cost accounting charges. These codes can represent one or more cost factors associated with a unit of work. An example of a cost type is a type of job, such as painting.
FTMCSTO Cost Type by Organization Maintenance Form

Use this form to enter the cost types (established on FTMCTYP) which are used for each servicing organization. For example, the maintenance department manages the painting activity, so the cost type for painting is associated with the maintenance department on this form.
FTMRTCT Rate Code by Cost Type/Organization Maintenance Form

Use this form to associate one or more rates to a cost type for the servicing organization. A painting cost type might include the cost of the painter's hourly rate, plus the cost associated with the equipment, plus an overhead factor to cover the cost of a supervisor, plus the time to complete related paperwork.
FTMCLAS Classification Code Maintenance Form

It is only necessary to maintain this form if you use the automatic rate calculation process. You can establish different employee classifications which you later reference to specific employee IDs.
FTMRTCL Rate Code/Classification by Org Maintenance Form

This form is required only if you use automatic rate calculations. The form is used to associate a servicing organization with rate codes and employee classifications.
November 2010
2-335
FTMARAT Rate Account Maintenance Form

This form is only required if you use automatic rate calculations. This form establishes the account codes that are associated with the Inventory Handling, Material Management, and Equipment Rental rate indicators. If an account is not established for each of these rate types, the automatic rate calculation process does not work for that rate type.
2-336
November 2010
Defining Project/Work Orders and Entering Costs
November 2010
2-337
Establishing a Project Work Order

To create a project work order, you must first create a customer or use a customer that already exists on your system. Refer to the instructions for the Customer Maintenance Form (FTMCUST) if you need to create a valid customer. There are two steps to establish a project: you must create a project work order and create the accounting distribution for a customer. The process involves the Project Maintenance Form (FTMPROJ) and the Project Charge Maintenance Form (FTMCHRG). Creating a Project Work Order To create a project work order, access the Project Maintenance Form (FTMPROJ).
1. Enter the Project Code and project Title. Click Project Code or select List to select
a project code from a list window.

2. Select Next Block.
The Start Date field defaults to the system date, but you may override it.
3. Enter the Termination Date for the project.
The Last Activity Date defaults if you are modifying an existing project.
4. Use the Memo Project check box to designate whether the project is a memo status
project type. If you check this check box, the charges to the project do not affect the ledgers. This merely keeps track of project charges within the Cost Accounting module. To enter text for this project, click Project Text or select the menu option to access the General Text Entry Form (FOATEXT).
5. The COA and Orgn fields are required. Use the COA (Chart of Accounts) field to
access and validate the IFOAPAL fields that you enter on the form. The Orgn field represents the organization you must access when you process internal rates and cost types. When you enter and process project charges, you can only use those rates and cost types that are defined to this organization.
6. The IFOAPAL fields (Index, Fund, Orgn (Organization), Acct (Account), Prog
(Program), Actv (Activity), and Locn (Location)) represent the income account distribution of the servicer. The system credits this account distribution with the revenue this project creates. Creating and Maintaining Customer Accounting Distribution for a Project Once the project work order is completed, access the Project Charge Maintenance Form (FTMCHRG). Use the Project/Work Order Maintenance Menu (*FINCAPC) or click Customer Charge or select Count Hits from FTMPROJ. Use FTMCHRG to create and
2-338
November 2010
maintain customer accounting distributions for each project. You must define at least one customer before you can collect charges against a project.
1. Enter the desired Project Number in the Key Information. Click Project or select
List to select a project number from a list window.

2. The system defaults the project name and populates the Transaction Date with the
current date. You may enter a new transaction date for which to post encumbrance transactions to the ledgers.
3. Select Next Block to access the account distribution data and enter customer
information.
4. The Customer ID is a required field. You must predefine the customer within cost
accounting on the Customer Maintenance Form (FTMCUST). For additional information, refer to Adding Customers to Banner Finance on page 2-171.
5. Enter the expense account distribution that you intend to charge against when you
process project charges. These fields are required when the Memo Project box on FTMPROJ is unchecked. Only the Fund and Acct (Account) fields are required when the customer is an external customer. A button and List is available for each of the FOAPAL fields.
6. The Percent field represents the allocation of charges for the project that this
customer is to receive. The total of all the customer percentages must equal 100%.This is a required field.
7. The Max Billable field is a required field only when the Encumber box is checked.
This field represents the total encumbrance dollar amount for this account distribution. The Max Billable field is not related to the percent allocation for project charges. The system defines an internal customer if this customer is defined as a financial manager within the Banner Finance System. Otherwise, the customer is considered an external customer.
8. Check the Encumber box to mark the project as an encumbrance if you are
authorized to do so.
9. The NSF Override box is a non-sufficient funds override indicator. Check this box to
override the budget if you are authorized to do so.

10. Click or select Save to save the project charge information. 11. Before you complete the project, the sum of all the customer percentages must equal
100%. Check the Complete box and click or select Save.
November 2010
2-339
When you complete this form, the system posts an approval record to the Approved Document Table (FOBAPPD) to signal that a project document is waiting to be posted only if the customer was encumbered. Run the Posting Process (FGRACTG) to post the encumbrances defined to the project. Once you post the project, only the percentage distribution may be changed.
Warning Do not try to create and bill a project in the same day. You must establish the postings for the project encumbrance prior to any billing runs.
Defining Additional External Rates for a Project/Work Order

This optional process enables you to change the rate values for customers by project. To begin this process, access the Project/Customer Rate Maintenance Form (FTMCRAT) from the Rate Structure Maintenance Menu (*FINCARS). Use this form to override the rate value of any internal rate code previously defined on the Internal Rate Maintenance Form (FCAINRT). You must define these rates before you run the billing process.
1. Enter the Project and Customer codes in the Key Information. A button and List is
available for each. Select Next Block to access the rate information fields.
2. Enter the internal Rate Code(s) that need a rate different than those defined for this
project's organization on the Internal Rate Maintenance Form (FCAINRT) and the Organization/Rate Code Maintenance Form (FTMIRTO). This is a required field.
Note These changes only affect the customer entered in the Key Information. Enter the inventory or equipment code with the internal rate code as required. The displayed base rate is the rate that is in effect as of the system date. To view rate amounts for this internal rate code for other dates, access the Internal Rate Maintenance Form (FCAINRT). This form enables you to view changes to the rate for a specific internal rate code over time. 3. The Inventory Code and Equipment Tag Number are required. 4. Enter the external rate Code. This is a required field. The system applies the amount
or % factor for this external rate code to the base rate of the internal rate code and displays it on the form as an external rate. Predefine this amount or % factor for the external rate code on the External Rate Code Maintenance Form (FTMEXRT).
5. You can enter the Effective Date or use the system date, which is the default. The
Effective Date determines when the system applies the defined external rate to the base rate. You may change the external rate for the base code, provided the Effective Date is greater than the system date.
2-340
November 2010
6. You can terminate the external rate as long as the Termination Date is greater than
the Effective Date and equal to or greater than the current date. This form emulates effective date processing without the next change date.
Entering Project Charges

There are two methods to create project charges. You can enter the units used for a cost type on the Cost Accounting Maintenance Form (FCAACCT). This creates project detail table entries. Alternatively, you can use the invoice process documents and the journal voucher process. Using the Cost Accounting Maintenance Form (FCAACCT) Access the Cost Accounting Maintenance Form (FCAACCT) from the Project/Work Order Maintenance Menu (*FINCAPC). Use this form to enter costs for a project by cost type.
1. Enter the Project code in the Key Information. The system defaults the project name.
Select Next Block to access the project charge information.

2. Enter the Cost Type. The cost type must be previously defined to the organization on
the Rate Code/Cost Type Maintenance Form (FTMRTCT). For additional information, refer to Establishing Cost Types for an Organization on page 2-345.
3. Under certain conditions, the Employee Number, Inventory Code, and Equipment
Tag Number fields are required.

Note You must set the respective Required indicator on the Rate Type Rules Maintenance Form (FTMRRUL) for all three of the fields listed above.
The Employee Number field is required when you enter a cost type associated with a direct or indirect labor rate. You must predefine the employee number on the Employee Maintenance Form (FCAEMPL). Click the button or select List for a list of valid values. Once you run the billing process, the system adds the number of units to the employee records for actual direct or indirect hours, depending upon whether the cost type is related to a labor or indirect labor rate. The Inventory Code field is required when the cost type is associated with an inventory handling rate. You must predefine the inventory code on the Inventory Code Maintenance Form (FTMINVT). Click the button or select List for a list of valid values. Once you run the billing process, the system updates the number of units you enter for this inventory item on the inventory record. The Equipment Tag number is required when you use a cost type associated with an equipment rate. You must predefine the equipment tag number on the Equipment
November 2010
2-341
Maintenance Form (FTMEQPT). Click the button or select List for a list of valid values. Once you run the billing process, the system updates the number of units you enter for the equipment on the equipment record for the projects organization.
4. Enter the number of Units to record the charge, such as the number of hours an
employee worked per week. The Units value can represent anything you can describe as a unit (for example; hours, dollars, gallons).
5. The Transaction Date defaults to the system date, but you may override it. Warning Do not enter a future date in the Transaction Date field because you may want to terminate the internal rate code during the time between the date of entry and the billing process run date. If you terminate the internal rate, the system does not create a charge. 6. Select Next Record to save the current transaction.
You can enter any one of the project detail entries repeatedly for the same transaction date or for a different transaction date. You can delete or modify each entry or any of its values until you run the billing process. After you run the billing process, the system converts the project detail entries into charges for the project and deletes them in preparation for a new billing cycle. For additional information, refer to Running the Billing Process on page 2-330. Using Journal Vouchers or Invoices You may need to track costs which occur outside of the Cost Accounting environment, such as when you pay for an item or service with the invoicing process. In order to support tracking costs for a project, both the Invoice/Credit Memo Form (FAAINVE) and the journal voucher distribution forms (FGAJVCD and FGAJVCQ) carry an enterable project code on the accounting distribution. When you enter an invoice or a journal entry for a project, you must enter the project code on the forms. The project code is carried forward from the purchase order if the invoice pays a purchase order. When you run the Posting Process (FGRACTG) for these documents, project detail entries are created for each account distribution. These table entries contain a hard coded cost type of DC, and you can view them on the Cost Accounting Maintenance Form (FCAACCT) by transaction date. You can delete or modify these project detail entries, or you can leave them as they are until you run the billing process. Prior to entering the direct charges for projects on either the invoice or journal voucher forms, you must define a cost type of DC on the Cost Type by Organization Maintenance Form (FTMCSTO). This code is associated with an internal rate code of DCGL (direct charge from general ledger). You must define this internal rate on the following forms: On the Internal Rate Code Maintenance Form (FTMINRT) to associate it to a rate type of DC.
2-342
November 2010
On the Organization/Rate Code Maintenance Form (FTMIRTO) as a valid internal rate code to use with an organization. On the Internal Rate Maintenance Form (FCAINRT) for this project's organization. This code is associated with a rate value of 1.
Establishing Rate Codes for an Organization

Use the Internal Rate Maintenance Form (FCAINRT) to define a rate value for an internal rate code. These internal rate codes maintain different rates for different periods of time. Before you can define rate values on this form, you must complete the following: Establish the rate type and rate rules on the Rate Type Rules Maintenance Form (FTMRRUL). Define an internal rate code and relate it to a rate type on the Internal Rate Code Maintenance Form (FTMINRT). Populate the Organization/Rate Code Maintenance Form (FTMIRTO) to recognize the above internal rate code, and any inventory or equipment which may relate to it, by organization.
Establishing Rate Types and Rate Rules

When you receive the test database, SunGard Higher Education provides seed data table entries for the Rate Type Cost Validation table (FTVRTYP). These rate types and rate rules are the core data the Cost Accounting module requires to run automatic rate calculations. The rate calculation indicators on the Rate Type Rules Maintenance Form (FTMRRUL) have a special meaning for each delivered rate type. On this form you can control, at a system level, whether or not to allow automatic rate calculations to occur. For example, the rate type of DL (Direct Labor) has a rate calculation indicator set to Y. You must set this indicator to Y for the automatic rate calculation process for Direct Labor to occur. Most of the rate type codes have their respective rate calculation indicators to control running the automatic rate calculation process. These rate calculation indicators will not affect any newly defined rate types. However, if you want to define rate types for use other than in automatic rate calculation, you may do so on the Rate Type Cost Maintenance Form (FTMRTYP). The indicators for employee, inventory, and equipment on the Rate Type Rules Maintenance Form (FTMRRUL) determine whether this information is required on the Cost Accounting Maintenance Form (FCAACCT) when a cost type is entered. New rate types entered on the Rate Type Code Maintenance Form (FTMRTYP) may use these required indicators. Once you associate a rate type to an internal rate code, you cannot change the rules.
November 2010
2-343
Establishing Internal Rate Codes

Internal rate codes are defined on the Internal Rate Code Maintenance Form (FTMINRT). Use this form to create an internal rate code and relate it to a rate type. For example, we define an internal rate code of DLCL, direct labor clerical and associate it to a rate type of DL, direct labor. This internal rate code must now follow the rules set for the rate type of DL. To create the internal rate code:
1. Select Insert Record and enter a descriptive four-position code in the Internal Rate
code field.
2. Enter a Short Description and a Long Description. 3. Enter a valid Rate Type. Click the button or select List for a list of valid values. 4. Click or select Save to save the internal rate code. Select Next Record to save the
internal rate code and to enter another new internal rate code.
5. You can delete an internal rate code until the point at which it is assigned to an
organization. You can modify the Short Description and Long Description at any point. Once you associate this internal rate code to an organization, you cannot change its Rate Type.
Assigning Internal Rate Codes to an Organization

Use the Organization Rate/Code Maintenance Form (FTMIRTO) to assign internal rate codes to an organization. The organization may only use these assigned internal rate codes to create charges for projects. To assign internal rate codes to an organization:
1. Enter a valid COA (Chart of Accounts) code and Organization code in the Key
Information. Click the button or select List for a list of valid values for each. Select Next Block to default the existing internal rate codes associated with the specified Chart of Accounts and Organization.
2. Enter an internal rate code in the Rate code field. Click the button or select List for a
list of valid values.This rate code must be previously defined on the Internal Rate Code Maintenance Form (FTMINRT). The system defaults the Description.
3. If the internal rate code is associated to a rate type that requires an inventory code, the
Inventory code is required. Click the button or select List for a list of valid values. To define this inventory code to the organization, use the Inventory Code Maintenance Form (FTMINVT).
2-344
November 2010
4. If the internal rate code is associated to a rate type that requires an equipment code,
the Equipment Tag code is required. Click the button or select List for a list of valid values. You must define this equipment code to the organization using the Equipment Tag Maintenance Form (FTMEQPT).
5. Select Next Record to save the table entry and assign another internal rate code.
You can delete the internal rate code, provided you do not assign a rate value to it.
Establishing Rate Values for Internal Rate Codes

Use the Internal Rate Maintenance Form (FCAINRT) to define rate values to internal rate codes for an organization. This is the final step to establish rate codes in cost accounting.
1. Enter a valid Chart of Accounts, Organization Code, internal Rate Code, and
appropriate Inventory Code or Equipment Tag No in the Key Information. Click the button or select List for a list of valid values for each of these fields. Select Next Block.
2. Enter the actual Internal Rate value to be used for the above internal rate code
combination.
3. The Effective Date is enterable and defaults to the system date. Use the Effective
Date, Termination Date, and Next Change Date fields to assign, change, or terminate the rates as desired. Since the rates may change over time, use the Effective Date functionality within this form. Once an internal rate code value is terminated you may not reactivate it. Different organizations may maintain different rate values for shared internal rate codes. For example, you may charge clerical labor rate in the accounting office at $15.00 per hour (unit), while you may charge clerical labor from the budgeting department at $14.00 per hour (unit).
Establishing Cost Types for an Organization

A cost type is similar to a job classification. Cost types enable you to record one or more rate charges for each job. To establish cost types, you must access three different forms: the Cost Type Code Maintenance Form (FTMCTYP), the Cost Type by Organization Maintenance Form (FTMCSTO), and the Rate Code by Cost Type/Organization Maintenance Form (FTMRTCT).
November 2010
2-345
The following functions are required to establish cost types: Define the cost type code itself on FTMCTYP. Define this cost type as a valid code for an organization on FTMCSTO. Associate the cost type to one or more internal rate codes on FTMRTCT.
Defining a Cost Type

Access the Cost Type Maintenance Form (FTMCTYP) from the Rate Structure Maintenance Menu (*FINCARS). Use this form to create a meaningful cost type with descriptive definitions. You can delete the cost type until it is assigned to an organization. However, you can modify the short and full descriptions at any time. For additional information about how to use the FTMCTYP form, refer to the online help.
Defining a Cost Type for an Organization

Access the Cost Type by Organization Maintenance Form (FTMCSTO) from the Organization Maintenance Menu (*FINCARD). Use this form to assign cost type codes to an organization. You may only use these cost types when you create charges for projects. You can delete a cost type as long as you do not assign an internal rate code to it on the Rate Code by Cost Type/Organization Maintenance Form (FTMRTCT). For additional information on how to use the FTMCSTO form, refer to the online help.
Assigning Internal Rate Codes to a Cost Type

Access the Rate Code by Cost Type/Organization Maintenance Form (FTMRTCT) from the Organization Maintenance Menu (*FINCARD). Use this form to define one or more internal rate codes to a cost type for an organization. This is the last requirement before you can use a cost type to charge against a project. The Effective Date defaults to the system date but may be changed. Once the code is in effect, the termination date must be greater than or equal to the system date. The Termination Date represents the last date on which you can use the code. To reactivate this code, you must make a new table entry for the same code with a new effective date that is greater than its prior termination date and greater than or equal to the system date. The only time you may delete a table entry is if the effective date is greater than the system date. You can assign more than one internal rate code to a cost type. By doing this, you have the ability to include overhead costs for a particular type of job. If you assign two internal rate codes, the system calculates two charges for this cost type: one for the overhead cost and one for the other labor type of cost. Different organizations can share internal rate codes and each can maintain different rate values. For example, you can charge clerical labor rate in the accounting office at $15.00
2-346
November 2010
per hour (unit), and you can charge clerical labor from the budgeting department at $14.00 per hour (unit).
Entering Charges From Invoices With Internal Rate Codes

If you expect to enter charges from invoices and or journal vouchers, you must make an association for a cost type of Direct Charge, DC to an internal rate code of Direct Charge General Labor, DCGL. Make this association for each organization that uses direct charges. If you do not make this association for direct charges, the billing process does not recognize a cost type of DC, and the system does not record these charges in the ledgers or in the project charges, history, or billing reports. For additional information, refer toEntering Project Charges on page 2-341.
Creating Direct and Indirect Labor Rate Codes

Use the Automatic Rate Calculation process to create or update direct and indirect labor internal rate codes with a valued rate. Use this process instead of or in addition to manual entry of the valued rates on the Internal Rate Maintenance Form (FCAINRT). The following forms and reports support this process. FTMCLAS Use the Classification Code Maintenance Form to define classifications. FTMIRTO Use the Rate Code by Organization Maintenance Form to define internal rate codes to an organization. FTMRTCL Use the Rate Code/Classification by Org Maintenance Form to define an organization's internal rate code to a classification. FOAIDEN Use the Identification Form to define employees to the system. FCAEMPL Use the Employee Maintenance Form to define employees, organizations, and classifications to the Cost Accounting module. FCAPARM Use the Cost Accounting Batch Parameter Maintenance Form to define the Batch Parameter rate process and to set the Direct Labor Rate and Indirect Labor Rate to Y. FCBLABR Use the Labor Rate Calculation Report to produce the Labor Rate Calculations Report to list the calculations of a direct or indirect labor rate for employees in an organization associated with classification code.
November 2010
2-347
Automatic Rate Calculations for Inventory Process

The following forms and reports support this process: FTMINVT Use the Inventory Code Maintenance Form to define inventory for the organization. FTMARAT Use the Rate Account Maintenance Form to define budgeted inventory accounts. FTMIRTO Use the Rate Code by Organization Maintenance Form to define internal rate codes to an organization. FCAEMPL Use the Employee Maintenance Form to define employees and to assign chart and organization. FCAPARM Use the Cost Accounting Batch Parameter Maintenance Form to define the Batch Parameter Rate process, and to set the Inventory Rate Calculations to Y. FCBINVT Run the Inventory Handling Rate Calculation Report to list the results for the inventory handling rate calculation for all employee and inventory items associated with an organization.
2-348
November 2010
Automatic Rate Calculations for Equipment Process

Use this process to automatically create or update equipment internal rate codes with a valued rate. Use this process instead of or in addition to manual entry of the valued rates on the Internal Rate Maintenance Form (FCAINRT). The following is a list of the forms and reports that support this process. FTMEQPT Use the Equipment Tag Maintenance Form to define equipment to an organization. FTMARAT Use the Rate Account Maintenance Form to define budgeted Equipment Accounts. FTMIRTO Use the Rate Code by Organization Maintenance Form to define internal rate codes to an organization.
November 2010
2-349
FCAEMPL Use the Employee Maintenance Form to define employees and to assign chart and organization. FCAPARM Use the Cost Accounting Batch Parameter Maintenance Form to define a Batch Parameter Rate process and to set the Equipment Rate Calculation to Y. FCBEQPT Run the Equipment Rental Rate Calculation Report to list the results of the equipment rental rate calculations for all employees and inventory items for an associated organization.
Automatic Rate Calculations for Material Management Process

Use this process to create or update material management internal rate codes with a valued rate. Use this process instead of or in addition to manual entry of the valued rates on the Internal Rate Maintenance Form (FCAINRT). The following is a list of the forms and reports that support this process. FTMARAT Use the Rate Account Maintenance Form to define budgeted Material Management Accounts. FTMIRTO Use the Rate Code Maintenance by Organization Form to define internal rate codes to an organization. FCAEMPL Use the Employee Maintenance Form to define employees and to assign chart and organization. FCAPARM Use the Cost Accounting Batch Parameter Maintenance Form to define a Batch Parameter Rate process and to set Material Management Rate Calculation to Y. FCBMATL Run the Material Management Rate Calculation Report to list the results of the material management rate calculation process for all employees and material management accounts associated with an organization.
2-350
November 2010
FTMARAT
FTMIRTO
FTMINRT
Does Internal Rate Code Exist?
No
Yes
FCAEMPL
FCAPARM
Yes
Run FCBMATL Report Process
Update FCBRATE table with new internal rate values.
No
Update Database?
Updates employee table's actual direct and indirect labor hours to 0.
Print FCBMATL Report
Delete batch parameter record
November 2010
2-351
Archive/Purge
The archive process copies data from the production current tables into the production archive table structure and removes the data from the production current database. Data which resides on the archive tables can be purged when outdated or no longer needed. Archive capability is provided for FGBTRNH and FGBTRND by fiscal year(s) and chart(s). The archive process can be performed in either audit mode or update mode. The database is not changed if the archive is performed in audit mode. If the archive is performed in update mode, the database will be archived. A report detailing transaction activity (FOPARCP) is available in either mode. The report will contain record counts to indicate how many records were read, how many were archived, and how many remain. Partial transaction archival may be performed for transactions which contain multiple charts on a transaction or multiple years on a transaction relative to concurrent year processing. Optional indicators can be used to include or exclude grant data or bank reconciliation data in the archive process. An exceptions indicator on the report will indicate transactions that were bypassed relative to grant data, non-reconciled checks, or partial transactions. By using optional scripts provided in the installation guide, any database changes made for a new release or interim release can be applied to the archived data.
Restore Capability
The restore process reestablishes previously archived data into the production current tables. Purged data cannot be restored. Restore capability is provided for FGBTRNH and FGBTRND by fiscal year(s) and chart(s). The restore process can be performed in either audit mode or update mode. The database is not changed if the restore process is performed in audit mode. If the restore process is performed in update mode, the archived data will be restored. A report detailing transaction activity (FOPARCR) is available in either mode. The report will contain record counts to indicate how many records were read, how many were restored, and how many remain. Partial transaction restoration may be performed for transactions which contain multiple charts on a transaction or multiple years on a transaction relative to concurrent year processing.
2-352
November 2010
Purge Capability
The purge process deletes data from the production current tables or production archive tables. Purge capability is provided for FGBTRNH and FGBTRND by fiscal year(s) and chart(s). The purge process can be performed in either audit mode or update mode. The database is not changed if the purge is performed in audit mode. If the purge is performed in update mode, the database will be purged. A report detailing transaction activity (FOPARCP) is available in either mode. The report will contain record counts to indicate how many records were read, how many were purged, and how many remain. Partial transaction purges may be performed for transactions which contain multiple charts on a transaction or multiple years on a transaction relative to concurrent year processing. Optional indicators can be used to include or exclude grant data or bank reconciliation data in the purge process. An exceptions indicator on the report will indicate transactions that were bypassed relative to grant data, non-reconciled checks, or partial transactions.
Automated Clearing House

Note For information about using Automated Clearing House to process student refunds, see the Banner Accounts Receivable User Guide.
A clearing house is a large financial institution that the Federal Deposit Insurance Corporation (FDIC) has licensed for transferring funds between banks, and other clearing houses. The clearing houses form an electronic network across the country, ensuring that financial transactions pass securely and efficiently. The network communicates using standard record formats, which are created by the National Automated Clearing House Association (NACHA). For a clearing house to pass funds from one place to another, it needs to know who is making the payments by direct deposit (that is, your institution), and who will receive the payment. In ACH terms, since you are making the payment from your bank account, you are the originator. The clearing house needs to know who your bank is, so the funds can be withdrawn from your account. Your bank is known as the immediate origin. From there, the funds can move to the clearing house, also known as the immediate destination. Lastly, the clearing house needs information on the recipient, the party who will receive the payment. You must identify the recipients name and their bank information. When you create direct deposit payments in Banner, the system will create a direct deposit file, which will contain all the information the clearing house will need to transfer the funds. You can then send the direct deposit file to your bank for processing. Banner provides a Remittance Advice feature, which enables you to print advices for the direct deposit payments.
November 2010
2-353
Standards
National Automated Clearing House Association Standards
For institutions operating in the United States, Banner formats records to the standards of the National Automated Clearing House Association (NACHA) for 1998 and 1999. These standards define the record layouts for data, including the Direct Deposit Header Label record, the Company/Batch Header record, and the File Header record. The Banner Automated Clearing House module conforms to these standards. Banner uses the CTX format, for corporate vendors, and the PPD format, for payments to individuals/students/ employees/non-corporate vendors. For a copy of the NACHA standards, please contact the NACHA as follows: National Automated Clearing House Association (NACHA) 607 Herndon Parkway, Suite 200 Herndon, VA 20170
Canadian Payment Association Standards

For institutions operating in Canada, Banner formats records to the standards of the Canadian Payment Association (CPA). Banner uses the CPA-005 credit file format, with a transaction code of 450 for all recipients of payments from the Banner Finance product. For a copy of the CPA standards, please contact your local bank.
Processing Payments by Check Only

This example illustrates how to pay Accounts Payable invoices by check.
1. Identify which vendor invoices should be paid before processing payments. Invoices
must be completed, approved, and posted.

2. To review a list of invoices for payment by date and bank code, run the Invoice
Selection Report (FARINVS). The invoices due date can be less than or equal to the payment date.
3. Use the Batch Check Print Form (FAABATC) to select the Bank Code that will be the
source of the withdrawals, and then click on the Check radio button. Do not select the other buttons: Direct Deposit or Direct Deposit & Check. Then enter the check date, the check numbers for printing, and print a test pattern for check stock alignment. When ready, select the Print Check icon.
4. Run the Batch Check Process (FABCHKS), which allows you to select invoices for
payment.
5. Run the Check Print Process (FABCHKP) process, to print the checks.
2-354
November 2010
6. Run the Check Register Process (FABCHKR) to print a register of the checks. This
will be your audit trail.

7. If you are satisfied with the quality and accuracy of the checks printed, then proceed
to Step 8. If you are not satisfied, you can rerun the check printing process by returning to Step 4 and restarting the Batch Check process. You can rerun the check printing procedure (Steps 2 through 6) as many times as needed, before running Step 8.
8. Now that you are satisfied with your checks, run the Batch Check Accounting Process
(FABCHKA) to create the cash disbursement transactions for your accounting ledgers.
9. After you have created the cash disbursements, you can post them to your ledgers by
running the Posting Program (FGRACTG).

10. Distribute checks as you normally do.
Processing Payments by Direct Deposit Only

This example illustrates how to pay Accounts Payable invoices by direct deposit.
1. Identify which vendor invoices should be paid before processing payments. Invoices
must be completed, approved, and posted.

Selection Report (FARINVS). The invoices due date can be less than or equal to the payment date. You must enter bank information for this vendor/invoice.
3. Use the Batch Check Print Form (FAABATC) to select a bank for payment, and then
click on the Direct Deposit radio button. Do not select the other buttons: Check or Direct Deposit & Check. You can then enter the check (payment) date.
4. Run the Batch Check process (FABCHKS), to select invoices for payment. The
system does this by comparing the invoices to be paid, to the date parameters you entered in Step 2.
5. If you are operating in the United States, run the Direct Deposit File Creation Process
(FAPDIRD) to create a file containing payments records that conform to NACHA standards. If you are operating in Canada, run the Canadian Direct Deposit File Creation Process (FAPCDIR), to create a file containing payment records that conform to CPA standards.
6. Run the Direct Deposit File Register Process (FAPTREG) to print a register of the
payments. This will be your audit trail of the direct deposit payments.
November 2010
2-355
7. If you would like to create advice for the payments made via direct deposit, you can
run the Batch Direct Deposit Advice Print Process (FARDIRD), and print the advice forms. You can send these forms as verification of payment to the party who received funds via direct deposit.
8. Now that you are satisfied with your direct deposit payments, run the Batch Check
Accounting Process (FABCHKA), to create the cash disbursement transactions for your accounting ledgers.
9. After you have created the cash disbursements, you can post them to your ledgers by
running the Posting Program (FGRACTG).

10. Send the Direct Deposit File to your bank or clearing house for processing. You may
want to send the Direct Deposit File Register along with the file. If you are operating in Canada, send the Canadian Direct Deposit File to your bank or clearing house for processing.
11. If you printed Direct Deposit Advice forms, you can distribute these to the
appropriate parties.
Processing Payments by Check and Direct Deposit

This process enables you to make payments using both checks and direct deposit. This option allows you to save time by not having to process check and direct deposit payments separately. This example shows you how to pay Accounts Payable invoices.
1. Identify which vendor invoices should be paid, just as you would if you were paying
by check. This is done by marking the invoices completed, approved, and then posted. Also, the Due Date for the invoice must be within the range for invoices to be paid.
Selection Report (FARINVS). The invoices due date can be less than or equal to the payment date. You must enter bank information for this vendor/invoice.
3. Use the Batch Check Print Form (FAABATC) to select a bank for payment, and then
click the Direct Deposit & Check radio button. Do not select the other buttons: Check or Direct Deposit. You can then enter the check date, the check numbers for printing.
4. Run the Batch Check Process (FABCHKS), which allows you to select invoices for
payment. The system does this by reviewing the invoices to be paid, to the date parameters you entered in Step 2.
5. Run the FABCHKP process to print the checks.
2-356
November 2010
Interfaces
This chapter details the interfaces from other Banner systems to the Banner Finance System. Information in this chapter also explains the application forms, rule forms, reports, and processes used in the interface between the Banner Human Resources and Banner Finance Systems. It contains detailed process flowcharts and step-by-step procedure checklists, and includes detailed instructions for performing interfaced budget and payroll transactions. Because this section is presented primarily from the perspective of the Banner Human Resources user, there is limited explanation of the feeds after they hit the Banner Finance System. Following is a high-level summary of the types of information included in this section: Banner Human Resources/Finance Interface Flow Summary provides a visual representation of the data flow between Banner Human Resources and Banner Finance. The HR/Finance Set Up Rules Form (NTRFINI) provides detailed instructions for completing the form that sets up the Banner Human Resources/Finance interface. Establishing and Feeding Original Budgets lists the rule forms, application forms, batch processes, and the process flow required to set up and feed original salary and fringe budgets in Banner. Budget Modeling specifies the rule forms, application forms, batch processes, and process flow that prepare the system for the establishment and feeds of budget models. Processing Wage/Salary Adjustments specifies the rule/application forms and batch processes necessary to update employee salary and wage information, update encumbrances, and feed encumbrances to Banner Finance. Approving Working Budgets explains the process for approving a working budget. Feeding Payroll Transactions provides procedures for feeding payroll transactions. Processing COBRA Transactions provides information on the Banner Human Resources/Finance COBRA Interface. Installments/Feed to Banner Finance provides a procedure for ensuring that payroll deductions fed from Banner Human Resources and Banner Advancement are not duplicated.
November 2010
Banner Finance 8.5 User Guide Interfaces
3-1
Banner Human Resources/Finance Interface Flow Summary

PHPFEXP
NHRFINC
A B C D E F G H I J
Earnings Employee Liability Net Payroll Employer Ben. Exp. Employer Liability Defer Pay Hold Defer Pay Payout Frng. C Back Exp. Frng. C B Clearing Frng. Actual Clearing Do not create transaction
Yes
NHPFIN1
K L M N O P Q R S T U Original Budget Budget Adjustments Original Fringe Budget Fringe Budget Adj. Salary Encum. Orig. Encum. Salaries Adj. Encum. Frng Chgbk Orig Encum. Frng. Chgbk. Adj. COBRA Cash COBRA Premium COBRA Admin. Fee No
Does the NTRFINI Update Budget Indicator = NH and the PTOT/FTOT Status = W ?
3-2
November 2010
HR/Finance Set up Rules Form (NTRFINI)

Before you can use the interface with Banner Finance, you must define interface transaction rules on the HR/Finance Set up Rules Form (NTRFINI). NTRFINI establishes interface rules, defines the accounting distribution for net pay and deferred pay, and validates rule class codes against the Finance System Rule Class Code Form (FTMRUCL).
Note This chapter discusses only the version of NTRFINI that appears when Banner Finance is installed.
November 2010
3-3
To establish the rules governing your HR/Finance interface, perform the following steps:
1. Access NTRFINI. All defined records are retrieved. (This requires a brief delay in
processing).
2. At Fiscal Year, enter the fiscal year for which you are setting up an interface to
Finance. The value you enter must be predefined on the Fiscal Year Form (NBAFISC). The system displays the year's start and end dates in the From and To fields. Once this form is completed for the first time, you can use the Copy Year function from this field to copy the data to ensuing fiscal years.
3. The COA field displays the Chart of Accounts code to be applied to the labor
distributions found on the Distribution Information Window. This field takes its default value from the Fiscal Year Form (NBAFISC).
4. The fiscal year's active status is displayed in the Active check box. If it is selected,
the fiscal year shown is the currently active fiscal year as defined on NBAFISC. If it is not selected, this year is not the currently active fiscal year.
5. At Finance Fiscal Year, enter the Finance System fiscal year for which you are
setting up the interface. If Banner Finance is installed, the value you enter must be predefined on the Finance Fiscal Year Form (FTMFSYR). The system displays the year's start and end dates in the From and To fields. Note that the end date should match the one that appears for the Banner Human Resources fiscal year in Step 2.
6. At Bank, enter the code of the bank you use to issue payroll checks and direct
deposits. The value you enter in this field must be predefined on the Bank Code Maintenance Form (GXRBANK).
7. Set the Feed Budget to Finance Budget Development check box as follows:
Selected
Update the Banner Finance Budget Development module with all original and adjusted budget entries (for both working and active salary and fringe budgets). Do not feed original and adjusted salary and fringe budgets to the Banner Finance Budget Development module. Active budgets (original and adjusted) are fed to the operating ledger with the Payroll system's ID.
Unselected
8. Use the Next Item function to move to the Finance Rule Class Code fields. For each
field, enter the Banner Finance System rule class code the system should use for validation. The codes you enter must be predefined on the Banner Finance System's Rule Class Code Maintenance Form (FTMRUCL).
9. Save. The system saves your new or revised rules.
3-4
November 2010
Distribution Information Window

The Distribution Information window displays the accounting distributions that control the processing of Human Resource accounting transactions. Perform the following steps:
1. At Net Distribution, indicate the Index and FOAPAL (Fund, Orgn, Account,
Program, Activity and Location) distribution to be used in the interface. If you want to default the FOAPAL components, enter a Banner Finance Index code at the Index field. The Net Distribution fields should be blank except for Fund which contains your bank fund, and Account which contains the general ledger account code of your Payroll Clearing Account. The sample data delivered with your Banner Human Resources application includes a Payroll Clearing Account value of 1060. This value corresponds to the posting modifier set up in your Banner Human Resources System rule classes on FTMRUCL. (If you do not want to use 1060, the Account Maintenance Form (FTMACCT) can be used to establish an equivalent account code for your institution. If you use a value other than 1060, you must also change the posting modifier on your Banner Human Resources rules classes on FTMRUCL to reflect your new Payroll Clearing Account value.)
2. At Deferred Pay, indicate the FOAPAL (Index, Fund, Orgn, Account, Program,
Activity, and Location) deferred pay distribution to be used in the interface. If you want to default the FOAPAL components, enter a Banner Finance Index code at the Index field. The Deferred Pay fields should be blank except for Fund and Account, which contain the fund and account used for the accrual of deferred pay liability. Use the Fund Code Maintenance Form (FTMFUND) and the Account Code Maintenance Form (FTMACCT) to establish the appropriate fund and account for this purpose.
3. At Fringe Clearing, enter the accounting distribution (fund and account) where the
actual fringe expense will be debited and the fringe chargeback amount will be credited.
Fringe Chargeback Rules Window

The Fringe Chargeback Rules window collects fringe chargeback data for use in the interface.
1. At Matching FOAPAL Components, specify which components of the FOAPAL
are to be considered in the matching of external funding sources. The values you enter in these fields will guide the fringe encumbrance and expense process. For each
November 2010
3-5
component (Fund, Orgn, Account, Program, Activity, and Location), select the box for Yes or leave it unselected for No.
2. When you run your payroll, NBPBUDM and PHPFEXP use the values entered at
Calculate or Process Fringe Encumbrances Fringe Calculation Method, and Override External Rate with Installation Rate? to determine how to encumber, liquidate encumbrances, and expense fringe benefits.
3. Go to the Recalculate All Salary or Fringe Encumbrances? box. When you make
changes for this fiscal year to the Fringe Rate Definition and Labor Distribution Override Rule Form (NTRFBLD), this field is updated to checked status (that is, to Yes). The next time NBPBUDM is run, it looks at this indicator and recalculates all encumbrance values. If NBPBUDM is run in process mode, it resets the indicator to unselected status (that is, to No).
Establishing and Feeding Original Budgets

Budgets establish guidelines to assist in managing fiscal responsibilities and ensuring solvency. One of the largest budget items is labor, which encompasses salaries/wages and fringe benefits. Before you initiate a labor budget, you must complete the forms outlined below. In addition, you must run batch jobs to post original budget transactions to Banner Finance.
Rule Forms
Before you enter position data into the Banner Human Resources System, you must complete several rule forms in the Banner Finance and Human Resources Systems. The forms that impact your ability to establish and feed original labor budgets are listed below.
Note Some of the data defined on the following forms is predefined as Banner Finance sample data.
Banner Finance
You must complete the following Banner Finance forms:
FTMCOAS FTMFUND
Establishes the Chart of Accounts for the installation. Establishes valid funds for labor expenditures. A fund is defined, in layperson's terms, as balance sheet items (assets, liabilities, equity). Funds can be restricted (for example, grants) or unrestricted (for example, general).
3-6
November 2010
FTMORGN FTMACCT
Establishes valid organizations for labor expenditures. An organization represents a department within the installation. Establishes valid accounts for labor expenditures. Accounts are line items within a site's financial structure. They include general ledger accounts (assets and liabilities) and operating ledger accounts (revenues and expenses). Establishes valid programs for labor expenditures. Programs enable you to define a method of pulling transactions across organizations and accounts. Examples include instruction, research, and plant operations. Most educational institutions use programs defined by the National Association of College and University Business Offices (NACUBO). Establishes valid activities for labor expenditures. An activity is an accounting element for use in tracking non-budget control financial affairs. An example of an activity is the YMCA's use of your site's pool to teach lifesaving. Establishes valid locations. Locations represent a building and room number. Establishes the system ID as PAYROLL. The PAYROLL system ID feeds payroll, encumbrance, budget, and COBRA transactions to the operating ledgers via the FURFEED process. (The PAYROLL ID is included as part of the Banner Finance seed data.) Defines the fiscal year and fiscal periods. Establishes valid budget phases within budget IDs for budget development purposes. Defines valid Banner Finance System rule class codes that identify the journal type being maintained for transactions from Banner Human Resources. These defined rule classes are used on the HR/Finance Setup Form (NTRFINI).
FTMPROG
FTMACTV
FTMLOCN FTMSDAT
FTMFSYR FTMOBUD FTMRUCL
Note When editing is performed against general ledger accounts, only a fund and account are required. When editing is performed against operating ledger accounts, you must enter the fund, organization, account, and program. Activity and location are always optional entries in Banner Human Resources and Finance.
November 2010
3-7
Banner Human Resources

When the Banner Human Resources System is first implemented, the following rule forms must be completed prior to the building of the Position Definition Form (NBAPOSN) and the Position Budget Form (NBAPBUD). Data contained in specific fields on these rule forms drives certain batch processes in the budget roll process. The following rule forms must be completed:
NTRFBLD
Contains three windows for entering fringe rate information. The Fringe Labor Distribution Override block in the main window is used for entering the installation fringe rate by employee class and the labor distribution override data for internal fringe benefits. The next two windows provide information on external fringe benefits. The External Funding Source Fringe Rate Definition Window is used for entering the external funding source fringe rate labor distributions on which the system is to match when performing labor distribution overrides for external fringe benefits. (The system obtains the rules for the match from the NTRFINI rule form.) The External Fringe Labor Distribution Override Window is used for entering an overriding labor distribution by employee class for each matching FOAPAL from the External Funding Source Fringe Rate Definition Window.
3-8
November 2010
NTRFINI
Uses predefined rule class codes from FTMRUCL in the Banner Finance System for Banner Human Resources transactions. It influences accounting distribution for such items as salary expense, employee/employer liabilities, net pay, deferred pay, and COBRA. It is important to take note of the Feed Budget to Finance Budget Development check box on NTRFINI and the contents of the Status field on the Position Salary Budgets Window of the Position Budget Form (NBAPBUD). If the NTRFINI Feed Budget to Finance Budget Development check box is selected and the NBAPBUD Status field is set to Approved, original budgets, budget adjustments, original fringe budgets, and fringe budget adjustments are passed to the Budget Development module in Banner Finance (as POSNBUD transactions) and to the live ledgers in Banner Finance (as PAYROLL transactions). If the NTRFINI Feed Budget to Finance Budget Development check box is not selected, these transaction types are posted only to the live ledgers, regardless of the contents of the NBAPBUD Status field. If the NBAPBUD Status field is set to Working, the transactions are passed only to the Budget Development module, regardless of the setting of the NTRFINI Feed Budget to Finance Budget Development check box.
Banner Position Control
NTRSGRP NTRSALA NTRBROL NTRFRNG
Specifies the active salary group code for each salary table (defined on NTRSALA). Establishes the salary ranges and/or steps for each salary group, salary table, and grade. Establishes step increases/decreases by employee class for use in budgeting salaries/wages in the budget roll process. Collects parameters for use in budgeting fringe benefit costs in the budget roll process.
November 2010
3-9
Application Forms
The following application forms are used to enable Banner's position budgeting features and to create and maintain position budgeting information.
NBAFISC NBAPOSN NBAPBUD
Defines the parameters of the fiscal year. Fiscal year begin and end dates default from the FTMFSYR form in Banner Finance. Defines and maintains all positions from a Banner Human Resources perspective. Defines position totals, fringe totals, and position labor distributions. It provides the ability to monitor position expenditures versus budgeted amounts, allows you to perform budget modeling via budget ID and phase, and displays expended and remaining fringe benefit totals. Organizational budget transfers are also initiated on this form. When creating a new position budget, you must enter a Budget ID and Phase in the Position Totals block for proper feed to the Budget Development module. This form's Budget Roll Indicator determines the amounts used in the Banner Human Resources budget roll process.
NBAJOBS
Contains salary, salary encumbrance, and fringe encumbrance information that (depending on the NBAPBUD Budget Roll Indicator value) may be used in the budgeting and encumbering processes.
Batch Processes
By reading position budgeting records, the following batch processes determine if there are original budgets or NBAPBUD position-total adjustments/changes that have not been interfaced to Banner Finance.
3-10
November 2010
NHPFIN1
Extracts data for budgeting (and for budget modeling, encumbrances, and COBRA payments) for the Banner Finance interface. This process generates budget transactions and inserts records into NHRFINC. Original budgets, budget adjustments, original fringe budgets, and fringe budget adjustments are passed to the Budget Development module in Banner Finance (as POSNBUD transactions) and to the live ledgers in Banner Finance (as PAYROLL transactions) if the Feed Budget to Finance Budget Development box on NTRFINI is selected. If the Feed Budget to Finance Budget Development box is not selected, these transaction types are posted only to the live ledgers (as PAYROLL transactions). In either case, only budgets in approved status are passed to the live ledgers. Salary encumbrances and COBRA transactions are posted only to the live ledgers. All of these transactions are passed to Banner Finance via NHPFIN2. Parameters include the following: COBRA Processing (Y/N) Budget Processing (Y/N) Encumbrance Processing (Y/N)
NHPFIN2
Extracts the budget transactions from the NHRFINC table and inserts them into the GURFEED table. GURFEED is a collector table through which all interfacing transactions to the Banner Finance System are passed. Parameters include the following: Detail Report (Y/N) Interface (Y/N) Transactions to GURFEED As noted above, if the NTRFINI Feed Budget to Finance Budget Development box is selected, any changes to the Budgeted Amount field of the NBAPBUD Position Total block are flagged for concurrent interface to the Budget Development module and the Operating Ledgers. You must then submit the following process to feed to the Budget Development module. This step must be performed before you submit processes to feed transactions to the Banner Finance live ledgers.
November 2010
3-11
FBRFEED
Selects budget transactions from GURFEED when the System ID is POSNBUD and creates and/or updates records to insert in to the Budget Development area of Banner Finance. The program actually creates/updates FBBBLIN records, which is the Budgeted Line Item Table in Banner Finance. This table contains annualized amounts. This program must be run only if the Feed Budget to Finance Budget Development check box on NTRFINI is selected and the System ID is POSNBUD.
To post the transactions to the live ledgers, submit the following processes: FURFEED Selects records from GURFEED when the System ID is PAYROLL. It then creates and/or updates records to insert into the Finance Interface Table (FGBTRNI) and updates the Banner Finance ledgers. Edits the documents (journal vouchers) and inserts the approved documents into the Approved Documents Table (FOBAPPD). Produces an error report that displays the system edits of suspended documents from the FGRTRNI process. Selects approved documents from the FGRTRNI process and posts the transactions to the ledgers in the Banner Finance System. If the NTRFINI Feed Budget to Finance Budget Development box is not selected, changes to the Budgeted Amount field in the Position Total block of NBAPBUD will be flagged for interface only to the Operating Ledgers in the Banner Finance System. Thus, you should not run FBRFEED and should run only FURFEED, FGRTRNI, FGRTRNR, and FGRACTG.
FGRTRNI
FGRTRNR FGRACTG
Process Flow
1. Complete all rule and application forms described above. 2. For original budget processing, only forms up to and including NBAPOSN and
NBAPBUD must be completed to place a recently created (but not filled) position in the budget module.
3. Once an employee is hired to fill the position and an actual salary is known, you may
choose to adjust the original budget on NBAPBUD to reflect the salary of the new incumbent and to post the encumbrance to Banner Finance and to the NBAPBUD Position Total block. Encumbrances must be posted to Banner Finance before feeding payroll transactions to Banner Finance.
3-12
November 2010
4. Run the following batch programs to feed budgets and budget adjustments to Banner
Finance.
Process
Comments/Special Instructions
NHPFIN1 NHPFIN2
Enter Y for the Budget Processing parameter. Do not enter a parameter value for Expenditure Payroll Id. The Expenditure Payroll Id parameter does not appear if no Payroll expenditure transactions exist.)
FBRFEED FURFEED FGRTRNI FGRTRNR FGRACTG
Only if NTRFINI Feed Budget to Finance Budget Development box is selected.
Budget Maintenance Checklist: Establishing and Feeding Original Budgets

Step Form Or Process Description
1 2
NTRFINI NTRFRNG or NTRFBLD
Verify criteria for Fringe Budgeting. Establish criteria for the computation of original fringe budgets for filled and vacant positions under the actual method. Establish criteria for the computation of original fringe budgets based on salary budget under the charge back method.
3 4 5
NBAPOSN NBAPBUD NBPBUDM (Charge Back Method only)
Define position (budgeted entity). Define position salary budget, premium earnings budget, and position labor distribution. Run process using the Budget Processing option. Specify processing of Active budgets. Calculates fringe budget amounts under the charge back method.
November 2010
3-13
Step
Form Or Process
Description
NHPFIN1
Run process using the Budget Processing option. Extracts data for original budgets for the Banner Finance Interface based on COA, Fiscal Year, Budget ID and Budget Phase. Generates Budget transactions for original budgets and inserts records into NHRFINC. Run process to extract original budget transactions from the NHRFINC table. Optionally inserts records into GURFEED (collector table), Run desired Banner Position Control reports. Run Banner Finance processes to post to Operating Ledgers in Banner Finance after NHPFIN2 has been used to populate the GURFEED table: FBRFEED, FURFEED, FGRTRNI, FGRTRNR, and FGRACTG.
NHPFIN2
8 9
Various Finance Feed
The following diagram illustrates the flow for establishing and feeding original budgets.
3-14
November 2010
November 2010
3-15
Budget Modeling
Banner Position Control and Budgeting provides an avenue for wage/salary and fringe budgeting for specified fiscal years. A variety of options enable you to create what-if scenarios on proposed budget adjustments to salaries and fringe benefits.
3-16
November 2010
Each created model can then be fed to the Budget Development module within the Banner Finance System to be included in overall Budget Development. To prepare the system for budget modeling, you must complete the forms outlined below. Once budgets have been created, several batch processes must be run to feed the budget transactions to Banner Finance.
Rule Forms
By the time you are ready to do budget modeling, you should already have completed the Banner Finance and Human Resources rule/control forms listed under Establishing and Feeding Original Budgets. They are repeated below for your convenience. Additional required forms are explained below under Banner Position Control on page 3-18.
Banner Finance
FTMCOAS FTMFUND
Establishes the Chart of Accounts for the installation Establishes valid funds for labor expenditures. A fund is defined, in layperson's terms, as balance sheet items (assets, liabilities, equity). Funds can be restricted (e.g., grants) or unrestricted (for example, general). Establishes valid organizations for labor expenditures. An organization represents a department within the installation. Establishes valid accounts for labor expenditures. Accounts are line items within a site's financial structure. They include general ledger accounts (assets and liabilities) and operating ledger accounts (revenues and expenses). Establishes valid programs for labor expenditures. Programs enable you to define a method of pulling transactions across organizations and accounts. Most educational institutions use programs defined by NACUBO (for example, Instruction). Establishes valid activities for labor expenditures. An example of an activity is a number assigned to the YMCA for using your site's pool to teach lifesaving. Establishes valid locations. Locations represent a building and room number.
FTMORGN FTMACCT
FTMPROG
FTMACTV
FTMLOCN
November 2010
3-17
FTMSDAT
Establishes the system ID as PAYROLL or POSNBUD. The PAYROLL system ID feeds payroll, encumbrance, budget, and COBRA transactions to the operating ledgers via the FURFEED process. The POSNBUD system ID feeds budget transactions to the Budget Development module via the FURFEED process. Both the PAYROLL and POSNBUD IDs are included as part of the Banner Finance seed data. Defines the fiscal year and fiscal periods. Establishes valid budget phases within budget IDs for budget development purposes. Defines valid Banner Finance System rule class codes that identify the journal type being maintained for transactions from Banner Human Resources. These defined rule classes are used on the HR/Finance Set up Rules Form (NTRFINI).
Note When editing is performed against general ledger accounts, only a fund and account are required. When editing is performed against operating ledger accounts, you must enter the fund, organization, account, and program. Activity and location are always optional entries in Banner Human Resources.
NTRSGRP NTRSALA NTRPCLS
Specifies the active salary group code for each salary table (defined on NTRSALA). Establishes the salary ranges and/or steps for each salary table and grade. Creates and associates position classes with employee classes, employee skill levels, position groups, and salary/wage ranges. Establishes the parameters used in the mass salary update process (NBPMASS) to roll data from one salary group to another.
NTRSTRL
3-18
November 2010
NTRBROL
Provides parameters for rolling the current Banner Human Resources budget into the new fiscal year. Users must complete this parameter form, which determines how budgets are computed for the Banner Human Resources budget roll/ budget modeling process. You may choose to increase or decrease the base budget amounts (defined for each employee class in NBAPBUD) to be used in the Banner Human Resources budget roll process by a specified percentage on this rule form. Enables you to define rules for calculating fringe budgets, encumbrances, and fringe expenses. This functionality is used when you choose to "charge back" accounts based on a percent versus the actual amount. It allows for the definition of installation fringe rates and external funding source fringe rates. It also contains the overriding labor distributions used for posting fringe amounts based on earnings defined when the fringe indicator on the Earnings Code Rule Form (PTREARN) is set to Yes. Enables you to establish budgets for fringe benefits that have employer contributions. These parameters are specified by employee class, deduction, and plan code and can be entered in terms of percentages or flat amounts. The Budget Indicator on this rule form determines how fringe budgets are calculated and what type of fringe calculations are performed in the budget roll process.
NTRFBLD
NTRFRNG
November 2010
3-19
NTRFINI
Uses predefined rule class codes from the FTMRUCL form in the Banner Finance System for Banner Position Control and Payroll transactions. It determines accounting distributions for such items as salary expense, employee/employer liabilities, net pay, deferred pay, COBRA, and so on. It is important to take note of the Feed Budget to Finance Budget Development check box. When this box is selected, budget transactions will continue to be interfaced to the Budget Development module of the Banner Finance System (as well as to the operating ledgers) after the position budgets have been approved in the Banner Position Control module. This enables the budget development area to stay in sync with the Banner Position Control module. Please keep in mind that data transferred to the Banner Finance System from the Banner Position Control module always posts to the operating ledgers. Only when the Feed Budget to Finance Budget Development check box is selected will the budget transactions also post to the Budget Development area of Banner Finance.
Application Forms
The following application forms enable you to use the budget modeling features of Banner.
NBAFISC NBAPOSN
Defines the parameters of the fiscal year. Fiscal year begin and end dates default from the FTMFSYR form in Banner Finance. Defines and maintains all positions (budgeted entities).
3-20
November 2010
NBAPBUD
Defines position totals, fringe totals, and position labor distributions. It provides the ability to monitor position expenditures versus budgeted amounts, allows you to perform budget modeling via budget ID and phase, and displays expended and remaining fringe benefit totals. Organizational budget transfers are also initiated on this form. When creating a new position budget, you must enter a Budget ID and Phase in the Position Totals block for proper feed to the Budget Development module. To roll budgets to future fiscal periods, choose from the following budget roll options by employee class. Current Budget Range Midpoint Roll current budgeted amounts, plus or minus the employee class increase/decrease parameter. Roll the salary range midpoint times the position appointment percent times the greater of the following: the number of budgeted FTE or the number of incumbent FTE The salary range midpoint reflects probable salary/rate and may not be the mathematical midpoint of the range. Remaining Budget Zero Roll the remaining budget amount. Roll a zero amount (for zero-based budgeting).
November 2010
3-21
Current Salary
Roll: The sum of annual salaries for NBAJOBS records that have a step equal to zero The sum of step value in the new/specified salary group for NBAJOBS records that have a step greater than zero and a salary indicator of S for the table/ grade/step combination associated with the job The sum of the annualized step values in the new/specified salary group for NBAJOBS records with a step greater that zero and an NTRSALA salary indicator of H for the table/grade/step combination associated with the job Vacant positions use the Range Midpoint method and job appointment percent is applied to 2 and 3 above. Positions selected must have active or frozen status and cannot have end dates prior to the new fiscal year.
Current Encumbrance
Roll the sum of all active salary encumbrances, plus or minus the employee class increase/decrease parameter. For vacant positions, the Range Midpoint method is used.
Actual Expenditure
Payment money that has been allocated for a position. The actual expenditure for the position total for the current year.
If Current Salary or Current Encumbrance is chosen, vacant positions will be rolled using the Range Midpoint of the salary table and grade assigned to each position on NBAPOSN multiplied by the number of vacant FTEs. NBAJOBS Contains salary and salary encumbrance information that (depending on the budget roll indicator value used in PTRECLS) may be used in the budgeting and encumbering processes.
3-22
November 2010
General Person
PPAIDEN
Provides a person's initial point of entry into the system and identifies basic biographic and demographic data on applicants, employees, beneficiaries, and COBRA persons/ dependents/beneficiaries.
PEAEMPL
Establishes basic employee information such as status, leave balances, review dates, termination and leave dates, etc. This form must be completed prior to NBAJOBS. Establishes deductions and contributions for benefits and taxes, and employee specified withholdings. These records may be used when creating fringe budgets for filled positions.
PDADEDN
Batch Processes
The following batch processes will be run to prepare the system for the actual budget modeling process.
Banner Finance
FBRBDBB
Rolls budget from the current year's Operating Ledger to the initial budget phase or from phase to phase.
NBPMASS
Posts changes to NBAJOBS, calculates automatic step increases (and posts changes to NBAJOBS if desired), and updates NTRSALA table entries by a percent or amount.
November 2010
3-23
For budget modeling, NBPMASS must be run prior to the Budget Roll Process to create new salary table entries on NTRSALA for the new salary group being entered as a parameter on NBPBROL. Parameters for this job are: Report or Process P (Process) Process Type U (Update table/grade steps) Salary Group to roll from New Salary Group to roll to Select the Process Type U and enter remaining parameters as prompted. The following batch process reads the parameters established on NTRBROL and NTRFRNG and actually creates each requested budget model
NBPBROL
Allows you to perform the following: Roll current position and fringe budgets (using Actual Method) to proposed position and fringe budgets (in working status) to single or multiple budget phases (explained in this section) Roll the adopted position and fringe budgets to approved status for the new fiscal year (see Approving Working Budgets on page 3-38). Delete the working budgets no longer needed (see Approving Working Budgets on page 3-38). Results of this process are posted to the Position Totals block of NBAPBUD.
3-24
November 2010
You can overwrite a previously-used Budget ID and Phase. Parameters include the following: Report Choice: Roll Budgets to Working Status Roll Working Budgets to Approved Status Delete Working Budgets No Longer Needed Chart of Accounts Code New Fiscal Year Current Fiscal Year Budget ID Budget Phase Salary Group Code The batch processes below read position budgeting records to determine if there are original budgets or adjustments/changes to position total records on NBAPBUD that have not been interfaced to Banner Finance.
NHPFIN1
Extracts data for budget models (and for position budgeting, encumbrances and COBRA payments) for the Banner Finance Interface. This process generates budget transactions for the new working budgets and inserts records into NHRFINC. They are then passed through to the Budget Development module in Banner Finance. Parameters include the following: COBRA Processing (Y/N) Budget Processing (Y/N) Encumbrance Processing (Y/N)
November 2010
3-25
NHPFIN2
Extracts the budget transactions from the NHRFINC table and inserts them into the GURFEED table.
Note: GURFEED is a collector table through which all interfacing transactions to the Banner Finance System are passed.
Parameters include the following: Detail Report (Y/N) Interface (Y/N) Pay ID FBRFEED Selects budget transactions off GURFEED and creates and/or updates records to insert in to the Budget Development area of Banner Finance. The program actually creates/updates FBBBLIN records, which is the Budgeted Line Item Table in Banner Finance. This table contains annualized amounts.
Reports
NBRBWRK Produces a budget worksheet for salary budget modeling. Parameters include the following: COA Code Previous Fiscal Year Proposed Fiscal Year Budget ID Budget Phase Average Percent Raise
Process Flow
1. Complete the rule and application forms described above. Take special note of the
following: If you are rolling salary and fringe budgets based on budgeted amounts, median of salary, range, or zero amount, only NBAPOSN and NBAPBUD must be completed. If you are rolling salary and fringe budgets based on remaining budgets, actual annual salaries, or salary encumbrances, NBAPOSN, NBAPBUD, PPAIDEN, PEAEMPL, and NBAJOBS must be completed.
3-26
November 2010
PDADEDN must be completed if you wish to base fringe budgets on actual deduction records.
2. Ensure you have the new fiscal year defined on NBAFISC. The current year should
have a selected Active check box. The Active check box for all other fiscal years should not be selected.
3. Complete the NTRSGRP rule form. Ensure that all salary tables on NTRSALA are
represented on NTRSGRP for the new salary group code.

4. Establish the budget roll parameters for salary (NTRBROL) and fringe (NTRFRNG
and NTRFBLD) budgeting.

5. Run the following batch processes as noted. Process Name Comments/Special Instructions
NBPMASS
Process Type = U. You must have already completed NTRSGRP with a new salary group code. Complete NTRSTRL, specifying how each salary table is to be rolled.
NBPBUDM NTRBROL NBPBUDM NBRBWRK (Optional) Enter N in the Current Budget parameter and complete the remaining parameters. Enter R in the Report Choice parameter and complete the remaining parameters.
6. (Optional) Make manual adjustments to the Position Total block of NBAPBUD to
handle exceptions to the mass roll process.

7. (Optional) To feed the budget model to the Budget Development module, run the
following processes:
Process Name
NHPFIN1 NHPFIN2 FBRFEED
Enter Y for Budget Processing. Enter parameters as desired. Enter parameters as desired.
8. (Optional) Produce an additional model or models.
November 2010
3-27
Budget Maintenance Checklist: Budget Modeling

1 2 3 4 5 6 7
NBAFISC NTRSGRP NTRSTRL NBPMASS NTRBROL NTRFINI NTRFRNG or NTRFBLD
Establish new Fiscal Year. Establish new Salary Groups for all existing salary tables. Establish criteria for updating pay plans/salary tables on NTRSALA. Run process using the U (update table/grade/step) option. Establish criteria for rolling salary budgets as well as premium earnings budgets. Verify criteria that determines Fringe Budgeting. Establish/verify criteria for rolling fringe budgets for filled and vacant positions under the actual method. Establish/verify criteria for rolling fringe budgets based on salary budget under the charge back method.
NBPBROL
Run process using the R (roll a budget) option. Rolls new salary, premium earning, and fringe budgets (under the actual method) into working status. Run the process using the Budget Processing option. Specify working budgets, COA, Fiscal Year, Budget ID, and Budget Phase for the working budgets being calculated. Calculates fringe budget amounts under the charge back method. Run the process using the Budget Processing option. Extracts data for working budgets for the Banner Finance Interface based on COA, Fiscal Year, Budget ID, and Budget Phase. Inserts working budget transaction records into NHRFINC. Run the process to extract working budget transactions from the NHRFINC table. Optionally inserts transactions into GURFEED (collector table).
NBPBUDM (Charge Back Method only)
10
NHPFIN1
11
NHPFIN2
3-28
November 2010
Step
Form Or Process
Description
12 13
Run desired Banner Position Control reports. Run Banner Finance Processes to post to Budget Development in Banner Finance after NHPFIN2 has been used to populate the GURFEED table. (FBRFEED)
The following diagrams show the flow for Budget Modeling.

Finance Rule Forms Human Resources Rule Forms PTRECLS PTRBDCA FTMCOAS FTMSDAT FTMACCT FTMOBUD FTMLOCN FTMORGN FTMRUCL FTMACTV FTMFUND FTMFSYR FTMPROG
Position Control Rule Forms NTRBROL NTRFRNG NTRSTRL NTRSALA NTRSCRP NTRFINI
Prerequisite Application Forms NBAFISC NBAPOSN NBAPBUD PDADEDN PPAIDEN PEAEMPL NBAJOBS
Batch Process Finance FBRBDBB
Batch Process Position Control NBPMASS NBPBUDM NBPBROL
November 2010
3-29
Processing Wage/Salary Adjustments

The mass processing of wage and/or salary adjustments typically occurs after budgets are determined for the new year. Through the use of rule forms and batch processes, the system creates new jobs records reflecting increases/decreases to current job records by salary table and posts resulting changes in encumbrances to the Banner Finance System. When an employee is assigned to a specific assignment (or job), a salary encumbrance for the fiscal year is calculated (or entered, depending on the rules established on PTRECLS) on NBAJOBS. This salary encumbrance is the value of the encumbrance which is posted to the Banner Finance System and to the Position Total block of the Position Budget Form
3-30
November 2010
(NBAPBUD) through batch processes explained in this section. Organizational budget transfers and budget adjustments (on NBAPBUD) and certain changes made to NBAJOBS are reflected in the same manner.
Rule Forms
NTRSGRP NTRSALA NTRJINC NTRHROL NTRCROL
Specifies the active salary group code for each salary table (defined on NTRSALA). Establishes the salary ranges and/or steps for each salary group, table, and grade. Establishes parameters used in the Mass Salary Update Process (NBPMASS) to implement step and salary increases. Establishes parameters used in Mass Salary Update Process (NBPMASS) to update encumbrance hours. Establishes parameters used in Mass Salary Update Process (NBPMASS) to update contract start/end dates.
Application Forms
NBAJOBS Contains salary and salary encumbrance information by assigned job(s) per employee. The current step and rates from each job record will be used in the mass salary/wage adjustment process.
Note Completion of NBAPOSN, NBAPBUD, PPAIDEN, and PEAEMPL is necessary before a job can be assigned to an employee on NBAJOBS.
Batch Processes
The following batch processes apply the rules established in NTRJINC to create new job records reflecting increased/decreased wages/salaries, update encumbrances, and feed the new encumbrances to Banner Finance.
November 2010
3-31
NBPMASS
Posts changes to NBAJOBS, calculates automatic step increases (and posts changes to NBAJOBS if desired), and updates NTRSALA table entries by a percent or amount. Parameters include the following: Report or Process P (Process) Process Type J (Update job records) Salary Group to use Job Change Reason Code Personnel Change Date Use Population Selection (Y/N) Selection ID (Y only) Creator ID (Y only) Application (Y only) To process mass salary changes, select Process Type J.
NHPFIN1
Extracts data for encumbrances (and for budgeting, budget modeling, and COBRA transactions) for the Banner Finance Interface. This process generates encumbrance transactions and inserts records into NHRFINC. They are then passed through to the Banner Finance System by NHPFIN2. Parameters include the following: COBRA Processing (Y/N) Budget Processing (Y/N) Encumbrance Processing (Y/N)
NHPFIN2
Extracts the budget transactions from the NHRFINC table and inserts them into the GURFEED table. GURFEED is a collector table through which all interfacing transactions to the Banner Finance System are passed. Parameters include the following: Detail Report (Y/N) Interface (Y/N) Pay ID
3-32
November 2010
If you have made manual adjustments to the budgeted amounts as a result of the mass salary process, it may be desirable to send the budget adjustments to Banner Finance. If the NTRFINI Feed Budget to Finance Budget Development box is selected, any changes to the Budgeted Amount field of the Position Total block on NBAPBUD are flagged for interface to both the Budget Development module and to the Operating Ledgers concurrently. You would then submit the following process to feed to the Budget Development module before submitting the processes to feed transactions to the live ledgers in Banner Finance.
FBRFEED
Selects budget transactions from GURFEED (with a system ID of POSNBUD) and creates and/or updates records to insert into the Budget Development area of Banner Finance. The program actually creates/updates FBBBLIN records, which is the Budgeted Line Item Table in Banner Finance. This table contains annualized amounts. It will also update only the Finance-distributed budget table FBRDIST. Updates to FBRDIST will be reflected in Period 1 of the distributed budget.
To post the encumbrance transactions (and budget adjustments, if any) to the live ledgers, submit the following processes.
FURFEED
Selects records from GURFEED based on the System ID of PAYROLL. It then creates and/or updates records to insert into the Finance Interface Table (FGBTRNI). Edits the documents (journal vouchers) and inserts the approved documents into the Approved Documents Table (FOBAPPD). Produces an error report that displays the system edits of suspended documents from the FGRTRNI process. Selects approved documents from the FGRTRNI process and posts the transactions to the ledgers in the Banner Finance System.
FGRTRNI FGRTRNR FGRACTG
If the NTRFINI Feed Budget to Finance Budget Development box is not selected, changes to the Budgeted Amount field in the Position Total block of NBAPBUD will be flagged for interface only to the Operating Ledgers in the Banner Finance System. Thus, you should not run FBRFEED and run only FURFEED, FGRTRNI, FGRTRNR, and FGRACTG.
November 2010
3-33
Process Flow
1. Complete all rule and application forms described above. 2. Be sure that a new Salary Group (NTRSGRP) and new Salary Table (NTRSALA)
have been created (see Budget Modeling on page 3-16) for the period in which the mass increases will be effective.
3. Be sure to complete NTRJINC with the desired information for salary and wage
increases.
4. Run the following batch process:
Process Name
NBPMASS
Run NBPMASS using the Process Type Value of J to update the jobs records. It is recommended that you run NBPMASS for the first time using the Report Mode of R, which will calculate and print changes to be made after you audit and approve results. If desired, make changes to NTRJINC and rerun NBPMASS in Report Mode R until desired results are realized. Once the audit is complete, run NBPMASS once again using the Report Mode of P to actually perform the database updates.
5. Since this is a mass update program, it is expected that some manual adjustments to
NBAJOBS will be necessary to handle exception employees. Prior to updating and feeding new encumbrances, these adjustments should be made.
6. Should you choose to make the budgeted amounts exactly the same as the new salary
amounts, these budget adjustments should be made at this time on the Position Total block of NBAPBUD.
Note Updating job records does not automatically cause a change to budgeted amounts (wages or fringes) on NBAPBUD. 7. If you are updating job records with an effective date that falls within a fiscal year
that is not currently active (as noted on NBAFISC), you should not proceed any further. Updating and posting encumbrances should not be done until working budgets (discussed in Budget Modeling on page 3-16) are approved (see Approving Working Budgets on page 3-38). Approving a working budget (through NBPBROL) causes the NBAFISC Active box to change to selected status for the approved fiscal year and to unselected for all other years. Only after this approval is
3-34
November 2010
completed will salary encumbrance calculations and encumbrance transactions be sent to Banner Finance be correct. If the effective date of the mass salary updates fall within a currently active year, submit the following jobs.
Process Name
NBPBUDM NHPFIN1
Use the Y option for encumbrance processing to calculate the new salary encumbrances for the current fiscal year. Enter a Y for the Encumbrance Processing parameter option. If you made changes to budgeted amounts since the last feed to Banner Finance, you may opt to enter a Y for the Budget Processing parameter option. Complete parameter options as desired. If you ran NHPFIN1 with the parameter option of Y for Budget Processing, run this program with desired parameter options. Otherwise, do not submit this job. Complete parameter options as desired. Complete parameter options as desired. Complete parameter options as desired. Complete parameter options as desired.
NHPFIN2 FBRFEED (Optional) FURFEED FGRTRNI FGRTRNR FGRACTG
Budget Maintenance Checklist: Processing Wage/Salary Adjustments

Complete the following steps only if salary adjustments are to be processed with the first day of the new fiscal year.
NTRCROL (If using System Generated Salary Encumbrance) NTRHROL (If using Encumbrance Hours Input)
Establish parameters used in Mass Salary Update Process (NBPMASS) to update Contract Start/End dates. Establish parameters used in Mass Salary Update Process (NBPMASS) to update Encumbrance Hours.
November 2010
3-35
Step
Form Or Process
Description
NTRJINC
Establish parameters used in Mass Salary Update Process (NBPMASS) to implement step and salary adjustments. Run process using the J (update <J> records) option. Make necessary adjustments to Job Records of exception employees (for example, red-circled employees). Run process entering Y at the Encumbrance Processing prompt. Run process using the following parameters: COBRA Processing: Budget Processing: Encumbrance Processing (Y/N) N (Y/N) N (Y/N) Y
4 5
NBPMASS NBAJOBS
6 7
NBPBUDM NHPFIN1
Extracts approved encumbrance data and inserts records into NHRFINC. 8 NHPFIN2 Extract encumbrance and adjustment transactions from the NHRFINC table. Insert transactions into GURFEED (collector table). Run desired Banner Position Control reports. Run Banner Finance processes to post adjustments to Operating Ledgers. FBRFEED, FURFEED, FGRTRNI, FGRTRNR, and FGRACTG.
9 10
The following diagrams show the processing flow for wage/salary adjustments.
3-36
November 2010
November 2010
3-37
Batch Process Position Control NBPMASS NHPFIN1 NHPFIN2 NPBUDM
Is NTRFINI Feed Budget to Finance Budget Development box checked?
Yes
Batch Process Batch Process Finance
Finance FBRFEED FRRFEED
No
Batch Process Finance FURFEED FGRTRNR FGRTRNI FGRACTG
End
Approving Working Budgets

Once budget modeling is complete, manual adjustments to rolled budgeted amounts have been made on the Position Total block of NBAPBUD, and a selected working budget is ready to be approved, you must complete the processes explained in this section. Ideally, an approved budget will be determined by the beginning of the new fiscal year. Human Resources and Finance personnel must work together to coordinate the processes and ensure that both systems have the same approved fiscal year. Once a budget model is accepted, it must be approved in the Banner Position Control module and in the Banner Finance System via separate batch processes.
3-38
November 2010
Application Forms
When position data is first entered in the Banner Human Resources System, several preliminary rule forms must be completed in both the Banner Finance and Human Resources Systems. These forms are listed below.
Banner Finance
FBABPRC
Establishes a record for each phase of the budget process for which a roll from another phase is required. This form defines the Base Budget and/or Phase from which each phase will be created or rolled. This form also provides for the deletion of any phase or the activation of the phase that is to be rolled to the General Ledger. The parameters entered on this form are used to run two RPTs: FBRBDBB and FBRBDRL. Distributes all or part of the budget over budget periods. (Note: If only the annual budget is used for budget reporting and available balance checking, there is no need to use the distribution feature.) Enter the FOAPAL combination to be distributed. RPT FBRBDDS must then be run to actually distribute the budget. Establishes parameters used in Mass Salary Update Process (NBPMASS) to update Contract Start/End dates (if using system-generated salary encumbrance). Establishes parameters used in Mass Salary Update Process (NBPMASS) to update Encumbrance Hours (if using encumbrance hours input).
FBABDDS
NTRCROL
NTRHROL
Batch Processes
The following batch processes approve a working budget and close the current active budget on NBAPBUD, update encumbrances on the jobs records (NBAJOBS) for the new fiscal year, post the new encumbrances to Banner Finance, and set the Active box on NBAFISC to unselected status for the fiscal year just ending and selected status for the fiscal year just beginning.
November 2010
3-39
NBPBROL
Allows you to roll the adopted position and fringe budgets to approved status for the new fiscal year, to roll current position and fringe budgets to proposed position and fringe budgets (in working status) to single or multiple budget phases (see Budget Modeling on page 3-16), and to delete the working budgets no longer needed. Results of this process are posted to the Position Totals block of NBAPBUD. Parameters include the following: Report Choice: Roll Budgets to Working Status Roll Working Budgets to Approved Status Delete Working Budgets No Longer Needed Chart of Accounts Code New Fiscal Year Current Fiscal Year Budget ID Budget Phase Salary Group Code
NBPMASS
Updates contract start/end dates and/or encumbrance hours for the fiscal year entered in the parameters (for system-generated salary encumbrances only) and posts changes to NBAJOBS. In addition, it calculates automatic step increases (and posts changes to NBAJOBS if desired), updates NTRSALA table entries by a percent or amount, and updates job records with new table/grade combinations (if desired).
3-40
November 2010
Parameters include the following: Report or Process Process Type J(Update Jobs) U(Update Table/Grade/Steps) D(Roll Contract Dates) E(Roll Encumbrance Hour) Job Change Reason Code Personnel Change Date Salary Group(FROM) Salary Group (TO) NHPFIN1 Extracts data for encumbrances and budget adjustments (and for budget modeling, budgeting and COBRA transactions) for the Banner Finance interface. This process generates budget transactions and inserts records into NHRFINC. Original budgets, budget adjustments, original fringe budgets, and fringe budget adjustments will be passed to the Budget Development module in Banner Finance (as POSNBUD transactions) and to the live ledgers (as PAYROLL transactions) in Banner Finance if the Feed Budget to Finance Budget Development box on NTRFINI is selected. If the Feed Budget to Finance Budget Development box is not selected, these transaction types will only be posted to the live ledgers (as PAYROLL transactions). Salary encumbrances and COBRA transactions are posted only to the live ledgers. All of these transactions are passed to Banner Finance through NHPFIN2. Parameters include the following: COBRA Processing (Y/N) Budget Processing (Y/N) Encumbrance Processing (Y/N)
November 2010
3-41
NHPFIN2
Extracts the encumbrance, budget and COBRA transactions from the NHRFINC table and inserts them into the GURFEED table. GURFEED is a collector table through which all interfacing transactions to the Banner Finance System are passed. Parameters include the following: Detail Report (Y/N) Interface (Y/N) Pay ID
NBPBUDM
Run process entering Y at the Process Encumbrance prompt. Make sure that the Fringe Rate Rules Change indicator on the Finance Setup Rule Form (NTRFINI) is set to Y.
Banner Finance
FBRBDDS FBRBDRL
Distributes the budget based on parameters entered on FBABDDS. Rolls the final budget phase into the new fiscal year Operating Ledger. If you are rolling current year budget into your first phase, define Action as 0 for OPAL and enter the COA code and Fiscal Year. Use B for a phase to phase roll. A and D are used for activation and deletion respectively.
FURFEED
Selects records from GURFEED when the System ID is PAYROLL. It then creates and/or updates records to insert into the Finance Interface Table (FGBTRNI) and updates the Banner Finance ledgers. Edits the documents (journal vouchers) and inserts the approved documents into the Approved Documents Table (FOBAPPD). Produces an error report that displays the system edits of suspended documents from the FGRTRNI process. Selects approved documents from the FGRTRNI process and posts the transactions to the ledgers in the Banner Finance System.
FGRTRNI
FGRTRNR FGRACTG
3-42
November 2010
Process Flow
Ideally, on the first day of the new fiscal year, there will be a budget to be approved for that fiscal year. When working budgets are rolled to Approved status in the Banner Position Control module, the status of currently active budgets changes from A to C and the status of the chosen working budget changes to A. In addition, you may choose to delete all other working budgets or to leave them indefinitely. The current fiscal year is made inactive and the approved fiscal year active in the NBAFISC Active box.
1. Complete the FBABPRC and FBABDDS forms to establish parameters for the
necessary batch process in finance to approve a budget.

2. Run the following batch processes. Process Name Comments/Special Instructions
NBPBROL
Use the Report Choice of A to roll a working budget to approved status. Enter the Budget ID and Phase of the working budget to be approved. Through this process, the Active box of NBAFISC for the fiscal year just ending is changed from selected to unselected. The Active box for the fiscal year just beginning is changed from unselected to selected status.
FBRBDDS FBRBDRL NBPBUDM NHPFIN1 NHPFIN2 FURFEED FGRTRNI FGRFRNR FGRACTG NBPBROL (Optional)
Complete parameter options as desired. Complete parameter options as desired. Enter Y in the Encumbrance Processing parameter. Enter Y in the Encumbrance Processing parameter. Complete parameter options as desired. Complete parameter options as desired. Complete parameter options as desired. Complete parameter options as desired. Complete parameter options as desired. If you wish to delete all working budgets, submit this process by entering Y at the Delete Working Budgets No Longer Needed parameter.
November 2010
3-43
Budget Maintenance Checklist: Approving a Working Budget

Complete Steps 13 to ensure that there are no outstanding budgets and/or encumbrances to post for the fiscal year coming to a close. 1 NBPBUDM (Charge Back Method only) NHPFIN1 Run the process using the budgeting and encumbering options for Active Budgets. Run process using the following parameters: COBRA Processing: Budget Processing: Encumbrance Processing (Y/N) N (Y/N) N (Y/N) Y
Extracts unposted encumbrance and budgets amounts and inserts records into NHRFINC for the fiscal year coming to a close. 3 NBPBROL (Optional) Run process using the A (approve a budget) option. Run process using the D (delete working budgets) option.
Complete Steps 411 only if salary adjustments are not to be processed effective with the first day of the new fiscal year. 4 NTRCROL If using System Generated Salary Encumbrance Establish parameters used in Mass Salary Update Process (NBPMASS) to update Contract Start/End dates. 5 NTRHROL If using Encumbrance Hours Input Establish parameters used in Mass Salary Update Process (NBPMASS) to update Encumbrance Hours. 6 7 NBPMASS NBPBUDM Run process using the update Contract Start/End dates and/or update Encumbrance Hours. Run process entering Y at the Encumbrances Processing prompt.
3-44
November 2010
Step
Form Or Process
Description
NHPFIN1
Run process using the following parameters: COBRA Processing: Budget Processing: Encumbrance Processing (Y/N) N (Y/N) N (Y/N) Y
Extracts approved budget and encumbrance data and inserts records into NHRFINC. 9 NHPFIN2 Extracts encumbrance and budget transactions from the NHRFINC table. Inserts transactions into GURFEED (collector table). Run desired Banner Position Control reports. Run Banner Finance processes to post approved budgets to Live Ledgers. FBRFEED, FURFEED, FGRTRNI, FGRTRNR, and FGRACTG. Banner Finance must approve the budget so that it moves from budget development to the operating ledger.
10 11
The following diagrams show the flow for Approving Working Budgets.
November 2010
3-45
Refer to Processing Wage/Salary Adjustments
Finance Control Form FBABPRC
Batch Processes Position Control NBPBROL NHPFIN1 NHPFIN2
Batch Processes Finance FBRBDDS FBRBDRL
3-46
November 2010
Do you wish to encumber labor dollars for the new fiscal year?
Yes
Batch Processes Position Control NBPMASS NHPFIN1 NBPBUDM NHPFIN2
No
Batch Processes Finance FURFEED FGRTRNI FGRTRNR FGRACTG
Do you wish to delete working budgets?
Yes
Batch Process Position Control NBPBROL
No
End of Process
November 2010
3-47
Feeding Payroll Transactions

A position labor distribution hierarchy allows the desired position labor distributions to default to application forms through various levels of the personnel and payroll processes. The default hierarchy flows as follows:
NBAPBUD
This form defines the labor distribution that is used to post to the Banner Finance System. Labor distributions can be split, but the total percentage must equal 100. The values in the Position Labor Distribution block default from NBAPBUD but can be overridden at this level. The values shown on this form default from the Job Labor Distribution block on NBAJOBS. The accounting distributions that default can be overridden at payroll entry time. After payroll is processed, Payroll could choose to do a payroll adjustment (termed Redistribute in Banner HR) to redistribute labor distribution transactions to alternate accounts from pay events that have or have not been interfaced to Banner Finance. This is accomplished by accessing PHAHOUR from the PHAADJT form.
NBAJOBS PHAHOUR
During the actual feed to Banner Finance, the following Banner Human Resources rule forms allow you to post transactions to labor distributions for specific earn codes and/or deductions other than the labor distribution on PHAHOUR.
PTRBDCA
The Benefit/Deduction Labor Distribution block enables users to post fringe liabilities (employer and/or employee) and expenses to different labor distribution(s) other than those defaulting from PHAHOUR during the feed to Banner Finance. The override is by employee class and COA code for each deduction code. The Employee Class Labor Distribution block allows you to define labor distributions for specific earn codes by employee class. For example, if the client wishes to charge all overtime to a different Fund, Organization, Account, Program, Activity, and/or Location, that information would be entered on this form and would be considered in the Banner Finance feed.
PTREARN
An employee's pay events (for example, adjustments and manual checks) are assigned dispositions ranging from 05 to 70 to indicate where they are in the multiple step payroll process.
3-48
November 2010
The following dispositions are associated with the interfacing of payroll expenses through to the Banner Finance System. 60 62 70 Awaiting Finance Extract Awaiting Finance Interface Complete
All pay events related to a particular payroll (as identified by Year, Pay ID, and Pay Number) must reach disposition 60 in order to be extracted and subsequently passed to the Banner Finance System. This includes various adjustments (e.g., voids, reissues, and redistributions) that are often processed some time after the main payroll run. In these cases, a payroll run may contain more than one pay event (and therefore more than one disposition) for an employee. For example, an employee may have an original pay event at disposition 70 and, because of the adjustment, have another pay event at a lower disposition. The objective is to get all dispositions for original pay events and adjustments to 70, which ensures that all payroll transactions have been posted to Banner Finance. The Expend Budget with Earning Value? check box on PTREARN controls whether or not a particular earning is added to the earnings expended amount on NBAPBUD. The Gross Salaries Rule Class (HGRS or HGNL) controls encumbrance liquidation. This can be overridden on PTREARN. Through the payroll process, year-to-date totals are updated for each employee by job(s), by earning code, and/or by deduction code. Each payroll (designated by year, pay ID, and pay number) is then fed to the Banner Finance System. The manner in which financial transactions post to the Banner Finance System from the Banner Human Resources module depends on the rule classes developed in Banner Finance and indicated on NTRFINI. There are two options for selective encumbrance liquidation processing: Bypass encumbrance liquidation on selected types of earnings Bypass encumbrance liquidation entirely To bypass encumbrance liquidation on selected types of earnings, follow these steps:
1. Go to the Earnings Code Rule Form (PTREARN) and enter the earnings code in the
Earnings Code field.

2. Go to the Earnings Code Rule Class field at the bottom of the form. Enter the rule
class HGNL and then Save. This rule class directs the HR Finance Expenditures Extract Program (PHPFEXP) and the Finance Posting Program (FGRACTG) to do everything that the existing HGRS rule class does, but to skip the encumbrance liquidation step. Because the HGNL rule class overrides the NTRFINI default rule class governing salary expenditures, you do not have to enter a value in this field for every earnings
November 2010
3-49
code. Only enter a value for an earnings codes that should use a rule class different from the NTRFINI default. For example, you may choose to leave regular pay (REG) as it is and install the HGNL override on PTREARN only for overtime pay (OT). When subsequent payrolls are run and fed from Banner Human Resources to Banner Finance, the encumbered amount for the position (specified in the Position Total block of NBAPBUD) is not reduced; the payroll encumbrance on the Finance side is not reduced when the transaction is posted. To bypass encumbrance liquidation entirely, access NTRFINI and substitute HGNL for HGRS. In this case, you do not have to specify any overrides on PTREARN. Encumbrances are not reduced on either the Banner Human Resources or the Banner Finance side.
Rule Forms
Banner Finance
FTMCOAS FTMFUND
Establishes the Chart of Accounts for the installation. Establishes valid funds for labor expenditures. A fund is defined, in layperson's terms, as balance sheet items (assets, liabilities, equity). Funds can be restricted (for example, grants) or unrestricted (for example, general). Establishes valid organizations for labor expenditures. An organization represents a department within the installation. Establishes valid accounts for labor expenditures. Accounts are line items within an installation's financial structure. They include general ledger accounts (assets and liabilities) and operating ledger accounts (revenues and expenses). Establishes valid programs for labor expenditures. Programs enable an installation to define a way of pulling transactions across organizations and accounts. Establishes valid activities for labor expenditures. Example: A number assigned to the YMCA for using the site's pool to teach lifesaving. Establishes valid locations. Locations represent a building and room number.
FTMORGN FTMACCT
FTMPROG
FTMACTV
FTMLOCN
3-50
November 2010
FTMSDAT
Establishes the system ID as PAYROLL. The PAYROLL system ID feeds payroll, encumbrance, budget, and COBRA transactions to the operating ledgers via the FURFEED process. Defines the fiscal year and fiscal periods. Establishes valid budget phases within budget IDs for budget development purposes. Defines valid Banner Finance System rule class codes that are being maintained for transactions from Banner Human Resources. Banner Human Resources uses these rule class codes on NTRFINI in the Banner Position Control module. Banner Finance uses them with transaction processing codes from other sources in the Budget Development module.
Note: When editing is performed against general ledger accounts, only a fund and account are required. When editing is performed against operating ledger accounts, you must enter fund, organization, account, and program. Activity and location are always optional entries in Banner Human Resources.

Several rule forms must be completed to run payrolls in Banner Human Resources. For detailed information, refer to the Banner Human Resources User Guide.
NTRSGRP NTRSALA NTRPCLS
Defines the salary group for each salary table (defined on NTRSALA). Establishes the salary ranges and/or steps for each salary group, table, and grade. Creates and associates position classes with employee classes, employee skill levels, position groups, and salary/wage ranges. This rule form must be completed prior to completing NBAPOSN.
November 2010
3-51
Application Forms
There are several application forms which must be completed to run a payroll cycle. It is important to note that the Banner Human Resources System allows you to override specific labor distributions by earn code (PTREARN) and by benefit/deduction code (PTRBDCA). This ensures that specified earnings and benefits/deductions can be charged to accounts which are different from the accounts where individual position labor expenses are charged. For example, if you charge all overtime to a central organization or account, the appropriate entry must be made on PTREARN for the overtime earn code. In the Banner Position Control module, NTRFINI determines accounting distributions for salary expenses, employee/employer liabilities, net pay, deferred pay, etc., through the use of rule classes established on FTMRUCL.
Batch Processes
The following batch processes feed payroll expenses (including adjustments) to the Banner Finance System.
PHPFEXP
Generates labor distributions based on the rules set up in Banner Human Resources. Updates the position totals encumbrance and expended amounts on NBAPBUD. This is a COBOL process that must be run from the host command or at the system level. It is run when the pay event disposition is at disposition 60 (Awaiting Finance Extract) and takes the pay event to disposition 62 (Awaiting Finance Interface). Parameters include the following: Payroll Year Payroll ID Payroll Number
3-52
November 2010
NHPFIN2
Extracts the labor, fringe benefits, and net pay distributions and inserts them into a table called GURFEED. This process is run when the pay event is at disposition 62 (Awaiting Finance Interface) and takes the pay event to disposition 70 (Complete). Parameters include the following: Detail Report (Y/N) Interface (Y/N) Pay ID
Banner Finance
FURFEED
Selects records from GURFEED where the System ID is PAYROLL and inserts the records into the Finance Interface Table (FGBTRNI). Edits the documents (journal vouchers) and inserts the approved documents into the Approved Documents Table (FOBAPPD). Produces an error report which displays the system edits of suspended documents from the FGRTRNI process. Selects approved documents from the FGRTRNI process and posts the transactions to the ledgers in the Banner Finance System.
FGRTRNI
FGRTRNR FGRACTG
Process Flow
1. Ensure that all rule forms in Banner Finance, Human Resources, and Position Control
have been completed.

2. Run the payroll process and/or payroll adjustments completely through PHPUPDT.
(The disposition will equal 60).

3. Submit NHPFIN1, NHPFIN2, FURFEED, FGRTRNI, FGRTRNR, and FGRACTG to
extract new or changed budget and encumbrance transactions and post them to Banner Finance.
November 2010
3-53
4. Submit PHPFEXP, NHPFIN2, FURFEED, FGRTRNI, FGRTRNR, and FGRACTG
to process payroll expenditures.

5. Use the Organization Budget Status Form (FGIBDST), the Detail Encumbrance
Activity Form (FGIENCD), and the Detail Transaction Activity Form (FGITRND) to reconcile the payroll to the Banner Finance feed.
Payroll Feed Checklist

NTRFINI
Establish/verify Finance Rule Classes used in the Interface process. Defines net, fringe and deferred pay distributions. Run process using the Year, Pay ID, Pay Number. The process uses amounts calculated by Payroll Calculation Process (PHPCALC) and assigns the appropriate rule classes as established on NTRFINI (above). Populates the Finance Interface Collector table (NHRFINC) in detail broken down by earn code and deduction code within each rule class. Run process to extract labor, fringe benefit, and net pay distribution from NHRFINC. Formats journal entry for submission to Banner Finance with system ID and time stamp. Journal entry inserted into GURFEED. Produces a detailed audit report of the submitted transactions. Primary source document for reconciliation of Payroll to Banner Finance. Run desired reports. Run Banner Finance processes to post transactions to the Operating Ledgers. (FURFEED, FGRTRNI, FGRTRNR, FGRACTG)
PHPFEXP
NHPFIN2
4 5
The following diagrams show the flow for feeding payroll transactions.
3-54
November 2010
Batch Processes Human Resources PDPLIFE PHPDOCM PHPLEAV PHPCALC PHPPROF PHPUPDT PHPTIME PHPCHEK PHR****
(Optional)
Are Payroll adjustments needed? (See Note*)
Yes
*Note: Adjustments can be processed at any time after PHPUPDT has been run.
No
Adjustment Forms And Processes Human Resources
November 2010
3-55
Batch ProcessHuman Resources PHPFEXP
Batch ProcessPosition Control NHPFIN2
Batch ProcessFinance FURFEED FGRTRNI FGRTRNR FGRACTG
End of Process
Processing COBRA Transactions

The Consolidated Omnibus Budget Reconciliation Act (COBRA) is the federal act requiring employers to extend medical coverage to individuals who lose their eligibility to participate in the employer's group health plan through certain qualifying events. Continuation of health coverage is administered separately by the employer and includes an administrative fee. Please note that posting of COBRA transactions to the Banner Finance System does not create receivable transactions.
Rule Forms
Below is a list of rule forms that apply to the actual feeding of COBRA transactions. It does not include all rule forms pertaining to this module.
Banner Finance
3-56
November 2010
FTMCOAS FTMFUND
Establishes the Chart of Accounts for the installation. Establishes valid funds for labor expenditures. A fund is defined, in layperson's terms, as balance sheet items (assets, liabilities, equity). Funds can be restricted (for example, grants) or unrestricted (for example., general). Establishes valid organizations for labor expenditures. An organization represents a department within the installation. Establishes valid accounts for labor expenditures. Accounts are line items within a site's financial structure. They include general ledger accounts (assets and liabilities) and operating ledger accounts (revenues and expenses). Establishes valid programs for labor expenditures. Programs enable you to define a method of pulling transactions across organizations and accounts. Most educational institutions use programs defined by NACUBO (for example, Instruction). Establishes valid activities for labor expenditures. An example of an activity is a number assigned to the YMCA for using your site's pool to teach lifesaving. Establishes valid locations. Locations represent a building and room number. Establishes the system ID as PAYROLL or POSNBUD. The PAYROLL system ID feeds payroll, encumbrance, budget, and COBRA transactions to the operating ledgers via the FURFEED process. The POSNBUD system ID feeds budget transactions to the Budget Development module via the FURFEED process. (Note: Both the PAYROLL and POSNBUD IDs are included as part of the Banner Finance seed data.) Defines the fiscal year and fiscal periods. Establishes valid budget phases within budget IDs for budget development purposes.
FTMORGN FTMACCT
FTMPROG
FTMACTV
FTMLOCN FTMSDAT
FTMFSYR FTMOBUD
November 2010
3-57
FTMRUCL
Defines valid Banner Finance System rule class codes that identify the journal type being maintained for transactions from Banner Human Resources. These defined rule classes are used on the HR/Finance Setup Form (NTRFINI). When editing is performed against general ledger accounts, only a fund and account are required. When editing is performed against operating ledger accounts, you must enter fund, org, account, and program. Activity and location are always optional entries in Banner Human Resources.
NTRFINI
Uses predefined rule class codes from FTMRUCL in the Banner Finance System for Banner Human Resources transactions. It determines accounting distributions for such items as salary expense, employee/employer liabilities, net pay, deferred pay, COBRA, and so on.
Batch Processes
The manner in which the financial transactions for COBRA post in Banner Finance from Banner Human Resources depends on the Banner Finance System rule class codes specified on NTRFINI.
Note Do not post COBRA payments to Banner Finance without first discussing system setup with a financial consultant.
NHPFIN1
Extracts data for COBRA payments (and for budgeting, budget modeling, and encumbrances) for the Banner Finance Interface. This process generates COBRA transactions and inserts records into NHRFINC. They are then passed through to the Banner Finance System by NHPFIN2. Parameters include the following: COBRA Processing (Y/N) Budget Processing (Y/N) Encumbrance Processing (Y/N)
3-58
November 2010
NHPFIN2
Extracts the transactions from the NHRFINC table and inserts them into the GURFEED table. GURFEED is a collector table through which all interfacing transactions to the Banner Finance System are passed.) Parameters include the following: Detail Report (Y/N) Interface (Y/N) Pay ID
Banner Finance
FURFEED
Selects records from GURFEED based on the System ID you specify and inserts the records into the Finance Interface Table (FGBTRNI) to update the Banner Finance ledgers. Edits the documents (journal vouchers) and inserts the approved documents into the Approved Documents Table (FOBAPPD). Produces an error report which displays the system edits of suspended documents from the FGRTRNI process. Selects approved documents from the FGRTRNI process and posts the transactions to the ledgers in the Banner Finance System.
FGRTRNI
FGRTRNR FGRACTG
Process Flow
1. Complete all rule and application forms as noted above. 2. After the system has been set up to have the payments interfaced to Banner Finance,
submit the following batch processes.

Process Name Comments/Special Instructions
NHPFIN1 NHPFIN2 FURFEED FGRTRNI
Enter Y at the COBRA Processing parameter. Complete parameter options as desired. Complete parameter options as desired. Complete parameter options as desired.
November 2010
3-59
Process Name
FGRTRNR FGRACTG
Complete parameter options as desired. Complete parameter options as desired.
COBRA Feed Checklist

The manner in which the financial transactions for COBRA post in Banner Finance from Banner Human Resources depends on the Banner Finance System rule class codes specified on NTRFINI. Do not post COBRA payments to Banner Finance without first discussing system setup with a financial consultant
Step
Form or Process
Description
NHPFIN1
Extract data for COBRA payments (and for budgeting, budget modeling, and encumbrances) for the Banner Finance Interface. This process generates COBRA transactions and inserts records into NHRFINC. Extract the transactions from the NHRFINC table and inserts them into the GURFEED table. Select records from GURFEED based on the System ID you specify and insert the records into the Finance Interface Table (FGBTRNI) to update the Banner Finance ledgers. Edits the documents (journal vouchers) and inserts the approved documents into the Approved Documents Table (FOBAPPD). Produces an error report which displays the system edits of suspended documents. Selects approved documents and posts the transactions to the ledgers in the Banner Finance System. (FURFEED, FGRTRNI, FGRTRNR, and FGRACTG)
2 3
NHPFIN2 Finance Feed
The following diagrams show the flow for processing COBRA transactions.
3-60
November 2010
November 2010
3-61
No
Do you wish to feed COBRA payments from BANNER Human Resources?
Consult your Finance representative regarding BANNER Finance implications.
Yes
Batch ProcessesPosition Control NHPFIN1 NHPFIN2
Batch ProcessesFinance FURFEED FGRTRNI FGRTRNR FGRACTG
End of Process
3-62
November 2010
November 2010
3-63
Installments/Feed to Banner Finance

As shown in the flowchart at the beginning of this section, both Banner Human Resources and Banner Advancement feed to Banner Finance the transactions relating to the deductions. These transactions cannot be posted twice. This process is similar to the way FICA deductions are handled between Banner Human Resources and Banner Finance. Finance personnel must enter a transaction to offset a liability account and produce an accounts payable check. This ensures that the money gets to the correct bank and fund. Payroll deduction gifts are fed to Banner Finance via the following procedure:
1. Banner Human Resources captures the deduction amount used to create a gift/
installment payment in Banner Advancement. The deduction creates a credit to a liability account when Banner Human Resources feeds the same deduction to Banner Finance.
2. Banner Finance creates a transaction to offset the liability. This may result in a check
being produced.
3. Banner Finance creates a second transaction to credit Accounts Receivable and debit
Cash Receipt.
4. Banner Advancement feeds the same gift/installment payment with a gift/payment
type (such as rule class) that will debit Accounts Receivable and credit the actual designation of the gift/installment payment.
Note A sample rule class, ASDE, is delivered to be used with the gift/payment type for payroll deduction gifts.
3-64
November 2010
Reports and Processes
This chapter contains information about reports generated by the Banner Finance System, as well as reports for GASB enhancements that you can open with a spreadsheet tool such as Microsoft Excel. The following table outlines the contents of this chapter.
Naming Conventions Attribute Reporting Reports Description Report Parameters
An explanation of the seven-character naming convention that applies to all Banner reports follows this introduction. A brief discussion of the ad hoc reporting capabilities of the Banner Finance System. A brief explanation of each reports contents and functionality follows each report heading throughout this chapter. The following information is provided with all report parameters: Parameter name Indicator stating if a parameter is required or optional Brief description of each parameter Valid values that must be entered for each required parameter, if applicable
Report Sample
A sample report follows each set of report parameters. The report sample provides you with a complete picture of the report. Most samples include the following information: Data page(s) Detailed, itemized report data Summary page Grand totals of all data categories
Note Sample reports are presented in alphabetical order by the reports sevencharacter name.
Job Submission
Job Submission enables you to execute a report without having to exit the application and return to the operating system. You do not have to know the operating system commands
November 2010
Banner Finance 8.5 User Guide Reports and Processes
4-1
to execute and print the report. A report refers to any Banner SQL* report program. Each report produces actual report output or is written to be a process (for example, posting).
Special Print Samples

Due to differences in vendor pre-printed form requirements, sample output is not provided with the following reports and processes in this manual: Check Print Process (FABCHKP) Batch Check Process (FABCHKS) Bid Form Print (FPABIDD) Change Order Form Print (FPACORD) Purchase Order Form Print (FPAPORD) Requisition Form Print (FPARQST)
Naming Conventions
A seven-character name is associated with all Banner reports and processes. Each letter of this report name corresponds to its numbered position depicted in the following example:
Position Locations:
F 1
B 2
R 3
F 4
E 5
E 6
D 7
Note Use W, Y, or Z as the first character for new client-developed applications built to coexist with Banner Finance. For client-developed forms or modules used within a Banner application, use the system identifier as the first character (for example, F= Finance). Use W, Y, or Z as the second character.
Position 1: Primary system owning the report:
A B C D F
= = = = =
Advancement Property Tax Courts Cash Drawer Finance
4-2
November 2010
G K L M N O P Q R S T U V X W,Y,Z
= = = = = = = = = = = = = = =
General Work Management Occupational Tax and License MICRO-FAIDS Position Control Customer Contact Human Resources/Payroll/Personnel Electronic Work Queue Financial Aid Student Accounts Receivable Utilities Voice Response Records Indexing Reserved for client-developed applications that co-exist with Banner
If W, Y, or Z appears as the first character of the report name, refer to the preceding note. Position 2: Application module owning the report. If the character in position 1 is F, then the character in Position 2 is one of the following:
A B C F G I O P R S T U X W,Y,Z
= = = = = = = = = = = = = =
Accounts Payable Budget Development Cost Accounting Fixed Assets General Ledger Investment Management Operations Purchasing and Procurement Research Accounting Stores Inventory Table Utilities Archive/Purge Reserved for client-developed forms or modules used within a Banner application (character in position 1 does not = W, Y, or Z)
Position 3: Type of report:
November 2010
4-3
A B I M Q P R
= = = = = = =
Application, input, or update form Base table Inquiry form Maintenance Form Query form accessed from another form Process Rule table Repeating table Report or process Validation table view
Positions 4 - 7: Unique four-character abbreviation of the report name. For example, FBRFEED (Finance Budget Feed Process) is named as follows: F B R FEED = = = = Finance Budget Development Report Feed Process
4-4
November 2010
Accounts Payable Module

This section describes each report in the Accounts Payable module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
4-5
November 2010
1099 Forms Print (FAB1099)

Description
This report creates 1099 forms for selected vendors for reporting to the IRS. Forms print two to a page. Refer to the online help for more information on the 1099 Income Type Maintenance Code Form (FTMITYP). FTMITYP contains the income type codes necessary for 1099 reporting. Income type codes are supplied in the seed data. Descriptions for the income type codes are standardized by the U. S. Government. Income types include:
Box 1 (rents) Should only print if >=600 Box 2 (Royalties) Should only print if >=10 Box 3 (Other income) Should only print if >=600 Box 5 (Fishing Boat) Any amount Box 6 (Medical and health care pmts) Should only print if >=600 Box 7 (non-employee compensation) Should only print if >=600
Box 8 (Substitute pmts in lieu of div/int) Should only print if >=10 Box 10 (Crop Insurance) Should only print if >=600 Box 13 (Excess Golden parachute pmts) Any amount Box 14 (Gross proceeds to an attorney) Any amount Box 15a (Section 409A Deferrals) Should only print if >=600 Box 15b (Section 409A Income) Any amount
4-6
November 2010
Parameters
Name
Required?
Description
Values
Printer Type (1)Dot, (2)Laser
Yes
Type of printer used.
1 2
Dot matrix printer Laser printer
Reporting Year (YYYY) Yes Correction as of Date No
Calendar 1099 reporting year Earliest date corrections were made to a vendor after the original 1099s were produced.
Note: Populate this parameter for correction runs only.
YY DD-MON-YYYY
Combine or Separate Amounts
Yes
Enter S to combine amount for rents and prizes over $599.99. The remaining amounts report separately. Enter C to combine amounts for rents, prizes, medical, and health care benefits, and nonemployee compensation. Based on the combined amount, the system determines whether a 1099 should be generated. The remaining amounts report separately.
C S
Combined amount Separate amount
4-7
November 2010
Report Sample
Banner University Systems & Computer Technology Four Country View Road Malvern PA 19355 610-555-6666 x7777
10000.01 20000.02 30000.03 69000.08
23-1701520
01-1222333
50000.05
60000.06
NNNN vendor w/ck vendor 221000.22 ap address no po address Allmighty CA 17112 130000.13 69000.08 PA 150000.15 151000.15 140000.13 80000.08 100000.11
4-8
November 2010
Batch Check Accounting Process (FABCHKA)

Description
Listed below are the four processes comprising the Banner Finance Batch Check writing process. Before executing a check processing cycle, you must complete the Batch Check Print Form (FAABATC) or the Online Check Print Form (FAAONLC). Execute these four individual check processes individually to accomplish selecting invoices to be paid, printing checks, producing the check register, and creating the accounting for checks.
Note These procedures are only examples of how to run checks at your installation. Due to potential differences in site specific modifications and the operating system installed at your site, these procedures may not run exactly as delivered. Please modify them to your site specific standards as is necessary.
Name
Process
Purpose
Additional Notes
Batch Check Process Check Print Process Batch Disbursement Register Process Batch Check Accounting Process
FABCHKS FABCHKP FABCHKR FABCHKA
Selects the invoices to be paid Prints the checks Produces the check register Creates the cash disbursements for the checks written in FABCHKP
This process produces no output. You may combine FABCHKS and FABCHKP into the FABCHK1 process. This process produces output. This process produces no output. After FABCHKA has completed, execute the Posting Program (FGRACTG) to post the checks to the ledgers.
FABCHK1 is an alternative method to executing FABCHKS and FABCHKP. Just as a report submitted through the Process Parameter Entry Form (GJAPCTL), FABCHK1 executes the Batch Check Process (FABCHKS) and the Check Print Process (FABCHKP). FABCHK1 selects and creates the check print file. After FABCHK1 completes successfully, you must execute by the Batch Disbursement Register Process (FABCHKR) and Batch Check Accounting Process (FABCHKA).
4-9
November 2010
You cannot combine all four of these procedures into one procedure for the following reasons: A procedure within job submission can only point to one printer; FABCHKP and FABCHKR may require different printers because of the special forms requirement of the check print. You cannot execute FABCHKA unless FABCHKP succeeds. The definition of FABCHK1 appears on the GJAJOBS form as a procedure. When you enter FABCHK1 in the Job Name field, GJAPCTL submits FABCHK1. If you do not wish to send the output to the printer after you execute the procedure (a parameter option on GJAPCTL), the output resides in your home directory. Refer to your site operating procedures at this time.
Warning If you rewrite scripts to execute the above procedures, you must modify the reports themselves. Within the reports, hardcode the report name and the procedure name. To execute the report with another script name, you must include the new script name in the JOBNAME1 variable within the report.
Currency Conversion If you use foreign currency for a given invoice, and the Disbursing Agent Indicator on the Invoice/Credit Memo Form (FAAINVE) equals Y (Yes), run FABCHKD before FABCHKA. Please refer to the Disbursement Check Report (FABCHKD) for a detailed description. If you use a foreign currency and the Disbursing Agent Indicator on FAAINVE equals N (No), FABCHKD processes as follows: Calculates exchange rate at time of check run Computes new invoice amount at the base currency Compares the new amount to the existing invoice amount Posts the difference to an exchange rate account Checks to ensure that the disbursing agent process has run to completion before deleting temporary records This process creates accounting records and writes a record to the Approved Document Table (FOBAPPD). This process does not produce output. You may execute FABCHKA from the Batch Check Print Form (FAABATC) or through Job Submission.
4-10
November 2010
Parameters
Name
Required?
Description
Values
Parameter Sequence Number
No
System-generated via Job Submission Number of printed lines on a page. Default = 55
Number of Printed Lines Yes per Page
4-11
November 2010
Disbursement Check Report (FABCHKD)

Description
The Disbursement Check Report will report all checks written to disbursing agents when a foreign currency is required for payment. FABCHKD selects invoices with currencies from the check run for which the Disbursing Agent Indicator on FAAINVE is set to Y (Yes). The check number and name of the foreign currency are printed in the page heading, and the detail information for each vendor is shown in the main body of the report. For each vendor, as identified by the vendor name and address, a list of invoices to be paid is printed along with the gross amount, discounts, tax amount, and net amount (in the foreign currency) for each invoice. After the list of invoices is printed for each vendor, a model check is printed which contains the total net amount, the total net amount spelled out, the vendor name and address, and is in the form of the check that will be issued from the disbursing agent to the vendor. Each currency code begins on a new page. When a new currency code is encountered, the total net amount is printed at the end of the previous currency page. When performing the batch check writing process, FABCHKD should be run after the Batch Check Selection Process (FABCHKS) and the Batch Check Printing Process (FABCHKP). FABCHKD should be run before the Batch Check Accounting Report (FABCHKA). If checks are written to a disbursing agent and FABCHKD is not run before FABCHKA, an error condition will be reported in FABCHKA.
Parameters
Name
Required?
Description
Values
No
4-12
November 2010
Report Sample (Page 1 of 3)
REPORT: FABCHKD CHECK NO: C1111110 DISB AGENT: Canadian National Bank CURRENCY: French Francs
Development Disbursement Check Report CHECK RUN: 06/25/1996
RUN DATE: 07/03/1996 TIME: 12:17 PM PAGE: 1
<------------------- APPROVED AMOUNTS --------------------> <--- INVOICE NUMBERS ---> DISCOUNT/ WITHHOLDING/ PAYEE/VENDOR NAME INTERNAL VENDOR'S GROSS PREV PAID ADDL CHRG/TAX NET ---------------------------------------------------- -------- ------------------ -------------- -------------LAB Discount J1000004 CCC 4,444.00 .00 .00 4,444.00 J1000005 CCC 50.00 .00 .00 50.00
Four Thousand Four Hundred Ninety-Four & 00/100************************************************ ************4,494.00 LAB Discount 2200 Devereaux Ave. Chicago IL 20045
<------------------- APPROVED AMOUNTS --------------------> <--- INVOICE NUMBERS ---> DISCOUNT/ WITHHOLDING/ PAYEE/VENDOR NAME INTERNAL VENDOR'S GROSS PREV PAID ADDL CHRG/TAX NET -------------------------------------------------------- -------- ------------------ -------------- -------------Laboratory Supplies, Inc. J1000003 BBB 2,222.00 .00 .00 2,222.00
Two Thousand Two Hundred Twenty-Two & 00/100******************************************************** ************2,222.00 Laboratory Supplies, Inc. 445 Washington LN Ambler PA 19033
4-13
November 2010
CURRENCY TOTAL
7,827.00
4-14
November 2010
Check Print Process (FABCHKP)

Description
The Check Print Process enables you to print checks. Use the Batch Check Print Form (FAABATC) or the Online Check Print Form (FAAONLC) to specify the parameters for a printed check. FABCHKP prints a '#' symbol in an address, if required. Names on checks appear in the following format: Name Prefix, First Name, Middle Initial, Last Name Prefix, Last Name, Suffix (for example, Mr. Stephen L. Van Gibson, Jr.). Currency Conversion The following information pertains to the printing of checks only, and not to direct deposit payments. The Check Print Process (FABCHKP) and the Batch Disbursement Register Process (FABCHKR) print an invoice's converted dollar amount as the check amount if currency conversion is being used and the invoice's Disbursing Agent Indicator on FAAINVE is set to Y (Yes). For a given invoice, if foreign currency is used and the Disbursing Agent Indicator on FAAINVE is set to N (No), FABCHKP prints the currency on the check (for example, French Francs). Report output varies based on your pre-printed form requirements.
Parameters
Name
Required?
Description
Values
No
4-15
November 2010
Batch Disbursement Register Process (FABCHKR)

This process produces a hard copy output generated after the execution of the Batch Check Print Process (FABCHKP) and before the Batch Check Accounting Process (FABCHKA). The Batch Check Register Report contains a listing (a register) of only those check numbers printed from the FABCHKP process. The Batch Check Print Process, FABCHKP, is the actual printing of checks on special check forms. The following information pertains to the printing of checks only, and not to direct deposit payments. If currency conversion is being used and the invoice's Disbursing Agent Indicator on FAAINVE is set to Y (Yes), the Check Print Process (FABCHKP) and the Batch Disbursement Register Process (FABCHKR) print an invoice's converted dollar amount as the check amount. For a given invoice, if foreign currency is used and the Disbursing Agent Indicator on FAAINVE is set to N (No), FABCHKP prints the currency on the check (for example, French Francs). When Processing Payments by Check Only You must run the Batch Check Process (FABCHKS) and the Check Print Process (FABCHKP) before running the Batch Disbursement Register Process (FABCHKR). When Processing Payments by Direct Deposit or by Check and Direct Deposit You run the Batch Check Process (FABCHKS), and either the Direct Deposit File Creation Process (FAPDIRD) or the Canadian Direct Deposit Tape Process (FAPCDIR), before running the Batch Disbursement Register Process (FABCHKR).
4-16
November 2010
Report Sample
REPORT FABCHKR FISCAL YEAR 96 BANK: T1 First National Bank
Development Batch Check Register Check Run: 05/02/1996 <------------------- APPROVED DISCOUNT/ GROSS PREV PAID ---------------- -----------$200.00 $20.00 $233.00 $344.00 $200.00 $234.00 $300.00 BANK TOTAL $23.30 $34.40 $20.00 $23.40 $30.00
RUN DATE: 05/02/1996 TIME: 03:47 PM PAGE: 1 AMOUNTS --------------------> WITHHOLDING/ ADDL CHG/TAX NET ------------ ---------------$.00 $180.00 $.00 $.00 $.00 $.00 $.00 $209.70 $309.60 $180.00 $210.60 $270.00 ================ $1,359.90 CHK TYP IND --B B B B B B
CHECK NUMBER -------00000004 00000005 00000006 00000007 00000008 00000009
PAYEE/VENDOR NAME -----------------------------Laboratory Supplies, Inc. Laboratory Supplies, Inc. Laboratory Supplies, Inc. Laboratory Supplies, Inc. Laboratory Supplies, Inc. Laboratory Supplies, Inc.
<--- INVOICE NUMBERS ---> INTERNAL VENDOR'S -------- --------------I0000015 I0000016 I0000017 I0000018 I0000019 I0000020
4-17
November 2010
Batch Check Process (FABCHKS)

Description
This process enables you to select items for payment by check or direct deposit. It does this by evaluating invoices to be paid, within the date and bank parameters specified. This process does not produce output. The Batch Check process supplies the name of the party who will be receiving payment (via check or direct deposit) to the Check Print Process (for checks), or to the Direct Deposit Creation Processes (FAPDIRD or FAPCDIR). This enables the checks/direct deposits to print by the partys name, in alphabetic order. Names on checks appear in the following format: Name Prefix, First Name, Middle Initial, Last Name Prefix, Last Name, Suffix (for example: Mr. Stephen L. Van Gibson, Jr.). Invoices which have not yet been posted cannot be selected for the check process. If there are no parameters on the Recurring Payables Form (FAARUIV), FABCHKS ignores the recurring invoice until those parameters are correctly established. If a Document Level invoice has one or more commodities on hold, FABCHKS will not select any portion of that invoice for checks. FABCHKS supplies the vendor name to the Check Print Process (FABCHKP). This enables the checks to print in vendor name order. While the Batch Disbursement Register Process (FABCHKR) lists checks in check number order by default, it is also in vendor name order since the check numbers were assigned by vendor name. Invoices for vendors on payment hold are excluded if there is no vendor hold override.
Note
An invoice with a check vendor on payment hold may still be selected for payment. Payment holds apply only to the invoiced vendor. Currency Conversion The following pertains to the printing of checks only, and not to direct deposit payments. The Batch Check Process (FABCHKS) prints a payments converted dollar amount as the check amount if currency conversion is being used and the payments Disbursing Agent indicator on the Invoice/Credit Memo Query Form (FAAINVE) is set to Y (Yes). For a given payment, if foreign currency is used and the payments Disbursing Agent indicator on the Invoice/Credit Memo Query Form (FAAINVE) is set to N (No), then the Batch Check process will print the currency on the check.
4-18
November 2010
Parameters
Name
Required?
Description
Values
No
System-generated via Job Submission Number of printed lines on a page. Used in business logic for both printed checks and for Direct Deposit disbursements. Default = 55
Number of Printed Lines Yes per Page 01 Check Selection Date No
4-19
November 2010
Receiving Matching Process (FABMATC)

Description
The Receiving Matching Process matches invoice information to receiving information. The report displays invoices that are completely matched, invoices awaiting receipts, and invoices that require further analysis in order for a match to be completed. The control parameters determine the processing of the Receiving Goods Form (FPARCVD) and the Invoice/ Credit Memo Form (FAAINVE). FABMATC uses the information entered into the documents and governs the actual payment of the invoice. The receiver document number is obtained from the Packing Slip Header Table (FPBRCDT). The Receiving Matching Process control parameters appear on the User Profile Maintenance Form (FOMPROF). Those invoices which have receiving data that is not in suspense will have the Complete indicator reset from R (Receipt required) to Y (Yes). If approvals are turned on for Invoices, the document will be forwarded to the Approvals in Process Table (FOBAINP) and will be processed according to the approval queue and routing criteria which apply. If approvals are not turned on for invoices, the document will be forwarded to the Approved Documents Table (FOBAPPD) to be processed in the next posting run. Those invoices which either do not have sufficient receiving quantities or which have receiving data that is in suspense will retain a status of R and be evaluated the next time the Receiving/Matching Process is run. There will be some invoices with no receiving information because the purchase was for something which was not formally received, like a service. Your site policy might be to create a packing slip document for the purchase. Alternatively, if there is no receiving information against a Purchase Order, the Invoice/Credit Memo Form (FAAINVE) enables you to enter the Quantity Accepted field to record that an item has been received for the purposes of completing the invoice. In some cases, there will be a timing issue. If the invoice has been processed in Accounts Payable before the goods have been received or processed, it might be an expediter's job to follow-up and ensure that the goods have been shipped from the vendor from which the receiving is performed. The invoices on the second and third sections of the report must be reviewed. The invoices being held up because of receiving information in suspense cannot be marked complete until the suspense condition is resolved or overridden. The invoices with insufficient or no receiving data will remain on the report until the receiving data is entered either because the goods finally arrived or by updating the invoice itself with the receiving information.
4-20
November 2010
You can run this process as often as local procedures can accommodate. It would be to your advantage to run it at least once prior to the posting run prior to the check run. This would ensure that all of the current matched invoices get posted and selected by the check process. There are three sections to this report.
Section One Section Two
Invoices Matched and Completed Receiving Analysis
Listing of invoices that have been matched and marked complete. Listing of invoices that are associated with receiving information which is in suspense. Typically, the quantity received exceeds the Receiving Tolerance amount. Listing of invoices that either have no receiving at all or the received quantity is less than the invoice approved quantity.
Section Three
Invoices Awaiting Receipts
Parameters
Name
Required?
Description
Values
No
4-21
November 2010
REPORT FABMATC
Development Receiving Matching Process Invoices Matched and Completed
PAGE: 1 RUN DATE: 01/18/1996 RUN TIME: 02:09 PM
VENDOR NUMBER 00010 00010 00011 00011
VENDOR NAME National Supplies, Inc. National Supplies, Inc. Office Furniture Warehouse Office Furniture Warehouse
INVOICE NUMBER I0000227 I0000229 I0000232 I0000237
INVOICE DATE 01/01/1996 01/01/1996 01/01/1996 01/01/1996
PAYMENT DUE DATE 01/31/1996 01/31/1996 01/31/1996 01/31/1996
APPROVED TOTAL 5000.00 5500.00 6000.00 6500.00
REPORT FABMATC
Development Receiving Matching Process Receiving Analysis
VENDOR NUMBER 00010 INVOICE NUMBER I0000112
VENDOR NAME National Supplies, Inc. INVOICE DATE 01/01/1996 PAYMENT DUE DATE 01/31/1996 APPROVED TOTAL 6000.00 PO NUMBER P0000545 PO ITEM 1 PO U/P 1000.0000 QUANTITY ORDERED 5.00 PREVIOUSLY QUANTITY INVOICED RETURNED .00 0.00 QUANTITY APPROVED 6.00 APPROVED U/P 1000.0000 QTY REJD .00
INV COMMODITY ITEM DESCRIPTION 1 Computer Software
RECEIVER DCMNT RDN22 INVOICE NUMBER I0000113 INVOICE DATE 01/03/1996 PAYMENT DUE DATE 01/31/1996 APPROVED TOTAL 4000.00 PO NUMBER P0000556 PO ITEM 1
PACKING SLIP HALPACK132A2
USER ID FIMSUSR
QTY RCVD 5.00
INV COMMODITY ITEM DESCRIPTION 1 Printer
PO U/P 2000.0000
QUANTITY ORDERED 2.00
PREVIOUSLY QUANTITY INVOICED RETURNED .00 .00
QUANTITY APPROVED 2.00
APPROVED U/P 2000.0000 QTY REJD .00
RECEIVER DCMNT RDN23
PACKING SLIP HALPACK132A3
USER ID FIMSUSR
QTY RCVD 2.00
4-22
November 2010
REPORT FABMATC
Development Receiving Matching Process Invoices Awaiting Receipts
VENDOR NUMBER 00010 INVOICE NUMBER I0000112
VENDOR NAME National Supplies, Inc. INVOICE DATE 01/01/1996 PAYMENT DUE DATE 01/31/1996 APPROVED TOTAL 6000.00 PO PO NUMBER ITEM P0000545 1 PAYMENT DUE DATE 01/31/1996 APPROVED TOTAL 4000.00 PO PO NUMBER ITEM P0000556 1 PO U/P 2000.0000 QUANTITY ORDERED 2.00 PREVIOUSLY QUANTITY INVOICED AVAILABLE .00 .00 QUANTITY APPROVED 2.00 APPROVED U/P 2000.0000 PO U/P 1000.0000 QUANTITY ORDERED 5.00 PREVIOUSLY QUANTITY INVOICED AVAILABLE .00 .00 QUANTITY APPROVED 6.00 APPROVED U/P 1000.0000
INV COMMODITY ITEM DESCRIPTION 1 Computer Software INVOICE NUMBER I0000113 INVOICE DATE 01/03/1996
INV COMMODITY ITEM DESCRIPTION 1 Printer
4-23
November 2010
1099 File Build Process (FAM1099)

Description
The FAM1099 process builds the IRS file and produces an audit report displaying summarized record counts and amounts reported in the IRS file. The report indicates the number of records (by record type) created on the 1099 tape, the number of payees, and the summary of amounts by distribution amount within income type (Non-employee Compensation, etc.). FAM1099 provides total dollar and record amounts. Refer to the online help for more information on the 1099 Income Type Maintenance Code Form (FTMITYP). FTMITYP contains the income type codes necessary for 1099 reporting. Income type codes are supplied in the seed data. Descriptions for the income type codes are standardized by the U. S. Government. Income types include:
Box 1 (rents) Should only print if >=600 Box 2 (Royalties) Should only print if >=10 Box 3 (Other income) Should only print if >=600 Box 5 (Fishing Boat) Any amount Box 6 (Medical and health care pmts) Should only print if >=600 Box 7 (non-employee compensation) Should only print if >=600
Box 8 (Substitute pmts in lieu of div/int) Should only print if >=10 Box 10 (Crop Insurance) Should only print if >=600 Box 13 (Excess Golden parachute pmts) Any amount Box 14 (Gross proceeds to an attorney) Any amount Box 15a (Section 409A Deferrals) Should only print if >=600 Box 15b (Section 409A Income) Any amount
4-24
November 2010
Parameters
Name
Required?
Description
Values
Reporting Year Prior Year Indicator
Yes No
Calendar 1099 reporting year Enter Y if you are reporting data for a previous tax year. Enter S to combine amount for rents and prizes over $599.99. The remaining amounts report separately. Enter C to combine amounts for rents, prizes, medical and health care benefits, and non-employee compensation. Based on the combined amount, the system determines whether a 1099 should be generated. The remaining amounts report separately.
YY Y = Yes N = No S C Separate amount Combine amount
Combine or Separate Amounts
Yes
Test/Correction/ Replacement
No
Type of file.
C T R
Correction Test Replacement
Blank Original Correction as of Date No Earliest date corrections were made to a vendor after the original 1099s were produced.
Note: Populate this parameter for correction runs only.
DD-MON-YYYY
Not used at this time Not used at this time Not used at this time
No No No
4-25
November 2010
Report Sample
REPORT FAM1099 REPORT YEAR 2005 Record Type count _____ COUNT records records records records records PAYEES 1 1 15 1 1 15 Total Distributions Rents Royalties Other Income Federal Income Tax Withheld Fishing Boat Proceeds Medical and Health Care Nonemployee Compensation Substitute Payments Crop Insurance Excess Golden Parachute Gross Proceeds for Legal Services Section 409A Deferrals Section 409A Income
Banner University 1099 Tape Summary Audit Report
RUN DATE: 10/05/2005 TIME: 10:04 AM PAGE: 1
____ TYPE T A B C F
______ AMOUNT
AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT AMOUNT
1 2 3 4 5 6 7 8 A B C D E
10,300.01 20,000.02 36,100.03 81,423.53 50,599.05 60,899.06 443,693.65 80,000.08 100,609.11 130,020.13 140,030.13 152,383.15 152,420.14
4-26
November 2010
Purchase Card Transactions Process (FAPCARD)

Description
The Temporary Purchase Card Transaction Table (FATCARD) is populated before the Purchase Card Transactions Process (FAPCARD) is run. FATCARD receives daily PCard transactions. These data can contain several summary records for each company/campus representing different posting days. For a diagram of the FAPCARD process flow, refer to Chapter 2, Processing. The FAPCARD process includes four steps.
1. Perform edits on FATCARD data
The first set of functions performs sum and duplication edits on the data found in FATCARD. Transaction totals received from the bank are compared (Record Types 1 and 2). The resulting totals are expected to be equal. The control file's company codes and bank post dates are then compared against previously fed information to ensure there are no duplicates. If sum or duplication errors exist, an error report is written. You must call the bank in question about the problem. All records in FATCARD for the System ID being processed must be removed. If no summary or duplication errors exist, the Purchase Transaction Fed Control Table (FABFEDC) is updated and the process continues.
2. Generate a liability journal voucher
The second part of this process performs an extrapolation of FOAPAL for each card transaction, summarizes by company or campus the amount of transactions being processed, and generates a liability Journal Voucher as indicated on the FTVSDAT record. The Transaction Date is the Processing Date (SYSDATE).
3. Populate PCard invoice tables
The process populates the FABINVT and FARINVT tables. Two key dates are used: Feed Sweep Date. Date used to determine when invoices should be pulled and fed into Banner Finance. The purpose of this date is to provide the account managers with enough time to perform edits. This date is based on the date the bank flat file was processed plus the user-defined lag days defined in the FTVCARD table. (The feed sweep date becomes the Invoice Transaction posting date for Banner Finance.)
4-27
November 2010
Payment Due Date. Date based on the payment cutoff date in the Payment Cutoff Schedule (FTMPCSH) plus the specified number of cycle days defined in the FTVSDAT table.
4. Send notification via GUAMESG to the account manager defined on the Purchase Card Maintenance Form
(FTMCARD).
Parameters
Name
Required?
Description
Values
System ID
Yes
System ID used to process records in the Temporary Purchase Card Transaction Table (FATCARD). System date and time in one of the following formats: YYYYDDMMHHMMSS YYYYDDMM
Any valid system ID
System Date Time Stamp
No
Any valid system date and time
Duplicate Override? (Y/N)
Yes
Indicator that lets you continue processing if duplicate data are found.
Y N
Yes No
4-28
November 2010
17-JAN-2002 03:47:36 PM
Development Load of Purchase Card Interface Transactions AS OF 17-JAN-2002
PAGE 1 FAPCARD
SYSTEM ID: FAPCARD SYSTEM TIMESTAMP: 20020117040404 CARD TYPE: MC CAMPUS 5301 POST DATE 13-JAN-2002 TOTAL AMOUNT 253723.00 ------------253723.00 COUNT SUM AMOUNT 10 253723.00 ---- ------------10 253723.00 SUM COUNT 10 ---10 MESSAGE Counts and Amounts match successfully
REPORT TOTALS: DUPLICATE STATUS CAMPUS POST DATE 5301 13-JAN-2002 BATCH STATUS:
OVERRIDE N
DUPLICATE STATUS No duplications found
FATCARD File successfully processed.
17-JAN-2002 03:47:36 PM
Development Load of Purchase Card Interface Transactions AS OF 17-JAN-2002 * * * REPORT CONTROL INFORMATION * * *
PAGE 2 FAPCARD
System ID: FAPCARD System Timestamp: 20020117 Duplicate Override Indicator: N Number of records processed: 10
4-29
November 2010
Canadian Direct Deposit Tape Process (FAPCDIR)

Description
This process, for Canadian institutions, enables you to create a file of direct deposit transactions to send to your bank/clearing house. The file can be saved as a flat file on disk or other media (tape). The Canadian Direct Deposit Tape Process (FAPCDIR) will review the system for direct deposit payments. The process will then create batches of records, following Canadian Payment Association (CPA) standard record formats. The resulting file can then be sent to the bank/clearing house for processing.
Note You must run the Batch Check Process (FABCHKS) before running the Canadian Direct Deposit Tape Process (FAPCDIR).
Parameters
Name
Required?
Description
Values
Bank Code
4-30
November 2010
Direct Deposit File Creation Process (FAPDIRD)

Description
This process enables you to create a file of direct deposit transactions that you will send to your bank/clearing house. The file can be saved as a flat file on disk or other media (tape). The Direct Deposit File Creation Process (FAPDIRD) will review the system for payments to be made via direct deposit. The process will then create batches of records, following National Automated Clearing House Association (NACHA) standard record formats. The resulting file can then be sent to the bank/clearing house for processing. You must run the Batch Check Process (FABCHKS) before running the Direct Deposit Creation Process (FAPDIRD). FAPDIRD edits International ACH Transactions (IATs) to ensure that all mandatory fields are complete before transactions are written to the direct deposit tape file. Error messages are written to the .log file and must be corrected before the direct deposit transactions are written to the .lis file. Refer to a description of the error messages below.
Note All IATs must be error-free before FAPDIRD creates the ACH deposit tape. The .lis file is empty if there are errors.
4-31
November 2010
Error Message
Cause
Solution
Undefined ACH Transaction Type in GXADIRD for Bank Routing <number>, Account <number>. Undefined ACH Transaction Type <xxx> for AR refunds in GTVSDAX (Code= ARACHTRAN).
The ACH transaction type on the Direct Deposit Recipient Form (GXADIRD) is either missing or no longer valid. There are two possible causes for this error. The default ACH transaction type defined on the Crosswalk Validation Form (GTVSDAX) for Accounts Receivable refunds (ARACHTRAN) is invalid. The institution has not properly defined a default ACH transaction type on GTVSDAX for Accounts Receivable refunds (ARACHTRAN). The ACH transaction type is still UPDATE_ME.
Access GXADIRD for the check vendor or vendor. Select the bank account indicated in the message. Ensure that a valid ACH transaction type is entered. Access GTVSDAX. Complete the default ACH transaction type by updating the external code to a valid value. The delivered value UPDATE_ME is not a valid ACH transaction type code.
Missing institution street address. Check Installation Controls form GUAINST. Missing institution Nation and/or Zip Code. Check Installation Controls form GUAINST.
The institutional address on Access GUAINST. Ensure the Installation Controls that at least one street Form (GUAINST) is address line is entered. incomplete. The institutional address on Access GUAINST. Ensure GUAINST is incomplete. that the nation and/or ZIP code is entered.
4-32
November 2010
Error Message
Cause
Solution
Missing ACH Information for the bank <xx>.
The ACH origination information on the Bank Code Rules Form (GXRBANK) is incomplete for the bank code listed. There are two possible causes for this error. On GXADIRD, the recipient has an IAT address override. An incomplete address was selected for the recipient, based on the GXADIRD address override. There is no IAT address override on GXADIRD, and the invoiced check vendor address or vendor address is missing street information.
Access GXRBANK. Navigate to the Immediate Destination Information block. Complete the Origin Name and Originating Bank Routing Number fields. Access the Vendor Maintenance Form (FTMVEND) for the check vendor or vendor. Navigate to the Address window. Select the address type and sequence indicated in the message. Enter the address line information.
Address <xx-xx> is missing street address. Check Vendor Maintenance form FTMVEND.
4-33
November 2010
Error Message
Cause
Solution
Address <xx-xx> is missing Nation and/or Zip Code. Check Vendor Maintenance form FTMVEND.
There are two possible causes for this error. On GXADIRD, the recipient has an IAT address override. Both the Nation and ZIP code are missing in the address selected for the recipient, based on the GXADIRD address override. There is no IAT address override on GXADIRD, and the invoiced check vendor address or vendor address is missing both Nation and ZIP code.
Access FTMVEND for the check vendor or vendor. Navigate to the Address window. Select the address type and sequence indicated in the message. Enter the nation and/or ZIP code.
4-34
November 2010
Error Message
Cause
Solution
Address Type <xx> defined There are two possible in GTVSDAX causes for this error. (Code=xxIATADDR) does On GTVSDAX, a default not exist for the vendor. IAT address hierarchy (APIATADDR or ARIATADDR) is defined. The recipient does not have an active address of the type that was selected, based on the hierarchy. The institution has not properly defined a default IAT address hierarchy on GTVSDAX (APIATADDR or ARIATADDR). The address type code is still UPDATE_ME.
There are two possible solutions: Access FTMVEND for the check vendor or vendor. Navigate to the Address window. Select the address type indicated in the message. Ensure that the recipient has an active address of this type. Access GTVSDAX. Complete the address hierarchy by updating the external code to a valid value. The delivered UPDATE_ME value is not a valid address type.
4-35
November 2010
Error Message
Cause
Solution
Address <xx-xx> does not exist. Check GXADIRD for Bank Routing <number>, Account <number>.
On GXADIRD, the recipient has an IAT address override. The recipient has an inactive or missing address, based on the address override.
Access FTMVEND for the check vendor or vendor. Navigate to the Address window. Select the address type and sequence indicated in the message. Ensure that the recipient has an active address for the address override entered on GXADIRD. There are two possible solutions: Access GXADIRD for the vendor. Select the bank account indicated in the message. Enter a valid IAT address override. Consider if a default IAT address hierarchy (APIATADDR) is appropriate. (The same hierarchy applies to both Prenote and active accounts.)
Missing Address in GXADIRD for Prenote with Bank Routing <number>, Account <number>.
The Prenote does not have an address associated with the recipients bank account. This occurs when both of the following conditions are true: The recipient does not have an IAT address override on GXADIRD. A default IAT address hierarchy (APIATADDR) is not defined on GTVSDAX.
Parameters
Name
Required?
Description
Values
Debit transaction 27 required?
Yes
If this transaction is valued to Y(es), FAPDIRD creates the 627 record for total debits in the FAPDIRD.lis output. With the creation of this record, the file can be sent to an originating bank that differs from the destination bank.
N Y
No (default) Yes
4-36
November 2010
Invoice Feed Process (FAPINVT)

Description
The Invoice Feed Process moves invoice transactions directly from the PCard Transaction Interface tables (FABINVT/FARINVT) into the invoice tables (FABINVH, FARINVC, and FARINVA). For a diagram of this process, refer to Chapter 2, Processing. PCard invoices FARINVT and FABINVT are selected based on a parameter-driven feed date, and include the following functions. Run on demand. Generate an invoice document number from FOBSEQN, where the prefix is set to S. Feed records from FABINVT/FARINVT into tables FABINVH/FARINVC/FARINVA based on a feed date parameter. Feed one-time vendors. Use Invoice Approvals Process (optional). (This is defined on the System_ID record in SDAT.) Feed a Payment Due Date and Invoice Date. Feed Zero Payment vouchers. Feed multiple accounting line distributions. Feed Check Vendor. Update the PCard Invoice Table (FABINVT) with the generated invoice document number and mark the transaction as being (F)ed.
Note Do not run this process if the Purchase Card Transactions Process (FAPCARD) was run with an option of S, as shown in the following chart. The S option generates a journal voucher with a debit to the incoming source expense from FTVCARD, a credit to the source fund, and a liability account found on the System Data Validation Form (FTVSDAT) defined by campus/company. The full FOAPAL must be defined on FTVCARD and used as is.
4-37
November 2010
Column Name Entity/Usage Code (FTVSDAT_Sdat_Code_Entity) Attribute Code (FTVSDAT_Sdat_Code_Attr) Optional Code #1(FTVSDAT_Sdat_Code_Opt_1) Title (FTVSDAT_Title) Short Title (FTVSDAT_Short_title) Data (FTSDAT_Data)
Value
FAPCARD SYSTEM_ID FAPCARD Purch Code Purch Card S
Parameters
Name
Required?
Description
Values
System Id Feed Sweep Date Bank Code
Yes Yes Yes
System Identifier Date used to determine when invoices should be pulled and fed into Banner Finance. Code used to identify the bank. The value of this field is included in both the invoice header and accounting records. Date used for the invoice header transaction date and for calculating the fiscal period for the accounting records.
Any valid System ID Any valid date in YYYYMMDDHHSS format Any valid two-character bank code. If not valued, defaults to a value from the fund. Any valid date. If not valued, will default to the value of the Feed Sweep Date.
Transaction Date
No
4-38
November 2010
Report Sample
* * * REPORT CONTROL INFORMATION - FAPINVT - Current Release 5.4 * * * REPORT : FAPINVT Development Invoice Feed Process FAPINVT 15-JAN-2002 U1 RUN DATE : 15-JAN-2002 RUN TIME : 02:26:51
System ID : Feed Sweep Date : Bank Code :
4-39
November 2010
Direct Deposit Transmittal Register Process (FAPTREG)

Description
This process enables you to create a listing of the summary control totals for the transactions contained in the Direct Deposit File. The register should be sent to your bank/clearing house, along with the Direct Deposit File. Some of the information that will appear on the register include: Company Name, Dollar Amount, Date of Transmission, and Hash totals.
Note Before running the Direct Deposit Transmittal Register Process (FAPTREG), you must run either the Direct Deposit File Creation Process (FAPDIRD), or the Canadian Direct Deposit File Creation Process (FAPCDIR).
Parameters
Name
Required?
Description
Values
Direct Deposit Date Bank Code
Yes Yes
Date as entered in the Batch Check Print Form (FAABATC). Code for the bank entered in the Batch Check Print Form (FAABATC).
DD-MON-YYYY
4-40
November 2010
Bank Reconciliation - Activity Aging Report (FARAAGE)

Description
This is a report of outstanding checks and deposits, displayed as outstanding activity in 30 day periods from less than one month to over 120 days.
Parameters
Name
Required?
Description
Values
Standard Date, DD-MON-YYYY Check Bank
Yes Yes
Reconciliation date for this report (i.e., from this date back). Check bank code for the reconciliation.
DD-MON-YYYY
Report Sample
REPORT FARAAGE BANK: 03 Third National Bank ACCOUNT: 16-1200-03-9874
Development Bank Reconciliation - Activity Aging As of 04/23/1996
DEPOSITS: CHECKS:
<----------------------------- OUTSTANDING ACTIVITY AGING ANALYSIS -----------------------------> UP TO 30 DAYS 31 TO 60 DAYS 61 TO 90 DAYS 91 TO 120 DAYS OVER 120 DAYS --------------------------------------------------------------------------------$100.00 $.00 $386.82 $169.35
TOTAL OUTSTANDING ----------------$100.00 $556.17
4-41
November 2010
Bank Reconciliation Balance Report (FARBBAL)

Description
FARBBAL is a hard copy report of the bank reconciliation.
Parameters
Name
Required?
Description
Values
Recon. Date, DD-MON-YYYY Bank Code Balance
Yes Yes No
Reconciliation date for this report; (i.e., from this date back). Bank code for the reconciliation. Suggested (expected) balance amount.
MM-DD-YYYY
Report Sample
REPORT FARBBAL BANK: 03 Third National Bank ACCOUNT: 16-1200-03-9874
Development Bank Reconciliation Balance As of 05/02/1996
BEGINNING GENERAL LEDGER BALANCE ADD: OUTSTANDING CHECKS MISC. CASH DISBURSEMENTS TOTAL CREDITS LESS: DEPOSITS IN-TRANSIT MISC. CASH RECEIPTS TOTAL DEBITS CURRENT BALANCE BALANCE PER BANK STATEMENT UNRECONCILED AMOUNT $556.17 $.00 ----------------$556.17 $100.00 $.00 ----------------$100.00
$28.06
$556.17
$100.00 ----------------$484.23 $.00 ----------------$484.23
4-42
November 2010
Bank Reconciliation Report (FARBREC)

Description
FARBREC provides a hard copy report of bank reconciling items. If the bank tape contains checks which have cleared after the date entered in the Reconciliation Date Parameter, these checks will be treated as not having cleared. If a check has been cancelled after the date entered in the Reconciliation Date Parameter, it will still display as a current check. If a bank mistakenly sends the same check number twice, Bank Reconciliation will reconcile the first occurrence of that check but will leave the other occurrence as an unreconciled item. Refer to the online help for detailed information on the Bank Tape Reconciliation Form (FAABREC).
Parameters
Name
Required?
Description
Values
Reconciliation Date Bank Code Type of Reconciliation
Yes Yes No
Reconciliation date for this report (i.e., from this date back). Bank code for the reconciliation. Type of reconciliation options.
MM-DD-YYYY
F R
Final reconciliation Regular reconciliation
4-43
November 2010
Check Register Report (FARCHKR)

Description
FARCHKR lists checks by check number and date for a specific date range. This report sorts by bank code, check number, and vendor name. The Check Register displays vendor/payee name, corresponding invoice numbers, and check amounts. In addition, it displays vendor check totals, invoice totals, and a total amount of each bank. Populate the From Range Date and the To Range Date parameters to print a cumulative check report. FARCHKR prints cancelled checks if the check cancellation date is less than the date specified in the Range of Dates parameters. If, however, the check was cancelled after the reporting period, it will display as not cancelled. For a given invoice, if foreign currency is used and the Disbursing Agent Indicator on FAAINVE is set to N (No), FARCHKR prints the currency description on the check register (for example, French Francs). One-time vendor information is included.
Note A vendor number does not display in the Payee/Vendor Number column for one-time vendors.
Parameters
Name
Required?
Description
Values
From Range Date, DD-MON-YYYY To Range Date, DD-MON-YYYY Bank Code Report layout option [A/V]
Yes Yes No No
Beginning date of the check register. End date of the check register. Bank code for the specific bank. Code that determines how the report output is displayed.
DD-MON-YYYY DD-MON-YYYY Any valid bank code. A V Accounting Distribution (default value) Vendor Invoice Layout
4-44
November 2010
REPORT FARCHKR FISCAL YEAR 96 BANK: T1 First National Bank CURRENCY: UNITED STATES DOLLARS
Development Check Register From 01/01/1996 To 04/01/1996 <--- INVOICE NUMBER ---> VENDOR'S INTERNAL --------------- -------RLOONE43 RLOONE44 RLOONE60 RLOONE61 RLOONE62 RLOONE63 RLOONE80 RLOONE81 RLOONE82 RLOFRM30 I000784 PJC00041
CHECK PAYEE/VENDOR NUMBER DATE NUMBER NAME ----------------- ---------------------------------------R5555552 02/20/1996 00005 Mail Order LAB Equipment R5555553 02/20/1996 R6666660 02/20/1996 R6666661 02/20/1996 R6666662 02/20/1996 R6666663 02/20/1996 R8888880 02/20/1996 R8888881 02/20/1996 R8888882 02/20/1996 R9999999 02/21/1996 S1111111 01/17/1996 S1111112 01/17/1996 00012 00009 00005 00005 National Good Line Inc. AutoCorp Mail Order LAB Equipment Air Corp Mail Order LAB Equipment Oxford Computer Inc. VIP Computer Inc. VIP Computer Inc. National Laboratory Supplies ABC Office Supplies Limited
FUND -----1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 103000
ORGN -----215 215 215 215 215 215 215 215 215 215 215 120
ACCT -----6310 6310 6310 6310 6310 6310 6310 6310 6310 6310 6310 6010
PROG CHECK AMOUNT ------ -------------620 1,200.00 620 620 620 620 620 620 620 620 620 620 620 100.00 100.00 120.00 200.00 200.00 100.00 100.00 200.00 110.00 1,100.00 10.00
PC1111111 Ace Hardware Service
4-45
November 2010
REPORT FARCHKR FISCAL YEAR 96 BANK: T1 First National Bank CURRENCY: UNITED STATES DOLLARS CHECK NUMBER DATE ----------------S1111113 01/17/1996 S1111114 01/17/1996 S1111115 01/17/1996 S1111116 01/17/1996 S1111117 01/17/1996 S1111118 01/17/1996
(cont.)
Development Check Register From 01/01/1996 To 04/01/1996
PAYEE/VENDOR <--- INVOICE NUMBER ---> NUMBER NAME VENDOR'S INTERNAL ---------------------------------------- --------------- -------PC1111111 Ace Hardware Service PC1111111 Ace Hardware Service PC1111111 Ace Hardware Service PC1111111 Ace Hardware Service PC1111111 Ace Hardware Service 00012 National Laboratory Supplies PJC00031 PJC00042 PJC00043 PJC00044 PJC00045 I0000001
FUND -----103000 103000 103000 103000 103000 1000
ORGN -----120 120 120 120 120 215
ACCT -----6010 6010 6010 6010 6010 6310
PROG CHECK AMOUNT ------ -------------620 620 620 620 620 620 55.00 1.00 1.00 11.00 16.50 1,100.00
T0000002 02/26/1996 T0000003 03/01/1996
Voided Check Voided Check
T0000010 03/01/1996
00001 00016 00001 00016
Laboratory Supplies Inc. Fitzpatrick Davies Brown CPA Laboratory Supplies Inc. Fitzpatrick Davies Brown CPA
GLIN2191
1000
220
6111
620
500.00
T0000011 03/01/1996
GLINV219
1000
220
6111
620
1,000.00
UNITED STATES DOLLARS BANK TOTAL
============== 6,224.50
4-46
November 2010
Cash Requirements Report (FARCSHR)

Description
This report displays, by bank code and name, predicted cash requirements for an installation's bank(s) based on payment due dates.
Parameters
Name
Required?
Description
Values
As of Date
Yes
Date to select data for reporting.
DD-MON-YYYY Default = current date
First Range Number of Days Second Range Number of Days Third Range Number of Days
No No No
Number of days for the first range. Number of days for the second range. Number of days for the third range.
0-99 0-99 0-99
4-47
November 2010
REPORT FARCSHR FISCAL YEAR 96
Development Cash Requirements Report As Of 05/03/1996
BANK NO NAME ---------------------------------T1 First National Bank
<------------------------------ AMOUNT TO BE PAID WITHIN ------------------------------> EXPIRED EXPIRED EXPIRED 10 DAYS DISCOUNT 20 DAYS DISCOUNT 30 DAYS DISCOUNT -------------- ----------------------- ----------------------- ---------$106.30 $10.00 $106.30 $10.00 $106.30 $10.00
REPORT FARCSHR FISCAL YEAR 96
Development Cash Requirements Report As Of 05/03/1996
BANK NO NAME ---------------------------------GRAND TOTAL
<------------------------------ AMOUNT TO BE PAID WITHIN ------------------------------> EXPIRED EXPIRED EXPIRED 10 DAYS DISCOUNT 20 DAYS DISCOUNT 30 DAYS DISCOUNT -------------- ----------------------- ----------------------- ---------$106.30 $10.00 $106.30 $10.00 $106.30 $10.00
4-48
November 2010
Batch Direct Deposit Advice Print Process (FARDIRD)

Description
This process enables you to print direct deposit remittance advice forms. The advice form can be sent to the party who will be receiving payment by direct deposit. The printing of direct deposit advices is not required. You must run the Direct Deposit File Creation Process (FAPDIRD) or the Canadian Direct Deposit Tape Process (FAPCDIR) before running the Direct Deposit Advice Print Process (FARDIRD).
4-49
November 2010
Invoice Aging Report (FARIAGE)

Description
This report provides an aging of open invoices from 30 to 120 days and over. This aids in the management of the Accounts Payables process.
Parameters
Name
Required?
Description
Values
As of Date
Yes
Report Sample
REPORT FARIAGE
Development Invoice Aging Report As Of 05/08/1996
INVOICE DATE -------10/26/1989 10/27/1989
VENDOR/PAYEE PAYMENT <---------------------- AMOUNT OVER ----------------------> NUMBER NAME INVOICE DUE DATE 30 DAYS 60 DAYS 90 DAYS 120 DAYS IND ---------------------------------------- -------- -------- -------------- -------------- -------------- -------------- --350000002 Energy System 310000002 BANNER CORP. 389000001 Spellman, Sam J. 310000002 BANNER CORP. I0000005 10/26/1989 I0000010 10/27/1989 F1 10/27/1989 S1 10/27/1989 I0000012 10/30/1989 TOTAL $2,345.00 $13,000.00 $375.00 $62.50 $250,000.00 ============== ============== ============== ============== $.00 $.00 $.00 $265,782.50 H H
10/30/1989
4-50
November 2010
Invoice Activity Report (FARINVA)

Description
The Invoice Activity Report enables you to print detail and summary invoice activity information for a specified period of time, bank vendor, or user. This report gathers the total amount of invoices processed by each person during the specified time period, as well as the total amount of invoices processed on each day during the specified time period, and the total amount of invoices by bank code during the specified period of time. This report enables you to: Obtain a listing and total amount of all invoices by bank code during a specified time period Obtain a listing and total amount of all invoices for a particular vendor during a specified time period Obtain a listing and total amount of all invoices for and processed by a specific individual during a specified time period
Parameters
Name
Required?
Description
Values
From Invoice Activity Date
Yes
Beginning of a time period for which the invoice activity information will be printed. This field is mandatory and cannot be left blank. Ending of a time period for which the invoice activity information will be printed. This field is mandatory and cannot be left blank. Code used to identify banks. Populating this parameter will limit this report to one bank. User identification code. Populating this parameter will limit the report to one user. Vendor identification code. Populating this parameter will limit the report to one vendor.
DD-MON-YYYY
To Invoice Activity Date Yes
DD-MON-YYYY
Bank Code User ID Vendor ID
No No No
4-51
November 2010
Report Sample
FARINVA 3.0 FISCAL YEAR 96 BANK SL First National Bank
Development Invoice Activity Report 18-OCT-1995 through 20-OCT-1995
08-NOV-1995
03:44:48 PM PAGE: 1
ACTIVITY USER ID DATE __________________ ________ FIMSUSR 10/19/1995
VENDOR/PAYEE NUMBER NAME ________________________________________ 00010 LAB Corporation
DUE DATE ________
INVOICE NUMBER DATE ________ ________
INVOICE AMOUNT ______________
ST __ O O O
C A _ _ N N N N N N
H/S/C _____ N N Y N N Y N N Y
10/18/1995 I000100 10/19/1995 I0000100 10/19/1995 I0000101
10/18/1995 $321.59 10/19/1995 $533.18 10/19/1995 -$533.18 -------------TOTAL DATE $321.59
10/20/1995
00010
LAB Corporation
10/20/1995
I0000896 10/20/1995 $1,151.00 -------------TOTAL DATE $1,151.00 TOTAL USER TOTAL BANK -------------$1,472.59 ============== $1,472.59
N N
N N N
4-52
November 2010
Invoice Selection Report (FARINVS)

Description
This report displays the invoices which will be paid on the next check run based on payment due dates. This report sorts by bank code and includes invoice amount and check amount for each vendor, as well as the total bank invoice amount and check amount. The discount amount is deducted from the invoice amount regardless of the number of remaining discount days. State and Federal taxes are deducted from the check amount if the invoice's 1099 Indicator is set to Y. The invoice amount is the net amount found on the Invoice/Credit Memo Query Form (FAIINVE). The check amount is the dollar amount to be used by the Check Printing Process FABCHKP. One-time vendor information is included.
Note A vendor number does not display in the Payee/Vendor Number column for one-time vendors.
Invoices for vendors on payment hold are excluded if there is no vendor hold override.
Note
An invoice with a check vendor on payment hold may still be included. Payment holds apply only to the invoiced vendor. This report selects and prints invoices for specified bank codes. By allowing you to specify bank codes, this report can be used to select and print invoices that appear in the next check run which can be run for one bank code at a time. If no bank code is specified, then all invoices will be selected and printed as normal, regardless of the bank code.
Parameters
Name
Required?
Description
Values
Next Check Run, DD-MON-YYYY Bank Code
Yes
Date for the next check run. This date identifies invoices that will be paid in the next check run. If this parameter is blank, the current date is used. Code used to identify banks. Populating this parameter will limit this report to one bank.
DD-MON-YYYY
No
4-53
November 2010
Report Sample
REPORT FARINVS BANK 01 VENDOR/PAYEE NUMBER NAME
Development Invoice Selection Report Next Check Run: 01/01/1996 DUE DATE -------06/07/1996 05/31/1996 INVOICE NUMBER DATE -------I0001178 I0001276 -------05/07/1996 05/21/1996 INVOICE AMOUNT -------------$1,000.00 $2,143.36 -------------$3,143.36 $150.00 $5.00 $20.00 $30.00 $8.10 $22.50 $14.40 $2.00 $13.00 $200.00 $100.00 $100.00 $45.00 $100.00 $.90 $1.80 $2.70 -------------$610.40 $20.00
RUN DATE: 08/19/1996 TIME: 12:48 PM PAGE: 1 CHECK AMOUNT -------------$1,000.00 $2,143.36 -------------$3,143.36 $150.00 $5.00 $20.00 $30.00 $8.10 $22.50 $14.40 $2.00 $13.00 $200.00 $100.00 $100.00 $45.00 $100.00 $.90 $1.80 $2.70 -------------$610.40 $20.00
----------------------------------------00009 ABC Office Supplies Limited TOTAL VENDOR Ace Hardware Service Allen, Roberta, Marie. Arnold, Hap 817856001 00006 Capriotti, June Computer Warehouse
08/11/1996 09/10/1996 07/31/1996 08/13/1996 05/30/1996 05/31/1996 06/06/1996 07/05/1996 05/31/1996 06/10/1996 06/10/1996 06/10/1996 07/02/1996 06/30/1996 05/23/1996 05/25/1996 05/25/1996
PJC00052 S0000054 S0000052 S0000125 HAL00031 HAL00032 HAL00035 HAL00037 HAL00041 HAL00042 HAL00043 HAL0004A HALCA001 HALCA01A I0001209 I0001226 I0001227
08/11/1996 09/10/1996 07/31/1995 08/13/1996 05/20/1996 05/21/1996 05/27/1996 06/04/1996 05/21/1996 06/05/1996 06/05/1996 06/05/1996 06/22/1996 06/22/1996 05/13/1996 05/15/1996 05/15/1996
TOTAL VENDOR 159489559 Gibson, Stephen, L. 12/24/91 S0000067 12/24/91
4-54
November 2010
Invoices Awaiting Receiver Report (FARIREC)

Description
This report lists invoice, commodity, and receiving information for invoices awaiting the final receiving/matching process. Invoice data includes invoice number, invoice date, and payment due. Commodity data includes commodity item and amount due. Receiving data includes the purchase order and packing slip number. The receiver document number is obtained from the Packing Slip Header Table (FPBRCDT). Invoices that have had their Complete Indicator set to Y and are required display an R upon requery in the Complete Indicator field. The R identifies that the invoice is awaiting the receiving/matching process. The R is updated to Y by the system when the Invoice/Receiving Matching Process is complete for that invoice.
Parameters
Name
Required?
Description
Values
Vendor Code
No
Vendor code for which you want to list outstanding invoices. More than one vendor code may be entered. Invoice records with a payment due date that is less than or equal to date specified will be retrieved. Default is the current date which will retrieve all invoices awaiting the Invoice/Receiving Matching Process. DD-MON-YYYY Default = current date
Payment Due As of Date No
4-55
November 2010
Report Sample
FARIREC
Development Invoices Awaiting Receiver Report As Of 25-OCT-1996 INVOICE DATE ----------23-JUN-1996 PAYMENT ITEM NET DUE DATE NUM AMOUNT DUE ----------- ---- ---------------03-JUL-1996 1 163.43 ================ VENDOR TOTAL 163.43 1 227.07 ================ VENDOR TOTAL 227.07 1 834.44 ================ VENDOR TOTAL 834.44 TGKP0504 TGKP0503
25-OCT-1996 09:57 AM PAGE: 1
VENDOR/PAYEE INVOICE NUMBER NAME NUMBER ----------------------------------------- --------00006 Computer Warehouse TGKI0502
PO RECEIVER PACKING NUMBER DOCUMENT SLIP -------- -------- --------------TGKP0502
00006
Computer Warehouse
TGKI0503 23-JUN-1996 03-JUL-1996
00006
Computer Warehouse
TGKI0504 23-JUN-1996 03-JUL-1996
4-56
November 2010
Open Invoice Report (FAROINV)

Description
The Open Invoice Report provides details of the invoices and credit memos that were/are open based on the As of Date selected by the user. When the report is executed using an As of Date prior to the current system date, the invoices or credit memos displayed will include any subsequent check information as well as any cancelled invoice, credit memos, and/or checks. When necessary, the report appropriately displays the amount of taxes not paid to the vendor (indicated when the TAXL code appears in the SRCE column rather than the INVC code) along with the invoice amount. The report includes invoices and credit memos that are open based on the As of Date entered by the user. Invoices or credit memos that are paid as of the current date but were open based on the As of Date are also included with the related check information provided. As well any invoices or credit memos that have been cancelled as of the current date but were open based on the As of Date are provided. An invoice may appear several times on the report showing its various iterations when the invoice itself or subsequent checks have been cancelled and reestablished or when the invoice includes taxes not paid to the vendor (TAXL). When invoices are reported more than once based on the As of Date entered by the user, it is important to look at the check number, check date, cancel date and/or source information to correctly evaluate the current status of the invoice document and its amount. Due to known issues related to maintenance of transaction history for recurring payables, this report will only reflect the first submission of a recurring invoice and its related activity. Subsequent submissions will not be included in the report regardless of payment status for the As of Date entered. The Cancel Date column on the report serves two purposes. When an invoice has been paid and the subsequent check cancelled (with or without reestablishing the invoice) then this date reflects the check cancellation date. If the invoice has not been paid and the invoice itself has been cancelled (with or without reestablishing the invoice), then this date reflects the date of the invoice cancellation. There are several issues of note when the report generated contains data for invoices that have been cancelled and reestablished. There are two mechanisms for canceling and reestablishing invoices. If the invoice has not been paid, the invoice may be cancelled with or without reestablishment on the Invoice/Credit Memo Cancellation Form (FAAINVD). If the invoice has been paid then the invoice may be cancelled with or without reestablishment on the Check Cancellation Form (FAACHKS). The issues outlined below regarding cancellation and reestablishment are the same for either mechanism unless stated specifically. When an invoice is cancelled with a cancellation transaction date greater than the invoices original transaction and reestablished invoice is re-completed and re-posted with the same transaction date as the original posting, the invoice will appear twice as of that date. For example, an invoice is posted with a
4-57
November 2010
transaction date of 01/02/2000 and is cancelled and reestablished on 01/10/2000. The user then recompletes and re-posts the invoice leaving the transaction date of 01/02/2000. When the Open Invoice Report is run as of 01/02/2000 the invoice will be listed twice once showing that it has been cancelled and once showing it has been reestablished and is awaiting payment. If the report is run as of 01/10/2000 the invoice will be reported only once as original iteration of the invoice is now cancelled as of 01/10/2000 and is no longer open. When an invoice has been paid and the check has been cancelled and the invoice reestablished the check amount will be used for the invoice amount as the invoice amount may be changed when the invoice is recompleted and re-posted. When a previously unpaid invoice is cancelled and reestablished, no amount will display in the invoice amount field as the invoice amount may be changed when the invoice is re-complete and re-posted. When an invoice has been cancelled the TAXL amount may not display if the invoice has been reestablished. The TAXL amount will only display when the invoice has not been reestablished or until the reestablished invoice is re-completed and re-posted. Once the reestablished invoice is re-complete and reposted the TAXL amount is overwritten with the amount for the new iteration of the invoice and therefore can no longer displayed the amounts for previous iterations of invoices.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date
Yes Yes
Chart of accounts for which you want to create a report. Date that specifies which invoices and credit memos DD-MON-YYYY you want to include in the report. Banner prints Default = system date information about invoices and credit memos that were open on the As of Date. Fund type you want to include in the report.
Fund Type Code
No
4-58
November 2010
Parameters (cont)
Name
Required?
Description
Values
Fund Option
No
Way you want to enter fund codes.
A R W S
Automatically enter all fund codes. (default value) Enter a range of fund codes. Search for specific fund codes using a wildcard. Enter specific fund codes.
From Fund To Fund Fund
First fund code in a series. Enter only if Fund Option = R. Last fund code in a series. Enter only if Fund Option = R. Fund codes that you would like to include in the report. Enter only if Fund Option = W or S. You may use a wildcard (%) if Fund Option = W.
4-59
November 2010
FAROINV 4.1
Banner University Open Invoice Report AS OF 16-NOV-1999 Banner University Unrestricted Current Education and General INVOICE I0000076 I0000078 I0000086 CM TRAN DATE INVOICE AMOUNT 11/16/99 11/16/99 11/23/99 600.00 300.00 100.00 -------------1,000.00 CHECK NUMBER CHECK DATE CANCEL DATE ORGN 11002 11002 11002
12/31/99 13:01:19 PAGE 1
COAS: FTYP: FUND: VENDOR
B 10 1110
ACCT 7210 7520 7210
PROG SRCE 10 10 10 INVC INVC INVC
National Supplies National Supplies National Supplies FUND Total: FUND: Office Office Office Office 1200 Max Max Max Max
Current Designated I0000082 I0000083 I0000084 I0000085 11/22/99 11/22/99 11/22/99 11/22/99 3,000.00 150.00 325.86 4,501.00 -------------7,976.86 -------------8,976.86 -------------8,976.86 11005 11005 11005 11005 7510 7210 7510 7510 10 10 10 10 INVC INVC INVC INVC
FUND Total: FTYP Total: Grand Total:
FAROINV 4.1
Banner University Open Invoice Report AS OF 16-NOV-1999 * * * REPORT CONTROL INFORMATION * * *
12/31/99 13:01:19 PAGE 1
PARAMETER SEQUENCE NUMBER: 14803 CHART OF ACCOUNTS: B AS OF DATE: 16-NOV-1999 FTYP: ALL FUND: 1110 FUND: 1200 NUMBER OF PRINTED LINES PER PAGE: 55
4-60
November 2010
Vendor Alphabetical Listing Report (FARVALP)

Description
This report lists vendors in alphabetical order. This report includes the vendor's contact information as well as Discount Code, Group Tax Code, and Tax ID. Vendor Type Codes are initially defined on the Vendor Type Code Maintenance Form (FTMVTYP). Discount codes are initially defined on the Discount Terms List Values Form (FTVDISC).
Parameters
Name
Required?
Description
Values
Vendor Type 1 Vendor Type 2 Vendor Type 3 Vendor Type 4 Vendor Type 5 Vendor Type 6 Vendor Type 7 Vendor Type 8 Vendor Type 9 Vendor Type 10 1099 Vendors only (Y/N) Vendor Grouping Indicator
No No No No No No No No No No No
Number one vendor type code selection Number two vendor type code selection Number three vendor type code selection Number four vendor type code selection Number five vendor type code selection Number six vendor type code selection Number seven vendor type code selection Number eight vendor type code selection Number nine vendor type code selection Number ten vendor type code selection Determines display of 1099 vendors only. Options are Y to display only 1099 vendors or N for a display that is not limited to 1099 vendors. Y N Yes No (default)
No
Determines vendor groupings. Options are 1 for one 1 or M vendor group selection or M for multiple vendor group selections.
4-61
November 2010
Report Sample
REPORT FARVALP
Banner University Vendor Alphabetical Listing
RUN DATE: 12/04/1996 TIME: 10:11 AM PAGE: 1 DISC CODE ----
VENDOR/ PAYEE NAME -----------------------------1099 Vendor - Income Type = NC
VENDOR/ PAYEE NO --------@00000166
CONTACT ------------------------------
VENDOR TYPES -----------------------------
GROUP TAX ID ----- --------1 1112
ADDRESS TYPE STREET 1/CITY - STATE - ZIP STREET 2/COUNTRY STREET 3/PHONE - EXTENSION ------------------------------ ------------------------------ ------------------------------ -----------------------------Mailing 1234 Any Street Smallville OH 11111 ABC Office Supplies Limited 00009 Pat Farrel SB 1
ADDRESS TYPE STREET 1/CITY - STATE - ZIP STREET 2/COUNTRY STREET 3/PHONE - EXTENSION ------------------------------ ------------------------------ ------------------------------ -----------------------------Billing 1 Kelly Drive Philadelphia PA 19103 United States of America 215-345-3187 Business 1 ABC Drive Philadelphia 477777777 Margaret Ternowchek PA 19103 United States of America 215-345-3187 1
Aaman Company, Limited
ADDRESS TYPE STREET 1/CITY - STATE - ZIP STREET 2/COUNTRY STREET 3/PHONE - EXTENSION ------------------------------ ------------------------------ ------------------------------ -----------------------------Billing 780 Smith Court Ambler PA 19033 Permanent Business 888 Abby Lane Chicago 111 Albion Way Aurora IL AK 60202 Andrews Hall 60202 Suite A1
4-62
November 2010
Vendor History Report (FARVHST)

Description
This report shows payment activity data for a vendor including check number, check date, invoice number and invoice date, PO number, invoice and check amounts, and vendor total. Vendor activity is displayed on a range of dates basis. One-time vendor information is included. Note that a vendor number does not display in the Payee/Vendor Number column for one-time vendors.
Parameters
Name
Required?
Description
Values
Start Date, DD-MON-YYYY End Date, DD-MON-YYYY
Yes No
Starting activity date from which you want to report. DD-MON-YYYY Ending activity date to which you want to report. Type of vendor. DD-MON-YYYY 1 2 3 Specific vendor One-time vendor All vendors
Vendor Selection Option No
Vendor Code
No*
Required only for specific vendors (that is, when Vendor Selection Option parameter is set to 1).
Any valid vendor code.
4-63
November 2010
Report Sample
REPORT FARVHST FISCAL YEAR 1996
Banner University Vendor History Report 01/01/1996 - 05/01/1996
RUN DATE: 08/19/1996 TIME: 12:35 PM PAGE: 1 PO NUMBER INVOICE AMOUNT -------- -------------$318.00 $318.00
VENDOR/PAYEE CHECK <--- INVOICE NUMBER ---> INVOICE NUMBER NAME BK NUMBER DATE VENDOR'S INTERNAL DATE ------------------------------------- -- -------- -------- --------------- -------- -------00006 Computer Warehouse US Allen, Roberta, Marie. T1 T1 US US P0000037 01/17/1996 S1111111 01/17/1996 E1113815 01/10/1996 E1113950 02/24/1996 I000784 I000784 01/10/1996 01/10/1996 E1113817 01/10/1996
CHECK AMOUNT --------------
I0000775 01/09/1996 P0000796
$1,100.00 $1,100.00 $1,100.00 $1,100.00 $10.00 $10.00 $70.00 $70.00 -------------$2,280.00
91INV022 12/04/1995 I0000908 02/24/1996
VENDOR TOTAL Arnold, Hap AA T1 T1 H0000001 03/02/1996 B0000002 01/18/1996 B0000003 01/18/1996 I0000837 01/16/1996 I0000679 12/11/1995 P0000742 I0000680 12/11/1995 P0000742
$100.00 $100.00 $270.00 $270.00 $400.00 $400.00 -------------$770.00
VENDOR TOTAL Houbson, Leslie US US E1113810 01/08/1996 E1113901 02/03/1996 I0000769 01/08/1996 I0000836 01/16/1996 P0000863 I0000845 01/17/1996 P0000863
$100.00 $100.00 -$50.00 $100.00 $50.00 -------------$150.00
VENDOR TOTAL
4-64
November 2010
Vendor Numerical Listing Report (FARVNUM)

Description
This report lists the vendors in numerical order by ID number. FARVNUM includes the vendor's contact information and Discount Code, Group Tax Code, and Tax ID.
Parameters
Name
Required?
Description
Values
Vendor Type 1 Vendor Type 2 Vendor Type 3 Vendor Type 4 Vendor Type 5 Vendor Type 6 Vendor Type 7 Vendor Type 8 Vendor Type 9 Vendor Type 10 1099 Vendors only
No No No No No No No No No No No
Number one vendor type code selection Number two vendor type code selection Number three vendor type code selection Number four vendor type code selection Number five vendor type code selection Number six vendor type code selection Number seven vendor type code selection Number eight vendor type code selection Number nine vendor type code selection Number ten vendor type code selection Determines display of 1099 vendors only. Options are Y to display only 1099 vendors or N for a display that is not limited to 1099 vendors. Y N Yes No (default)
Vendor Grouping Indicator (Y/N)
No
Determines vendor groupings. Options are 1 for one 1 or M vendor group selection or M for multiple vendor group selections.
4-65
November 2010
Report Sample
REPORT FARVNUM
Banner University Vendor Numerical Listing
RUN DATE: 12/04/1996 TIME: 10:26 AM PAGE: 1 DISC CODE ---01
VENDOR/PAYEE NUMBER NAME/CHECK NAME --------- -----------------------------00003 Mike & Sons Supplies
CONTACT -----------------------------Bill Burke
VENDOR TYPES ----------------------------MN
GROUP TAX ID ----- --------M
ADDRESS TYPE STREET 1/CITY - STATE - ZIP STREET 2/COUNTRY STREET 3/PHONE - EXTENSION ------------------------------ ------------------------------ ------------------------------ -----------------------------Business 456 Cambria Ave Philadelphia PA 19107 United States of America 215-754-4500 00004 Lydon's Chemistry Equipment Mitch Lydon 1
ADDRESS TYPE STREET 1/CITY - STATE - ZIP STREET 2/COUNTRY STREET 3/PHONE - EXTENSION ------------------------------ ------------------------------ ------------------------------ -----------------------------Business 2438 St. Vincent Street Philadelphia PA 19111 United States of America 215-342-1700 00005 Mail Order LAB Equipment Dennis Cowley 1
ADDRESS TYPE STREET 1/CITY - STATE - ZIP STREET 2/COUNTRY STREET 3/PHONE - EXTENSION ------------------------------ ------------------------------ ------------------------------ -----------------------------Billing 1450 Rodeo Drive Los Angeles CA 34567 United States of America 576-432-7831 243 Mailing 456 Topeka Blvd Ventura CA 34500 United States of America 987-390-9800
4-66
November 2010
1099 Reporting/Withholding Status Report (FARWHLD)

Description
This report indicates U.S. Federal Government and appropriate State Government withholding tax and reporting data by vendor for those purchases subject to the IRS 1099 form reporting requirements. Columns include amounts for reportable, withheld, and paid over to the taxing authority.
Parameters
Name
Required?
Description
Values
Reporting Year, (YY) As of Date, DD-MON-YYYY
Yes Yes
Calendar 1099 reporting year Date to select data for reporting.
YY DD-MON-YYYY Default = current date
REPORT FARWHLD REPORT YEAR 96
Banner Development Environment 1099 Reporting/Withholding Status Report As Of 08/10/1996
VENDOR/PAYEE RPT_ID NAME ----------------------------------------Alex R. Banta ABC Corporation Textile Corporation TOTAL ALL VENDORS
<--------- WITHHELD --------> <-------- PAID OVER --------> REPORTABLE FEDERAL STATE FEDERAL STATE BALANCE -------------- -------------- -------------- -------------- -------------- -------------$5,135.80 $410.00 $205.00 $.00 $.00 $615.00
sasi-2
$11,901.00 $123.90 $247.80 $.00 $.00 $371.70 ============== ============== ============== ============== ============== ============== $17,036.80 $533.90 $452.80 $.00 $.00 $986.70 TOTAL FEDERAL BALANCE TOTAL STATE BALANCE $533.90 $452.80
4-67
November 2010
REPORT FARWHLD
Banner Development Environment 1099 Reporting/Withholding Status Report As Of 08/10/1996 * * * REPORT CONTROL INFORMATION * * *
RPTNAME: FARWHLD PARAMETER SEQUENCE NUMBER: REPORTING YEAR: 96 AS OF DATE: 08/10/1996 NUMBER OF PRINTED LINES PER PAGE: 55
4-68
November 2010
1099 Reporting/Withholding Audit Report (FARWHLY)

Description
This report contains the U.S. Federal Government and appropriate State Government withholding tax and reporting data by vendor for those purchases subject to the IRS 1099 Form reporting requirements. Columns include Reportable Amounts, Federal and State Withheld, and Federal and State Paid Over amounts all within income type. Use this report to verify the accuracy of distributions made to each vendor within income type. This report sorts by vendor ID.
Parameters
Name
Required?
Description
Values
Reporting Year, (YY) As of Date (DD-MON-YYYY)
Yes Yes
Calendar 1099 reporting year Date to select data for reporting.
YY DD-MON-YYYY Default = current date
REPORT FARWHLY REPORT YEAR 96
Banner Development Environment 1099 Reporting/Withholding Audit Report As Of 08/10/1996
VENDOR/PAYEE <--------- WITHHELD --------> <-------- PAID OVER --------> RPT_ID NAME ITYP REPORTABLE FEDERAL STATE FEDERAL STATE BALANCE ----------------------------------------- -------------- -------------- -------------- -------------- -------------- -------------Alex R. Banta ABC Corporation Textile Corporation TOTAL ALL VENDORS RE PR $5,135.80 $410.00 $205.00 $.00 $.00 $615.00
$11,901.00 $123.90 $247.80 $.00 $.00 $371.70 ============== ============== ============== ============== ============== ============== $17,036.80 $533.90 $452.80 $.00 $.00 $986.70 TOTAL FEDERAL BALANCE TOTAL STATE BALANCE $533.90 $452.80
4-69
November 2010
REPORT FARWHLY
Banner Development Environment 1099 Reporting/Withholding Status Report As Of 08/10/1996 * * * REPORT CONTROL INFORMATION * * *
RPTNAME: FARWHLY PARAMETER SEQUENCE NUMBER: REPORTING YEAR: 96 AS OF DATE: 08/10/1996 NUMBER OF PRINTED LINES PER PAGE: 55
4-70
November 2010
1099 Forms Test Patterns (FAT1099)

Description
This process prints test patterns for 1099 forms, two forms per page. A sample test pattern is provided following the parameters.
Parameters
Name
Required?
Description
Values
Print Test Pattern1, 2, or N
No
Enter Y to print test patterns, or enter N to suppress printing.
Y N
Yes No
Sample Test Pattern
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxx
xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxxxx xxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxx xxxxxxxxxxxxx x xxxxxxxxxxxxx
xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xx xxxxxxxxxxxxx xxxxxxxxxxxxx
4-71
November 2010
Budget Development Module

This section describes each report in the Budget Development module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
4-72
November 2010
Budget Defaults SS Mass Update (FBPBDEF)

Description
This process allows an Administrator to control defaults for how budget information will be displayed to users in Self-Service Budget Development. Run this process to automatically insert and/or update each User's default values to use the same values as the Budget Worksheet template specified by a parameter. Users with a FOMPROF record allowing Self-Service Access will be processed. The user defaults are updated in the table FOBPRTO for the template type REPORTBDEF and will then be applied when using any of the following options: My Worksheets Create Budget Development Query Create Budget Worksheet The following default values will be updated for each user in the population Budget Types (such as Adopted, Permanent Adjustments, Temporary Adopted, Temporary Adjustments) Budget Duration Financial Manager origin Account Types Deleted Items
Note Changes made by a User in Self-Service Budget Development can overwrite these values for the specific User and will remain until the next time the process is run.
Parameters
Name
Required?
Description
Values
01 02
Report Mode Process Mode
Report Mode: (A)udit only no updates, (U)pdate database. (U)pdate to existing Users, (A)dd defaults to new Users, (B)oth update and add.
A B
4-73
November 2010
Parameters (cont)
Name
Required?
Description
Values
03
Default Template Name
Enter 'Saved Query' name for Budget Worksheet. Validated against FOBPRTO_NAME. Verify 'Saved Query' name on Budget Worksheet web page, or work with IT to view existing table values.
Enter User ID identified with the 'Saved Query' default name. Validated against GOAEACC. Print a list of Users that were updated, Yes or No.
04 05 06 07 08 09
User ID Print User Names Population Selection Indicator Application ID Selection ID Creator ID
N N
Enter Population Selection Entry Indicator. Enter the name of the Population Selection Application. Enter the Population Selection ID. Enter the Creator of the Population Selection.
4-74
November 2010
Approved Distributed Budget Report (FBRAPPD)

Description
The Approved Distributed Budget Report lists the distributed approved budget, the distributed current year budget, the distributed prior year budget, and the variance from the approved to the current budget. This report is sorted by organization, fund, program, activity, location, and account.
Parameters
Name
Required?
Description
Values
Budget Year Chart of Accounts As of Date (DD-MON-YYYY) Budget ID Print Net Totals
Yes Yes No
Two-digit budget year for reporting. Chart of accounts for reporting. Date to select data for reporting.
YY
Yes No
Budget ID for reporting. Enter Y to print net totals. Y N Yes (default) No
Specific Organization Organization Level
No No
Organization for reporting. Organization level for the specific organization, if entered. Enter E for As Exists or a value from 1 to 8 for a specific organization level. Amounts will be rolled to this level in the report. Fund used for reporting. Fund level for the specific fund, if entered. Enter E E As exists (default value) for As Exists or a value from 1 to 5 for a specific fund level. Amounts will be rolled to this level in the 1-5 Specific fund level report. Program for reporting. E As exists (default)
1-8 Specific organization level
Specific Fund Fund Level
No No
Specific Program
No
4-75
November 2010
Parameters (cont)
Name
Required?
Description
Values
Program Level
No
Program level for the specific program, if entered. Enter E for As Exists or a value from 1 to 5 for a specific program level. Amounts will be rolled to this level in the report. Activity for reporting. Location for reporting. Location level for the specific location, if entered. Enter E for As Exists or a value from 1 to 5 for a specific location level. Amounts will be rolled to this level in the report. Account for reporting. Account level for the specific account, if entered. Enter E for As Exists or a value from 1 to 4 for a specific account level. Amounts will be rolled to this level in the report.
As exists (default)
1-5 Specific program level
Specific Activity Specific Location Location Level
No No No
As exists (default)
1-5 Specific location level
Specific Account Account Level
No No
As exists (default
1-4 Specific account level
4-76
November 2010
03/08/1997 12:06:04 BUDGET YEAR 96
Banner University Approved Distributed Budget Operating Budget for FY 96 As of 30-oct-1995 Office of the Provost Current Operating Funds APPROVED BUDGET 1996 CURRENT YEAR BUDGET 1995 PRIOR YEAR BUDGET
PAGE 1 FBRAPPD
ORGANIZATION: FUND: Prog/ Actv/ Locn 400 01 10
101 102000
CODE TITLE Academic Support Program Executive Management Old Campus PERIOD 1 2 3
******** VARIANCE ******** APPROVED BUDGET TO CURRENT YEAR AMOUNT PERCENT
ACCOUNT TITLE 5000 Salary & Wages
587,666.66 587,666.67 587,666.67 1,763,000.00
.00 .00 .00 .00
.00 .00 .00 .00
587,666.66 587,666.67 587,666.67 1,763,000.00
.000 .000 .000 .000
TOTAL: TOTAL:
Salary & Wages Academic Support Program Total revenues Total labor Total expense Total transfers Total net Institutional Administration Executive Management Old Campus Salary & Wages 1 2 3
.00 1,763,000.00 .00 .00 -1,763,000.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 1,763,000.00 .00 .00 -1,763,000.00
.000 .000 .000 .000 .000
600 01 10 5000
133,000.00 133,000.00 133,000.00
.00 .00 .00
.00 .00 .00
133,000.00 133,000.00 133,000.00
.000 .000 .000
******************* CONTINUED ON NEXT PAGE *******************
4-77
November 2010
******************* CONTINUED FROM PREVIOUS PAGE ******************* TOTAL: TOTAL: Salary & Wages Institutional Administration Total revenues Total labor Total expense Total transfers Total net 399,000.00 .00 399,000.00 .00 .00 -399,000.00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 399,000.00 .00 399,000.00 .00 .00 -399,000.00 .000 .000 .000 .000 .000 .000
TOTAL:
Current Operating Funds Total revenues Total labor Total expense Total transfers Total net
.00 2,162,000.00 .00 .00 -2,162,000.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 2,162,000.00 .00 .00 -2,162,000.00
.000 .000 .000 .000 .000
03/08/1997 12:06:04 BUDGET YEAR 96
Banner University Approved Distributed Budget Operating Budget for FY 96 AS OF 30-oct-1995 Office of the Provost Current Operating Funds APPROVED BUDGET 1996 CURRENT YEAR BUDGET 1995 PRIOR YEAR BUDGET
PAGE 2 FBRAPPD
ORGANIZATION: FUND: Prog/ Actv/ Locn 600 01 10 ACCOUNT TOTAL:
101 102000
CODE TITLE Institutional Administration Executive Management Old Campus TITLE Office of the Provost Total revenues Total labor Total expense Total transfers Total net PERIOD
.00 2,162,000.00 .00 .00 -2,162,000.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 2,162,000.00 .00 .00 -2,162,000.00
.000 .000 .000 .000 .000
4-78
November 2010
Approved Budget Report (FBRAPPR)

Description
The Approved Budget Report lists the approved budget, the current year budget, the prior year budget, and the variance from the approved to the current budget. This report is sorted by organization, fund, program, activity, location, and account.
Parameters
Name
Required?
Description
Values
Budget Year Chart of Accounts As of Date (DD-MON-YYYY) Budget ID Print Net Totals
Yes Yes No
Two-digit budget year for reporting. Chart of accounts for reporting. Date to select data for reporting.
YY
Yes Yes
Budget ID for reporting. Enter Y to print net totals. Y N Yes (default) No
Specific Organization Organization Level
No No
Organization for reporting. Organization level for the specific organization, if entered. Enter E for As Exists or a value from 1 to 8 for a specific organization level. Amounts will be rolled to this level in the report. Fund used for reporting. Fund level for the specific fund, if entered. Enter E E As exists (default) for As Exists or a value from 1 to 5 for a specific fund level. Amounts will be rolled to this level in the 1-5 Specific fund level report. Program for reporting. E As exists (default)
1-8 Specific organization level
Specific Fund Fund Level
No No
Specific Program
No
4-79
November 2010
Parameters (cont)
Name
Required?
Description
Values
Program Level
No
Program level for the specific program, if entered. Enter E for As Exists or a value from 1 to 5 for a specific program level. Amounts will be rolled to this level in the report. Activity for reporting. Location for reporting. Location level for the specific location, if entered. Enter E for As Exists or a value from 1 to 5 for a specific location level. Amounts will be rolled to this level in the report. Account used for reporting. Account level for the specific account, if entered. Enter E for As Exists or a value from 1 to 4 for a specific account level. Amounts will be rolled to this level in the report.
As exists (default)
1-5 Specific program level
Specific Activity Specific Location Location Level
No No No
As exists (default)
1-5 Specific location level
Specific Account Account Level
No No
As exists (default)
1-4 Specific account level
4-80
November 2010
03/08/91 10:14:09 BUDGET YEAR 96
Banner University Approved Budget Operating Budget for FY 96 AS OF 30-oct-1995 Office of the Provost Unrestricted Funds APPROVED BUDGET 1996 CURRENT YEAR BUDGET 1995 PRIOR YEAR BUDGET
PAGE 1 FBRAPPR
ORGANIZATION: FUND: Prog/ Actv/ Locn 400 01 10
101 102000
CODE TITLE Academic Support Program Executive Management Old Campus
ACCOUNT TITLE 5000 Salary & Wages TOTAL: TOTAL: TOTAL: Old Campus Executive Management Academic Support Program Total revenues Total labor Total expense Total transfers Total net Current Operating Funds Total revenues Total labor Total expense Total transfers Total net
1,763,000.00 1,763,000.00 1,763,000.00
.00 .00 .00
.00 .00 .00
1,763,000.00 1,763,000.00 1,763,000.00
.000 .000 .000
.00 1,763,000.00 .00 .00 -1,763,000.00 .00 1,763,000.00 .00 .00 -1,763,000.00
.00 .00 .00 .00 .00 .00 .00 .00 .00 .00
.00 .00 .00 .00 .00 .00 .00 .00 .00 .00
.00 1,763,000.00 .00 .00 -1,763,000.00 .00 1,763,000.00 .00 .00 -1,763,000.00
.000 .000 .000 .000 .000 .000 .000 .000 .000 .000
TOTAL:
4-81
November 2010
03/08/91 10:14:09 BUDGET YEAR 96
Banner University Approved Budget Operating Budget for FY 96 AS OF 30-OCT-1995 Office of the Provost Unrestricted Funds APPROVED BUDGET 1996 CURRENT YEAR BUDGET 1995 PRIOR YEAR BUDGET
PAGE 2 FBRAPPR
ORGANIZATION: FUND: Prog/ Actv/ Locn 600 01 10 ACCOUNT TOTAL:
101 102000
CODE TITLE Institutional Administration Executive Management Old Campus TITLE Office of the Provost Total revenues Total labor Total expense Total transfers Total net
.00 2,162,000.00 .00 .00 -2,162,000.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 2,162,000.00 .00 .00 -2,162,000.00
.000 .000 .000 .000 .000
4-82
November 2010
Budget Build Process (FBRBDBB)

Description
This process is used to build phases and distributed budget records according to the parameters entered on the Budget Process Control Parameter Form (FBABPRC).
Note If any of these parameters are null, then all values will be included.
Phases may be created based on the Operating Ledger (FGBOPAL) or the Budget Line Item Table (FBBBLIN). This process produces no output.
4-83
November 2010
Distribution Process Summary (FBRBDDS)

Description
FBRBDDS provides a summary of the off-line process used to distribute amounts from the budget line item table into periodic amounts in the distribution table. This process produces no output.
4-84
November 2010
Budget Roll to General Ledger (FBRBDRL)

Description
FBRBDRL rolls budget amounts into the finance ledgers. Enter values in the parameters for the budget roll on the Budget Process Control Parameter Form (FBABPRC). When you execute FBRBDRL, records are written to the Transaction Input Table (FGBTRNI). Generate these two reports to view any errors encountered during the budget roll process: Interface Process (FGRTRNI) Transaction Error Report (FGRTRNR)
Report Sample
07/01/1995 08:29:17
Banner University Budget Roll to General Ledger As of 01-JUL-1995 * * * REPORT CONTROL INFORMATION * * *
PAGE 1 FBRBDRL
BUDGET ID: FY93 BUDGET PHASE: FINAL CHART OF ACCOUNTS: A PERMANENT RULE CODE: BD01 TEMPORARY RULE CODE: BD03 ROLL PERCENTAGE: 100.000 REPEAT ROLL INDICATOR: DESCRIPTION: budg roll DOCUMENT CODE: L0000042 SYSTEM ID: BUDGET SYSTEM DATE: 19930701082917 ACTIVATION DATE: 01-JUL-1995 TRANSACTION HEADER AMOUNT: 225220.00
PARAMETER SEQUENCE NUMBER: NUMBER OF PRINTED LINES PER PAGE: 55 COUNT OF INSERTS TO FGBTRNI: 8423 RECORD COUNT: 1
4-85
November 2010
Finance Budget Feed Process (FBRFEED)

Description
This process is used to move Position Control budget information from the Position Control module into the Finance Budget tables. All FOAPAL data is transferred between modules. Both the Budget Line Item Table (FBBBLIN) and the corresponding Distribute Table (FBRDIST) are affected by the FBRFEED process. FBRFEED reads the GURFEED table which has data supplied by the Finance Interface Process, NHPFIN2. FBRFEED decides which budget module tables to update. Enter new Position Control information on the Position Definition Form (NBAPOSN). Specify Active or Working Budgets in the Fringe Total Block. Both Active and Working Budgets are sent to the Finance Budget Tables when this process is run. Run the Finance Interface Extract Process NHPFIN1. Run the Finance Interface Process NHPFIN2. NHPFIN2 configures the records into GURFEED format. Run the FBRFEED process.
Parameters
Name
Required?
Description
Values
Report Mode Process ALL Indicator
No No
Report Mode options are: V to examine the data that will be processed, or S to actually run the updates. Process ALL Indicator options are: Y to process all records or N to process selected records. Enables direct specific processing. A date value only processes all batches for that day; a specific timestamp will do only that one process.
S or V Y N Yes No
Time Stamp
No
DD-MON-YYYY[HH24MISS]
4-86
November 2010
Report Sample
PAGE 1 REPORT : FBRFEED
Banner University Finance Budget Feed Process DOCUMENT -------F0000748 F0000754 DESCRIPTION ----------------------------------Banner HR / Position Batch Header Banner HR / Position Batch Header REPORT TOTALS: AMOUNT -------------25455.94 515810.40 -------------541266.34 COUNT -----1 3 -----4
RUN DATE 11/18/1996 RUN TIME 04:14 PM
SYSTEM ID --------POSNBUD POSNBUD
TIMESTAMP -----------------19911114132318 19911115170601
4 TRANSACTIONS 0 3 1
LINE ITEM INSERTS: LINE ITEM UPDATES: DISTRIBUTION UPDATES:
4-87
November 2010
Budget Mass Change Process (FBRMCHG)

Description
This process permits you to make global budget changes, by organization, to adjust budget items by flat amounts or percentages. Parameters used by this process are defined on the Mass Budget Changes Form (FBAMCHG).
Report Sample
04/26/1996 19:46:19
Banner University Budget Mass Change Process As of 26-APR-1996 INDEX ORGN 125 125 FUND 1000 1000 PROG 111 111 ACCT 1010 1010 ACTV 410 410 LOCN 1001 1001 DUR P P DIST W/IN N N AMOUNT PCT 10.000 5.000
PAGE 1 FBRMCHG
BUDG ID
BUDG PHASE
COA T T
MANT91 M91P1 MANT91 M91P2
4-88
November 2010
Budget Worksheet Report (FBRWKSH)

Description
This report displays up to three budget phases with current year and prior year budget amounts from the budget file. This report is sorted by organization, fund, program, activity, location, and account. Use this as a worksheet for the new year's budget.
Parameters
Name
Required?
Description
Values
Budget Year Chart of Accounts Budget ID Budget Phase 1 Budget Phase 2 Budget Phase 3 As of Date (DD-MON-YYYY) Print Net Totals
Yes Yes Yes No No No No
Two digit budget year to report. Chart of accounts for reporting. Budget ID for reporting. First budget phase for reporting. Second budget phase for reporting. Third budget phase for reporting. Date to select data for reporting.
YY
No
Enter Y to print net totals.
Y N
Yes (default) No
Specific Organization Specific Fund Specific Program Specific Activity Specific Location Specific Account
No No No No No No
Organization for reporting. Fund for reporting. Program for reporting. Activity for reporting. Location for reporting. Account for reporting.
4-89
November 2010
03/07/91 11:03:50 BUDGET YEAR 96
Banner University Budget Worksheet Fiscal Year '96 Budget AS OF 05-feb-1995
PAGE 1 FBRWKSH
ORGANIZATION: 103 Vice President for Administration FUND: 103000 Current Operating Funds - unrestric PRIOR YEAR CURRENT YEAR PHASE 1: PHASE 2: PHASE 3: 1990 1991 ---------------- ---------------- ---------------- ---------------- ---------------PROGRAM: 610 Executive Management ACTIVITY: 01 Executive Management LOCATION: 16 Vice President Admin - Suite 10 ACCOUNT: 6111 Office Supply Accounts 6310 6330 6340 6410 Capital Purchases - Computers Capital Purchases - Lab Equipment Capital Purchases - Vehicles Utilities Expense - Electric
4,000.00 100,800.00 4,000.00 18,500.00 10,600.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
PROGRAM TOTAL: Total Total Total Total Total
Revenue Labor Expense Transfers Net
.00 .00 137,900.00 .00 -137,900.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
******************* CONTINUED ON NEXT PAGE *******************
4-90
November 2010
******************* CONTINUED FROM PREVIOUS PAGE ******************* PROGRAM: 640 General Administration ACTIVITY: Activity not budgeted LOCATION: Location not budgeted ACCOUNT: 6111 Office Supply Accounts PROGRAM TOTAL: Total Total Total Total Total FUND TOTAL: Total Total Total Total Total .00 950.00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 950.00 .00 -950.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 137,900.00 .00 -137,900.00
.00 .00 950.00 .00 -950.00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
.00 .00 .00 .00 .00
4-91
November 2010
Cost Accounting Module

This section describes each report in the Cost Accounting module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their sevencharacter names.
4-92
November 2010
Cost Accounting Billing Process (FCBBILL)

Description
The Cost Accounting Billing Report prints a summary of all billing charges by project and by project rate type for the current billing cycle. Category rate types list in order of the sequence assigned on the Rate Type Code Maintenance Form (FTMRTYP). All of the internal rate codes associated with the category rate types list the following: Current billing rate Number of units charged for this billing cycle Any prior billing charges for that rate code Current billing charge If no charges occurred during this billing cycle for a rate type, only Previous Billing and Total Billing columns display. Totals display for each rate type which are previous and total billing amounts. Customer and project totals display for the following columns: Previous Billing Current Billing Total Billing FTBBILL takes into account a start and end date for project billing transactions. If the Update Database indicator is set to N, the report is generated in a test mode which produces FCBBILL without updating the database. Set the indicator to Y to generate FCBBILL and to do the following: Create Billing Detail Report records Create history records for the Project History Table (FCBPHST) Create charge records for the Project/Customer Charges Table (FCBPRJC) Create Transaction Input Table (FGBTRNI) records Update inventory, equipment, and employee database fields The parameter table entry for this billing cycle is deleted at the end of report execution. The parameter table entry is always deleted whether this report is run in test mode or database update mode. All detail charges entered on the
4-93
November 2010
Cost Accounting Maintenance Form (FCAACCT) that were selected for projects processed during this billing cycle are deleted. Submit this report through the Job Submission feature or define parameters on the Cost Accounting Batch Parameter Maintenance Form (FCAPARM).
Note The Document Number parameter is required when the Update Database indicator is populated with Y. If you specify N for the Update Database Indicator, then Document Number is optional. The Update Database indicator will not accept a null value. After you run the billing process in update mode, conclude the billing run by executing the Transaction Interface Process (FGRTRNI).
This list of parameters is only accessible through the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). If you submit this report through Job Submission you will be prompted for only two parameters: Parameter Sequence Number and Number of Printed Lines Per Page.
4-94
November 2010
Report Sample
REPORT FCBBILL FISCAL YEAR 1992
Banner University Billing Report
CUSTOMER #: CUSTOMER NAME: CUSTOMER ADDRESS: CUSTOMER CHARGE % PROJECT CODE: PROJECT DESC: START DATE: END DATE: CATEGORY Direct Labor
310 Johnson, John Business Center Malvern PA 19355 100.000 M126 Office Renovation 05-NOV-91
RATE CODE DLOH DLST
RATE 5.000 20.000
UNITS 40.00 40.00
PREVIOUS BILLING .00
CURRENT BILLING 200.00 800.00
TOTAL BILLING
1000.00 Equipment Rental REQP REQP Inventory Handling INHD INHD 18.000 22.000 5.00 4.00 7.000 15.000 6.00 1.00 .00 90.00 88.00 178.00 CUSTOMER TOTAL PROJECT TOTAL .00 .00 1235.00 1235.00 1235.00 1235.00 .00 42.00 15.00 57.00
4-95
November 2010
Equipment Rental Rate Calculation Report (FCBEQPT)

Description
This report displays the results of the equipment rental rate calculations for all employees and equipment within an organization. The automatic labor rate calculation process for equipment rental provides the ability to calculate a new rate value for internal rate codes associated to rate types of Equipment Rental. This new rate value is stored in the Internal Rates Table (FCBRATE) with a new effective date. This process also produces a paper report listing all items used to perform the calculations as well as the resulting valued rates. The final process of this report resets the equipment actual machine hours in the Equipment Validation Table (FTVEQPT) to zero and resets the employee's actual direct hours and actual indirect hours in the Employee Table (FCBEMPL) to zero. The organization's current year uncommitted budget for all defined equipment handling accounts is used in the calculations to derive a new rate value. This list of parameters is only accessible through the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). If you submit this report through Job Submission, you will be prompted for only two parameters: Parameter Sequence Number and Number of Printed Lines Per Page.
4-96
November 2010
REPORT FCBEQPT FISCAL YEAR 1992
Banner University Equipment Rental Rate Calculation
COA:
TITLE: Banner University TITLE: Mechanical Engineering DESC : Equipment Rental BENEFITS TOTAL LABOR AVAILABLE HRS DIRECT INDRCT 41,000.00 31,500.00 63,000.00 55,000.00 1,000.00 175.00 300.00 6,975.00 0.191 1.102 AMOUNT 160.00 15.00 175.00 41,000.00 55,175.00 2,300.00 2,080 2,080 2,080 2,080 2,080 2,080 80 0 10 2,090 2,080 VAC SICK HOL OTHER PRODUCTIVE HOURS DIRECT INDIRECT 2,080.00 2,080.00 2,080.00 2,080.00 8 16 0 1,856.00 1,792.00 64.00 0.00 2,080.00 0.00 0.00 0.00 0.00 8.00 2,088.00
ORGANIZATION: 165 RATE CODE : EMPLOYEE# REQP NAME WAGES 213450066 777010005 777010007 777010008 777010011 777010027 777010028
Butler, Nora A. 40,000.00 Smith, Lisa B. 30,000.00 Dean, Thomas R. 60,000.00 Evans, Ruth W. 55,000.00 Adams, Eugene M. 40,000.00 Smith, Joshua 55,000.00 Smith, Jane 2,000.00
1,000.00 1,500.00 3,000.00
80 120 120 160 40 80 4 604
96 96 96 96 80 96 6 566
96 96 96 96 96 96 8 584
TOTAL ORGANIZATION 282,000.00 DIRECT LABOR RATE INDIRECT LABOR RATE ACCOUNT 6180 6400 TITLE Indirect Cost Charges Utilities Expense TOTAL OTHER COSTS
288,975.00 12,560
24 12,032.00
******************************* CONTINUED ON NEXT PAGE *******************************
4-97
November 2010
******************************* CONTINUED FROM PREVIOUS PAGE ******************************* EQUIP NO DESCRIPTION LABOR PS0000002 paint sprayer type 2 1,000.00 PS0000003 paint sprayer type 3 500.00 PS0000004 paint sprayer type 4 400.00 PS0000005 paint sprayer type 5 700.00 PS0000001 Sears Fine Quality Paint Sprayer #1 500.00 35.00 20.00 20.00 10.00 375.00 50.00 1,130.00 580.00 500.00 100.00 64.268 18.202 10.00 5.00 300.00 715.00 200.00 28.378 30.00 12.00 200.00 742.00 270.00 36.232 20.00 5.00 350.00 1,375.00 300.00 41.788 MAINTENANCE SUPPLIES DEPRECIATION MACHINE COSTS HOURS AVAIL RATE
REPORT FCBEQPT FISCAL YEAR 1992
Banner University Equipment Rental Rate Calculation
COA:
TITLE: Banner University TITLE: Mechanical Engineering DESC : Equipment Rental DESCRIPTION LABOR MAINTENANCE 10.00 125.00 SUPPLIES 10.00 62.00 DEPRECIATION 200.00 1,475.00 MACHINE COSTS 1,220.00 5,762.00 HOURS AVAIL 50.00 1,420.00 RATE 30.601
ORGANIZATION: 165 RATE CODE : EQUIP NO REQP
PS-000001 Paint Sprayer Fine Quality 1,000.00 TOTAL ORGANIZATION 4,100.00
4-98
November 2010
Inventory Handling Rate Calculation Report (FCBINVT)

Description
This report displays the result of the inventory handling rate calculation for all employee and inventory items associated with an organization. The automatic labor rate calculation process for inventory handling provides the ability to calculate a new rate value for internal rate codes associated to rate types of inventory handling. This new rate value is stored in the Internal Rates Table (FCBRATE) with a new effective date. This process also produces a paper report listing all items used to perform the calculations as well as the resulting valued rates. The final process of this report resets the inventory actual units in the Inventory Validation Table (FTVINVT) to zero and resets the employee's actual direct hours and actual indirect hours in the Employee Table (FCBEMPL) to zero. The organization's current year uncommitted budget for all defined inventory handling accounts is used in the calculations to derive a new rate value. This list of parameters is only accessible through the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). If you submit this report through Job Submission, you will be prompted for only two parameters: Parameter Sequence Number and Number of Printed Lines Per Page.
4-99
November 2010
Report Sample
REPORT FCBINVT FISCAL YEAR 97 COA: T ORGANIZATION: 165 RATE CODE : INHD EMPLOYEE# 213450066 777010005 777010007 777010008 777010011 777010027 777010028 NAME WAGES Butler, Nora A. 40,000.00 Smith, Lisa B. 30,000.00 Dean, Thomas R. 60,000.00 Evans, Ruth W. 55,000.00 Adams, Eugene M. 40,000.00 Smith, Joshua 55,000.00 Smith, Jane 2,000.00 BENEFITS 1,000.00 1,500.00 3,000.00
Banner University Inventory Handling Rate Calculation TITLE: Banner University TITLE: Mechanical Engineering DESC : Inventory Handling TOTAL LABOR AVAILABLE HRS DIRECT INDRCT 41,000.00 31,500.00 63,000.00 55,000.00 1,000.00 175.00 300.00 6,975.00 0.191 1.102 AMOUNT 160.00 15.00 175.00 UNIT PRICE 25.00 20.00 ESTIMATED UNITS 100 100 RATE 26.761 21.761 41,000.00 55,175.00 2,300.00 2,080 2,080 2,080 2,080 2,080 2,080 80 0 10 2,090 2,080 VAC 80 120 120 160 40 80 4 604 SICK 96 96 96 96 80 96 6 566 HOL 96 96 96 96 96 96 8 584
OTHER
PRODUCTIVE HOURS DIRECT INDIRECT 2,080.00 2,080.00 2,080.00 2,080.00 0.00 2,080.00 0.00 0.00 0.00 0.00 8.00 2,088.00
8 16 0
1,856.00 1,792.00 64.00
TOTAL ORGANIZATION 282,000.00 DIRECT LABOR RATE INDIRECT LABOR RATE ACCOUNT 6180 6400 TITLE Indirect Cost Charges Utilities Expense TOTAL OTHER COSTS INVENTORY LB-PAINT DB-PAINT DESCRIPTION Light Blue Paint Dark Blue Paint
288,975.00 12,560
24 12,032.00
4-100
November 2010
Labor Rate Calculation Report (FCBLABR)

Description
This report is designed to display results for the calculation of a direct or indirect labor rate for employees within an organization associated with classification codes. Labor rates are printed for each rate code. The automatic rate calculation process for direct and indirect labor provides the ability to calculate a new rate value for internal rate codes associated to rate types of direct labor and indirect labor. This new rate value is stored in the Internal Rates Table (FCBRATE) with a new effective date. This process also produces a paper report listing all items used to perform the calculations as well as the resulting valued rates. The final function of this report resets the employee's actual direct hours and actual indirect hours in the Employee Table (FCBEMPL) to zero. This list of parameters is only accessible through the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). If you submit this report through Job Submission, you will be prompted for only two parameters: Parameter Sequence Number and Number of Printed Lines Per Page.
Report Sample
REPORT FCBLABR FISCAL YEAR 97
Banner University Labor Rate Calculation
COA:
TITLE: Banner University TITLE: Mechanical Engineering DESC : Direct Labor Overhead DESC : Clerical Employee Classification NAME BENEFITS
ORGANIZATION: 165 RATE CODE: CLASS CODE: EMPLOYEE# WAGES 777010005 777010028 RATE TOTAL 32,000.00 LABOR RATE DLOH CLER
TOTAL LABOR AVAILABLE HRS DIRECT INDRCT 31,500.00 2,300.00 33,800.00 15.765 2,080 80 2,160 2,080 10 2,090
VAC
SICK
HOL
OTHER
PRODUCTIVE HOURS DIRECT INDIRECT 2,080.00 2,080.00 8.00 2,088.00
Smith, Lisa B. 30,000.00 Smith, Jane 2,000.00
1,500.00 300.00 1,800.00
120 4 124
96 6 102
96 8 104 0 0
64.00 2,144.00
4-101
November 2010
Material Management Rate Calculation Report (FCBMATL)

Description
This report is designed to display the results of the material management rate calculation process for all employees and material management accounts associated with an organization. The automatic labor rate calculation process for material management provides the ability to calculate a new rate value for internal rate codes associated to rate types of material management. This new rate value is stored in the Internal Rates Table (FCBRATE) with a new effective date. This process also produces a paper report listing all items used to perform the calculations as well as the resulting valued rates. The final function of this report resets the employee's actual direct hours and actual indirect hours in the Employee Table (FCBEMPL) to zero. The organization's current year uncommitted budget for all defined material management accounts is used in the calculations to derive a new rate value. This list of parameters is only accessible through the Cost Accounting Batch Parameter Maintenance Form (FCAPARM). If you submit this report through Job Submission, you will be prompted for only two parameters: Parameter Sequence Number and Number of Printed Lines Per Page.
4-102
November 2010
Report Sample
REPORT FCBMATL FISCAL YEAR 97
Banner University Material Management Rate Calculation
COA:
TITLE: Banner University TITLE: Mechanical Engineering DESC : MECH Material Management NAME AVAILABLE HRS DIRECT INDRCT 2,080 2,080 2,080 2,080 2,080 2,080 80 12,560 2,080 VAC 80 120 120 160 40 80 4 604 AMOUNT 2485.00 15.00 2500.00 0.177 SICK 96 96 96 96 80 96 6 566 HOLDY 96 96 96 96 96 96 8 584 OTHER PRODUCTIVE HOURS 2,080.00 4,160.00 2,080.00 2,080.00 1,856.00 1,792.00 72.00 14,120.00
ORGANIZATION: 165 RATE CODE : EMPLOYEE# 213450066 777010005 777010007 777010008 777010011 777010027 777010028 MMTS
Butler, Nora A. Smith, Lisa B. Dean, Thomas R. Evans, Ruth W. Adams, Eugene M. Smith, Joshua Smith, Jane TOTAL ORGANIZATION
0 10 2,090
8 16 0 24
ACCOUNT 6180 6400
TITLE Indirect Cost Charges Utilities Expense TOTAL OTHER COSTS MATERIAL MANAGEMENT RATE
4-103
November 2010
Cost Accounting Billing Detail Report (FCRBDTR)

Description
The Billing Detail Report prints billing details by project, cost type, and rate code. Maximum billing amount and charge percentage are printed for each customer. All cost types and employee name, inventory code, or equipment code charged for a project are displayed along with the internal rate code and dollar rate amount (or external rate code and dollar amount). The number of units and billed amount charged to the cost type and rate code display. The Billed Date prints for each rate code displayed. If a document reference number is associated with an internal rate code, it displays under rate code along with the document type code. This report is generated when Y is entered in the Update Database indicator on the Cost Accounting Billing Report (FCBBILL). FCRBDTR displays all of the transactions from the project's inception to the last billing cycle run of the project.
4-104
November 2010
Report Sample
REPORT FCRBDTR
Banner University Billing Detail Report
CUSTOMER NUMBER 310
CUSTOMER NAME Johnson, John DESC: Office Renovation
MAX BILLABLE AMOUNT 25000.00
CHARGE PERCENT 100.000
PROJECT: M126
COST TRANS EMPLOYEE/ TYPE DATE NAME EL 08-NOV-1996 RATE CODE INTERNAL RATE REQP Eqpmnt Ren 7.000 REQP Eqpmnt Ren 15.000 COST TRANS EMPLOYEE/ TYPE DATE NAME IN 08-NOV-1996 RATE CODE INTERNAL RATE INHD Inv Handle 18.000 INHD Inv Handle 22.000 COST TRANS EMPLOYEE/ TYPE DATE NAME LB 08-NOV-1996 777010005 Brown, Lisa R. RATE CODE INTERNAL RATE DLOH DL Ovrhead 5.000 DLST DL Standar 20.000
INVENTORY/ DESC
EQUIPMENT/ DESC PS-000001 Paint Sprayer Fine Quality UNITS 6.00 1.00 BILLED AMOUNT 42.00 15.00 BILLED DATE 08-NOV-1996 08-NOV-1996
EXTERNAL RATE CODE EXTERNAL RATE
INVENTORY/ DESC OW-PAINT Off White Paint EXTERNAL RATE CODE EXTERNAL RATE
EQUIPMENT/ DESC
UNITS 5.00 4.00
BILLED AMOUNT 90.00 88.00
BILLED DATE 08-NOV-1996 08-NOV-1996
INVENTORY/ DESC
EQUIPMENT/ DESC
EXTERNAL RATE CODE EXTERNAL RATE
UNITS 40.00 40.00
BILLED AMOUNT 200.00 800.00
BILLED DATE 08-NOV-1996 08-NOV-1996
4-105
November 2010
C/A Rate Schedule Report (FCRSCHD)

Description
The Cost Accounting Rate Schedule Report prints all internal and external rates within each rate type by chart of accounts and organization code. Supply an As of Date to generate this report.
Parameters
Name
Required?
Description
Values
As of Date (DD-MON-YYYY)
No
Date to select for reporting.
4-106
November 2010
Report Sample
REPORT FCRSCHD FISCAL YEAR 97 Chart of Accounts: T RATE TYPE Direct Labor
Banner University C/A Rate Schedule Report As Of 11/07/1997 Organization: 165 Mechanical Engineering INTERNAL RATE EXTERNAL RATE CODE DESCRIPTION CODE DESCRIPTION DLDT DL Dbltime DLDT DL Dbltime DLOH DL Ovrhead DLOT DL Ovrtime DLOT DL Ovrtime DLSA DL Sys Ana DLSR DL Sr Sys DLST DL Standar DLST DL Standar DLST DL Standar M0 M0 M0 Noop Noop Noop M0 P25 Noop Add 25 M0 P50 Noop Add 50 INTERNAL RATE 40.000 40.000 5.000 30.000 30.000 40.000 50.000 20.000 22.000 24.000 5.000 P1P P25 Add 1 Per Add 25 18.000 18.000 7.000 22.000 7.000 M0 P1P Noop Add 1 Per 15.000 15.000 .00 1.000 25.000 .000 .000 .000 .00 25.000 ADJUSTMENT AMOUNT PERCENT .00 50.000
RUN DATE: 11/07/1997 TIME: 12:11 PM PAGE: 1 EXTERNAL RATE 40.000 60.000
30.000 37.500
20.000 20.000 20.000
Indirect Labor Inventory Handling
ILOH IL Ovrhead INHD Inv Handle INHD Inv Handle INHD Inv Handle INHD Inv Handle
18.180 22.500
Equipment Rental
REQP Eqpmnt Ren REQP Eqpmnt Ren REQP Eqpmnt Ren
15.000
4-107
November 2010
C/A Variance Analysis Report (FCRVARA)

Description
Supply an As of Date to generate the Cost Accounting Variance Analysis Report.
Parameters
Name
Required?
Description
Values
No
Date to select for reporting.
Report Sample
REPORT FCRVARA FISCAL YEAR 97
Banner University C/A Variance Analysis Report As Of 01/08/1997 Organization: 350 Physical Plant RATE TYPE Direct Labor Direct Charges Direct Charges Direct Charges Direct Labor Direct Charges Direct Charges Direct Charges Direct Charges Direct Charges Indirect Labor Inventory Handling Direct Labor Direct Labor
Chart of Accounts: T EMPLOYEE NAME
---------------- UNITS ---------------ESTIMATED ACTUAL VARIANCE 2080.00 243.00 1837.00 0.00 0.00 0.00 1837.00 0.00 0.00 0.00 0.00 0.00 2080.00 0.00 1870.00 1870.00
777010027 Smith, Joshua
777010027 Smith, Joshua
2080.00
243.00
777010011 Adams, Eugene M. 777010005 Smith, Lisa B 777010005 Smith, Lisa B
2080.00 2080.00 2080.00
00.00 210.00 210.00
4-108
November 2010
Fixed Assets Module

This section describes each report in the Fixed Assets module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
4-109
November 2010
Depreciation Process (FFPDEPR)

Description
The Depreciation Process (FFPDEPR) will calculate depreciation for any open periods from the Last Depreciation Date up to the Depreciation Date you specify in the process parameters, with the exception of prior period or catch-up depreciation. In this case, you must run the Depreciation Process to calculate and (where appropriate) post this prior depreciation before the asset record will be considered for current depreciation. This date can only be entered in the form of month and year. A variety of parameters enable you to limit the records that will be considered for the process. You may run the Depreciation Process in audit or update mode. Both modes will produce a report, but only the update mode will amend the appropriate depreciation-related records. You may enter one or more charts in the Chart of Accounts parameter, but the selected Chart of Account records must have identical Fiscal Year records (FTVFSYR table). Only one year of prior period depreciation can be calculated and posted per run. This limitation applies because the accounting usually differs for postings in either the prior year or in the current year. Any depreciation record that is incomplete or is split across two or more charts will be flagged for errors by the Depreciation Process. The process will proceed to completion for all of the other records.
Parameters
Name
Required?
Description
Values
Asset Type
No
User-defined code which describes an asset category for grouping, reporting, and depreciation purposes. Leave this parameter blank to include all asset types. User-defined designation for the combination of internal depreciation method code and first year option. Leave blank to include all depreciation method codes. Periodic basis for the depreciation calculation. A S Q M Annual (default) Semi-annual Quarterly Monthly
Depreciation Method Code
No
Depreciation Frequency
Yes
4-110
November 2010
Parameters (cont)
Name
Required?
Description
Values
Chart of Accounts
Yes
Chart of accounts code where the depreciation expense accounts exist and to which the depreciation postings will be made. Enter the month and year up to which depreciation will be calculated. For catch-up of prior year depreciation, enter the last fiscal month and the fiscal year. Enter the transaction date for posting depreciation to the Operating Account Ledger and the General Ledger. Enter A (Audit) in this parameter to generate an as if report only (no records will be changed), or enter U (Update) in this parameter to amend the appropriate depreciation-related records and generate the report. Code that determines whether a summary report or a detailed report will be produced. The summary report is a summary of expense account distribution postings. Postings are for individual assets. The detail report shows depreciation for each account distribution on each selected record. MON-YYYY
Depreciation Month and Year
Yes
Posting Date (DD-MON-YYYY) Execution Mode (A/U)
Yes
DD-MON-YYYY Default = current date A U Audit mode (default) Update mode
Yes
Report Type
Yes
D S
Detail (default) Summary
4-111
November 2010
Report Sample - Detail Report (Page 1 of 2)
FFPDEPR 3.0
Banner Development Environment Fixed Asset Depreciation Detail Report Asset Description ------------------Vehicles Vehicles CB antenna Standard Double Ped P-200 PC w/32 MB ED Last Depr Date ----------31-DEC-1996 31-DEC-1996 31-DEC-1996 31-DEC-1996 31-DEC-1996 Depr Method -----SP SP SP SP SP Fst Year Opt ---PR PR PR PR PR
12/11/1996 14:44:04 PAGE 1
Permanent Tag --------JC0001 AP0010 TP246 P00000326 SU9700715 Otag Code ---------T00000255 T00000176
Seq No ---1 1 1 1 2
Est Life Rem Adjusted Salvage Depr Current Accum. Post Yrs Life Cost Value Freq Depr Depr Ind ---- ---- ------------ ---------- ---- ---------- ------------ ---2 12 6600.00 0.00 M 472.06 4711.77 P 4 36 5940.00 300.00 M 122.20 1240.93 P 5 54 100.00 0.00 M 5.00 55.00 P 7 78 509.91 0.00 M 36.42 36.42 P 3 35 1447.67 100.00 M 37.44 37.44 P
Error Message ------------------------------------------------------------------------------------Prior years have not been depreciated Prior years have not been depreciated
FFPDEPR 3.0
Banner Development Environment Fixed Asset Depreciation Detail Report * * * REPORT CONTROL INFORMATION (FFPDEPR RELEASE 3.0) * * * Parameters have been entered from Host Prompt.
12/11/1996 14:44:04 PAGE 2
Parameter Name _____________________________ Parameter Seq No: Adjustment doc code: Asty Code: Depr Method Code: Depr Frequency: Chart of accounts: Depreciation Date: Posting Date: Execution Mode: Report Type: Line Count:
Value ________________ 26950 All SP M B 31-DEC-1996 11-DEC-1996 A D 55
Message ____________________________________________________________
Monthly Depreciation
Audit Detail Chosen number of lines per page
4-112
November 2010
Report Sample - Summary Report (Page 1 of 2)
FFPDEPR 3.0 Fund Code --------9601 4997 1001 3997 4998 Otag Code ---------T00000255 T00000176 Account Code Depr Amount ------------ -------------3951 122.20 7931 472.06 7951 5.00 7941 36.42 7951 37.44
Banner Development Environment Fixed Asset Depreciation Summary Report
12/11/1996 15:13:45 PAGE 2
Error Message ------------------------------------------------------------------------------------Prior years have not been depreciated Prior years have not been depreciated
FFPDEPR 3.0
Banner Development Environment Fixed Asset Depreciation Summary Report * * * REPORT CONTROL INFORMATION (FFPDEPR RELEASE 3.0) * * * Parameters have been entered from Host Prompt.
12/11/1996 15:13:45 PAGE 2
Parameter Name _____________________________ Parameter Seq No: Adjustment doc code: Asty Code: Depr Method Code: Depr Frequency: Chart of accounts: Depreciation Date: Posting Date: Execution Mode: Report Type: Line Count:
Value ________________ 26954 All SP M B 31-DEC-1996 11-DEC-1996 A S 55
Message ____________________________________________________________
Monthly Depreciation
Audit Summary Chosen number of lines per page
4-113
November 2010
Fixed Asset Origination Tag Extraction Process (FFPOEXT)

Description
This process provides a consistent method of creating origination tag entries for the Asset Master record from the Procurement and Payables modules. Data from the invoice is fed into a collector table (FFBOTAG) during the Posting Process to determine whether an origination tag should be created, additional acquisition data should be updated, or the origination tag should be updated with cancellation information. If records in FFBOTAG have a non-invoice document reference, this process inserts records into the Fixed Assets Dtag tables (FFBDTGH, FFRDTGA, and FFRDTGD.) This process also prevents origination tags from being generated before the invoice has been approved or when a transaction rolls back in posting or matching process. Refer to Chapter 2, Processing for more details. The one exception to this process will be the origination tag created from receiving. In this case, the receiving process will feed the appropriate data to the collector table (FFBOTAG). The Receiving Process does not create accounting records for the asset. The report created in this process functions as an audit trail which describes the Origination tags to be created. This includes the Origination tag number, the invoice or receiving document used to create the origination tag, and the purchase order number. In addition, the invoice or receiving line item is provided. The report is always sorted by Document Number, Document Item Number, Purchase Order Number, and Purchase Order Item Number.
Parameters
Name
Required?
Description
Values
Audit or Update Mode
Yes
Enter A (Audit) in this parameter to generate an as if report only (no origination tags will be created), or enter U (Update) in this parameter to create the origination tags and generate the report.
A U
Audit mode (default) Update mode
4-114
November 2010
PAGE 1 FFPOEXT 5.3.1 Document # Item CW2678 I0010900 I0010900 I0010901 CW1111 DMI1023G I0010944 1 2 2 2 1 1 1 Commodity Description
DEVELOPMENT Fixed Asset Orig. Tag Extract Origination Tag T00007099 T00007100 T00007101 T00007102 T00007098 T00007103 T00007105 PO Number P0007278 P0007278 P0007278 E0000515 Amount 150.00 16.00 16.00 16.07 200.00 73000.00 50.00 Cap Action Taken T T T T T I I Tag Tag Tag Tag Tag Tag Tag created created created created created created created from from from from from from from
Supplies 1211000000 Desk, Classroom, Woo 1211000000 Desk, Classroom, Woo 1211000000 Desk, Classroom, Woo Supplies Supplies COMMODITY FROM GEN.
Invoice Invoice Invoice Invoice Invoice Invoice Invoice
PAGE 2 FFPOEXT 5.3.1
DEVELOPMENT Fixed Asset Orig. Tag Extract Document Tag Extract information
Document # Type Sub # Seq U0002143 H0003987 ISS DCR 1 1
Description Dtag Created Dtag Created
Document Tag D00007030 D00007031
Amount Cap 441.54 N -10.00 N
4-115
November 2010

PAGE 4 FFPOEXT 5.3.1 DEVELOPMENT Fixed Asset Orig. Tag Extract * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission. Parameter Name _____________________________ Parameter Seq No: Report Mode: Line Count: Value ________________ 978440 U 55 Message ____________________________________________________________ Update Mode RUN DATE 10/29/2002 RUN TIME 02:03 PM
The following chart contains a brief description of each field that is displayed on the Fixed Asset Origination Tag Extract Report.
Field Description
Document Number Item Commodity Description Origination Tag PO Number Amount Cap Action Taken
Invoice or receiving document number of the transaction processed. Commodity line item from either the invoice or the receiving document. Commodity code of the fixed asset. Asset description from the asset master record (FFBMAST). Number of the origination tag created and assigned by the system in this process for this transaction. Purchase order number related to the transaction processed. Cost of the asset. Indicator (FARINVC_CAP_TAG_CODE) that shows whether or not the asset is capitalized. Description of the action taken by the process; for example, Tag created from Invoice.
4-116
November 2010
Fixed Asset/Asset Group Report (FFRAGRP)

Description
The Fixed Asset/Asset Group Report allows you to select a specified asset master record or a group of asset master records that are associated as attachments or components. This report shows all of the data elements which appear in the FFRMAST report.
Parameters
Name
Required?
Description
Values
Specific Asset(s)
No
Specific asset tag number for reporting. The asset tag can be an origination tag or a permanent tag. Multiple entries and wildcard characters are permitted. This parameter is required if the Primary Tag parameter is not entered. Permanent tag number of the parent asset. This tag number appears on the asset master records that are associated with the parent asset as attachments or components. This parameter is required if the Specific Asset parameter is not entered. This parameter takes precedence over Specific Asset if both are entered.
Primary Tag
No
4-117
November 2010
12-DEC-1996 14:08:58
Banner Development Environment Fixed Asset/Asset Group Report DATE: DATE: SUB TYPE C/A: IN USE IND: Vehicles GIFT ITEM: N ACQUISITION CODE: DN ACQUISITION DATE: 05-NOV-1996 WORK IN PROGRESS: 30-OCT-1996 28-OCT-1996 N SYSTEM STATUS: USER STATUS: TITLED TO: COND CODE: I
PAGE 1 FFRAGRP 3.0
PERMANENT TAG: TP72 ORIGINATION TAG: T00000072 PRIMARY TAG: DESCRIPTION: COMMODITY: ASSET TYPE: Vehicles TFX003 AC
Auxiliary Services
RESPONSIBLE CHART: RESPONSIBLE ORGANIZATION: LOCATION: TRANSFER DATE:
A 629 10
Banner University Auxiliary Services
------------------------------------------------VENDOR: PO NUM JRP9704 FR09 PO ITEM 1 Fisher Ford, INV NUM INV9704 INV ITEM 1
ACQUISITION DATA
-------------------------------------------------
INV DATE 28-OCT-1996
RCVD NUM RCR9704
RCVD DATE
IN SERV DATE
LAST INV DATE
PCT USED
Make: Ford Model: 4x4 Manufacturer: Ford Replacement Book Value Market Value
Serial Number/VIN: Part #/Vehicle Tag: Barcode: User Ref Number: Insurance
5678 9325 7623 EXP 104
Total Cost 41,078.00 ------------------------------------------------Pct 100 Original Cost 41,078.00 Attachment
------------------------------------------------Fund 1010 Orgn 629 Acct 2140 Prog 920
FUNDING SOURCE DATA Actv Locn 10
------------------------------------------------Cap Date: 28-OCT-1996 Cap Fund 4998
CAPITALIZATION DATA Asset Acct 1930 Eq Acct 3901 Pct 100
------------------------------------------------Capitalization 41,078.00 Attachment
4-118
November 2010
12-DEC-1996 14:08:58
Banner Development Environment Fixed Asset/Asset Group Report
PAGE 2 FFRAGRP 3.0
PERMANENT TAG: TP82 ORIGINATION TAG: T00000082 PRIMARY TAG: TP72 DESCRIPTION: COMMODITY: ASSET TYPE: Trailer TFX004 AC
DATE: DATE: SUB TYPE C/A: IN USE IND: Trailer
31-OCT-1996 31-OCT-1996 C N
SYSTEM STATUS: USER STATUS: TITLED TO: COND CODE:
G I 10
RESPONSIBLE CHART: RESPONSIBLE ORGANIZATION: LOCATION: TRANSFER DATE:
A 629 10
University Auxiliary Services
GIFT ITEM: ACQUISITION CODE: ACQUISITION DATE: WORK IN PROGRESS:
Y DN 30-OCT-1996 N
------------------------------------------------VENDOR: PO NUM PO ITEM INV NUM INV ITEM INV DATE
ACQUISITION DATA
-------------------------------------------------
RCVD NUM
RCVD DATE 30-OCT-1996
IN SERV DATE
LAST INV DATE
PCT USED
Make: Ford Model: Manufacturer: Ford Replacement 10,000.00 Book Value 10,030.00 Market Value 10,030.00
Serial Number/VIN: Part #/Vehicle Tag: Barcode: User Ref Number: Insurance 10,200.00 USER ATTRIBUTES
T532 5463 1271
Total Cost 10,100.00 -------------------------------------------------
------------------------------------------------CATEGORY F
------------------------------------------------Fund 3100 Orgn 12603 Acct 1930 Prog 90
FUNDING SOURCE DATA Actv Locn 10 Pct 33
------------------------------------------------Original Cost 10,100.00 Attachment
------------------------------------------------Cap Date: 31-OCT-1996 Cap Fund 3100
CAPITALIZATION DATA Asset Acct 1930 Eq Acct 3901 Pct 100
------------------------------------------------Capitalization 10,100.00 Attachment
4-119
November 2010
12-DEC-1996 14:08:58
Banner Development Environment Fixed Asset/Asset Group Report
PAGE 3 FFRAGRP 2.1.11
Parameter Name _____________________________ Parameter Seq No Parameter From Asset Tag Primary Tag Number of lines per page Record Count
* * * REPORT CONTROL INFORMATION * * * Value Message ________________ ____________________________________________________________ 27058 Host TP72 55 2
4-120
November 2010
Fixed Asset DTAG Aging Report (FFRDTGA)

Description
This report displays the aging of Pending Dtags as of a given cutoff date. Information displays on the report by document type (Journal Voucher, Direct Cash Receipts, Stores Issues) and provides a breakdown of the account over different periods, such as 31-60 days, 61-90 days, and over 90 days.
Parameters
Name
Required?
Description
Values
01 02 03 04
COA Fund Account Aging by
No No No No
Code for the chart of accounts. Fund code associated with the Dtag. Account code associated with the Dtag. One of two options for aging of Dtags.
Valid chart of accounts or blank for All (default value) Valid fund code or blank for All (default value) Valid account code or blank for All (default value) 1 2 Document transaction date (default value) Dtag extract date
05
Cutoff date
No
Date for which report is to be run.
Valid date or sysdate (default value)
4-121
November 2010
24-JUN-2002 11:09:05 AM
Development Fixed Asset DTAG Aging Report (31 to 60 days) ------------------------Count Amount (61 to 90 days) ------------------------Count Amount 5 6 1,800.00 1,500.00
PAGE 1 FFRDTGA (over 90 days) ------------------------Count Amount 6 2 11,000.00 1,765.14
(0 to 30 days) ----------- ------------------------Count Amount
Document Type: DCR Direct Cash Receipts P 0 0.00 4 -100,003,100.00 Document Type: ISS Issues P 0 0.00 1 8,830.71 Document Type: JV Journal Document P 9 -18,066.67 26 100,012,110.00 ----------- ------------------------------------------------Summary P 9 -18,066.67 31 17,840.71 ----------- -------------------------------------------------
20 8,345.00 ------------------------31 11,645.00 -------------------------
11 -4,966.35 ------------------------19 7,798.79 -------------------------
24-JUN-2002 11:09:05 AM
Development Fixed Asset DTAG Aging Report * * * REPORT CONTROL INFORMATION * * *
PAGE 2 FFRDTGA
Chart of Account: Fund Code: Account Code: Aging by: 1 Cutoff date: 30-JUN-2002 Activity Date: 24-JUN-2002
4-122
November 2010
Fixed Asset DTAG Transaction Report (FFRDTGT)

Description
This report displays Dtag transaction information as specified in the parameters of the report.
Parameters
Name
Required?
Description
Values
Document Number Include Document Text
No No
Non-invoice document number. Document text indicator.
Specific document or blank for all Y N Yes (default) No Journal Voucher Direct Cash Receipt All (default) Pending Resolved All (default)
Document Type
No
Document type of the source document.
1 2 blank
Dtag Status
No
Status of the document tag.
P R Blank
Dtag from Date Dtag To Date COA Fund Code Account Code Sort Option
No No No No No No
Beginning date for the Dtag. Ending date for the Dtag. Code for the Chart of Accounts. Fund code associated with the Dtag. Account code associated with the Dtag. Sort order for items in the report.
Valid date or 01-Oct.-1988. Valid date or sysdate. Sysdate (that is, current date) is the default value. Valid COA or blank for All (default value) Valid Fund or blank for All (default value) Valid Account code or blank for All (default value) 1 2 Chart of Accounts (default) Document number
4-123
November 2010
24-JUN-2002 11:04:02 AM
Development Fixed Asset DTAG Transaction Report Dtag Date Ptag Otag Action Date Document Ref
PAGE 1 FFRDTGT
Doc Seq
Dtag
Dtag Stat JV
COA
Fund
Orgn
Account
Prog
Location
Deposit
Amount
Document Type:
Journal Document Transaction Date: 06/03/02 B B B B B 1110 1110 1110 1110 1110 09 09 09 09 09 7810 7810 7810 7810 7810 Extraction Date: 06/03/02 90 90 90 90 90 06/04/02 -1,200.00 -1,200.00 -1,200.00 -1,200.00 -1,200.00 -6,000.00
Document Number: J0003048 Document Text: 1 2 3 4 5 D00007000 D00007001 D00007002 D00007003 D00007004 R P P P P 06/03/02 06/03/02 06/03/02 06/03/02 06/03/02 N00000287 T00007025
Document J0003048 Total: Document Number: J0003069 Document Text: 1 D00007005 P 06/06/02 N00000294 Transaction Date: 06/06/02 B 1110 09 7810 Extraction Date: 06/06/02 90 Document J0003069 Total: Document Number: J0003074 Document Text: 1 D00007006 R 06/11/02 N00000298 Transaction Date: 06/11/02 B 1110 09 7810 Extraction Date: 06/11/02 90 06/11/02 Document J0003074 Total: Document Number: J0003075 Document Text: 1 D00007007 R 06/11/02 N00000299 Transaction Date: 06/11/02 B 1110 10 7810 Extraction Date: 06/11/02 20 06/11/02 Document J0003075 Total:
-4,916.67 -4,916.67
-1,500.00 -1,500.00
-1,750.00 -1,750.00
4-124
November 2010
Document Number: J0003076 Document Text: 1 2 3 4 5 D00007008 D00007009 D00007010 D00007011 D00007012 R R P P P 06/11/02 06/11/02 06/11/02 06/11/02 06/11/02 N00000300 N00000301
Transaction Date: 06/11/02 B B B B B 1110 1110 1110 1110 1110 09 09 09 09 09 7810 7810 7810 7810 7810
Extraction Date: 06/11/02 90 90 90 90 90 06/11/02 06/11/02 -1,750.00 -1,750.00 -1,750.00 -1,750.00 -1,750.00 -8,750.00
Document J0003076 Total: Document Number: J0003079 Document Text: 24-JUN-2002 11:04:02 AM Transaction Date: 06/12/02 Extraction Date: 06/12/02
Development Fixed Asset DTAG Transaction Report Dtag Date Ptag Otag N00000306 Action Date 06/12/02 Document J0003079 Total: Document Ref
PAGE 2 FFRDTGT
Doc Seq 1
Dtag D00007013
Dtag Stat R
COA B
Fund 1110
Orgn 09
Account 7810
Prog 90
Location
Deposit
Amount -1,750.00 -1,750.00
06/12/02
Document Number: J0003080 Document Text: 1 2 D00007014 D00007015 P R 06/12/02 06/12/02 N00000308
Transaction Date: 06/12/02 B B 1110 1110 09 09 7810 7810
Extraction Date: 06/12/02 90 90 -3,100.00 -3,000.00 -6,100.00 Amount -18,066.67 -12,700.00 -30,766.67
06/12/02 Document J0003080 Total:
Document Type Summary: P R Total
Count 9 7 16
4-125
November 2010
24-JUN-2002 11:04:02 AM
Development Fixed Asset DTAG Transaction Report * * * REPORT CONTROL INFORMATION * * *
PAGE 3 FFRDTGT
Document Number: Document Text: Y Document Type: Dtag Status: Dtag From Date: 01-JUN-2002 Dtag To Date: 24-JUN-2002 Chart of Account: Fund Code: Account Code: Sort Option: 2 Activity Date: 24-JUN-2002
4-126
November 2010
Fixed Asset Master Record Report (FFRMAST)

Description
This report produces a printed record of all of the data appearing on the Asset Master record for selected assets.
Parameters
Name
Required?
Description
Values
System Status of the asset
No
Current system status of the fixed asset master record.
D R I G C V M
Disposed Origination tag created from receiving document Origination tag created from invoice document Gift/donation Cancelled invoice or check Converted incomplete Converted complete
User Status of the asset
No
One-character user-defined status code for this asset. Validated against FTVSDAT; the Entity is FFBMAST and the Attribute is User_Status_Code. Chart of accounts for reporting. Organization for reporting. Location for reporting. User-defined code which describes an asset category. Asset condition code used to describe the physical condition of the asset.
Responsible Chart of Accounts Responsible Organization Responsible Location Asset Type Condition Code
No No No No No
4-127
November 2010
Parameters (cont)
Name
Required?
Description
Values
Title-To Code Depreciation Method
No No
Code for the entity owning the asset (i.e., who the asset is titled-to). User-defined designation for the combination of internal depreciation method code and first year option. Leave blank to include all depreciation method codes. Assigned frequency factor for calculating and recording depreciation. Leave blank unless Depreciation Method is valued and only depreciated equipment is being requested. A M S Q Annual (default) Monthly Semi-annual Quarterly
Depreciation Frequency
No
4-128
November 2010
10-30-2002 15:39:06
DEVELOPMENT Fixed Asset Master Report
PAGE 1 FFRMAST 5.3.1
PERMANENT TAG: N00000273 ORIGINATION TAG: T00006481 PRIMARY TAG: DESCRIPTION: COMMODITY: ASSET TYPE:
DATE: DATE: SUB TYPE C/A: TAG IN USE:
07-MAY-2002 14-NOV-2001
SYSTEM STATUS: USER STATUS: TITLED TO: COND CODE:
Furniture, Office, Capital 1110000000 Furniture, Office, Capital BK Bookstore Fixtures GIFT ITEM: N ACQUISITION CODE: ACQUISITION DATE: WORK IN PROGRESS: -------------------------------------------------
RESPONSIBLE CHART: B Chart of Accounts B RESPONSIBLE ORGANIZATION: 10 Administrative Support LOCATION: TRANSFER DATE: ------------------------------------------------ACQUISITION DATA VENDOR: PO NUM Make: Model: Manfr: Replacement Book Value V1 PO ITEM 0 Office Max, INV NUM I0009898 INV ITEM 1 INV DATE 14-NOV-2001 RCVD NUM
RCVD DATE
IN SERV DATE
LAST INV DATE DTAG Src: Doc Type: Sub Num: Seq Num:
PCT USED
Serial Number/VIN: Part #/Vehicle Tag: Barcode: User Ref Number: Market Value Insurance Total Cost 1,250.00
4-129
November 2010
10-30-2002 15:39:06 ------------------------------------------------Fund 1009 1110 Orgn 10 09 Acct 7810 7810 Prog 20 90
DEVELOPMENT Fixed Asset Master Report FUNDING SOURCE DATA Actv Locn Pct 17 83
PAGE 2 FFRMAST 5.3.1 ------------------------------------------------Original Cost 200.00 1,000.00 Attachment Orig Doc I0009898 J0002949
------------------------------------------------Cap Date: 14-NOV-2001 Cap Fund 9601 9601
CAPITALIZATION DATA Asset Acct 1930 1930 Eq Acct 3550 42000 Pct 20 80
------------------------------------------------Capitalization 250.00 1,000.00 Attachment
------------------------------------------------METHOD DD FREQ A START DATE EST LIFE 10 REM LIFE 120
DEPRECIATION DATA ACCUM DEPR .00
------------------------------------------------SALVAGE VALUE LAST DEPR DATE
10-30-2002 15:39:06
DEVELOPMENT Fixed Asset Master Report
PAGE 4 FFRMAST 5.3.1
Parameter Name _____________________________ Parameter Seq No Parameter From System Status User Status Responsible COA Responsible Organization Responsible Location Asset Type Condition Code Title To Depreciation Method Depreciation Frequency Number of lines per page: Record Count
* * * REPORT CONTROL INFORMATION * * * Value ________________ 980389 Job Submission
BK
A 55 3
4-130
November 2010
Fixed Asset Procurement Report (FFRPROC)

Description
This report produces a single-line printed display of the procurement and payable information related to an asset master record for each selected asset. If this report is run from the host, you will only be prompted for those parameters that apply to your selection for the Selection Criteria parameter.
Parameters
Name
Required?
Description
Values
Selection Criteria
Yes
Allows you to select asset master records based on one of three criteria (see Values column).
1 2 3
Specific document Funding source COA/Fund/ Account User status/vendor (default)
Chart of Accounts Document Type
No No
Chart(s) of accounts for selection. This parameter is required only if Selection Criteria = 2. Document type. This parameter is required only if Selection Criteria = 1. 1 2 3 4 Invoice Purchase Order Receiving Permanent Tag
Document Number
No
Document number. Entry of permanent tag number is allowed. This parameter is required only if Selection Criteria = 1. Determines whether the report is restricted to capitalized records. This parameter is required only if Selection Criteria = 2 or 3. Y N Yes No (default)
Print Capitalized Data Only?
No
4-131
November 2010
Parameters (cont)
Name
Required?
Description
Values
From Date
No
Starting Origination Tag date for the range of assets to be included in the report. Leave the From Date and To Date parameters blank to include all tags. This parameter is required only if Selection Criteria = 2 or 3. Ending Origination Tag date for the range of assets to be included in the report. Leave the From Date and To Date parameters blank to include all tags. This parameter is required only if Selection Criteria = 2 or 3. Funding source fund code (from Asset Master Funding Source record FFRMASF). Multiple entries and wildcard characters are permitted. This parameter is required only if Selection Criteria = 2. Funding source account code (from Asset Master Funding Source record FFRMASF). Multiple entries and wildcard characters are permitted. This parameter is required only if Selection Criteria = 2. Current system status of the fixed asset master record. This parameter is required only if Selection Criteria = 3. D R I G C V M Disposed Origination tag created from receiving document Origination tag created from invoice document Gift/donation Cancelled invoice or check Converted incomplete Converted complete
To Date
No
Funding Fund
No
Funding Account
No
System Status
No
4-132
November 2010
Parameters (cont)
Name
Required?
Description
Values
User Status
No
One-character user-defined status code for this asset. Validated against FTVSDAT; the Entity is FFBMAST and the Attribute is User_Status_Code. This parameter is required only if Selection Criteria = 3. Vendor code that is presumably associated with the desired asset master records. This parameter is required only if Selection Criteria = 3. Enter Y for this parameter to print Funds and Accounts in the Control Report. Y or N
Vendor Code
No
Print Funds and Accounts?
No
4-133
November 2010
Report Sample (Selection Criteria = 3) (Page 1 of 2)
PAGE REPORT : FFRPROC 5.3.1 RUN DATE 10/29/2002 RUN TIME 02:26 PM DEVELOPMENT Fixed Asset Procurement Report Reporting Period: 01-JAN-2002 To: 29-OCT-2002
----------------------------------------------------------------------- -----------------------------------------------------------Permanent Origination Asset Description PO Number Invoice INV Receiving Vendor name DTAG Doc Amount Cap Tag Tag Number Item Number Source Type ----------------------------------------------------------------------- -----------------------------------------------------------T00006742 Furniture I0010185 1 J & B Construction 1,100.00 Y T00006743 Furniture I0010187 1 J & B Construction 1.00 T00006744 Furniture I0010190 1 J & B Construction 1,100.00 Y T00006745 P5-100 w/32Mb EDO, 4Gb I0010191 1 J & B Construction 1,210.00 Y T00006746 P5-100 w/32Mb EDO, 4Gb I0010193 1 J & B Construction 1,210.00 T00006747 P5-100 w/32Mb EDO, 4Gb I0010194 1 J & B Construction 1.10 T00006748 P5-100 w/32Mb EDO, 4Gb I0010195 1 J & B Construction 1,210.00 Y T00006749 P5-100 w/32Mb EDO, 4Gb I0010196 1 J & B Construction 3.30 T00006750 P5-100 w/32Mb EDO, 4Gb I0010197 1 J & B Construction 1,210.00 Y T00006751 P5-100 w/32Mb EDO, 4Gb I0010198 1 J & B Construction 1.10 Y T00006752 P5-100 w/32Mb EDO, 4Gb I0010199 1 J & B Construction 1,210.00 Y T00006753 P5-100 w/32Mb EDO, 4Gb I0010200 1 J & B Construction 11.00 T00006754 P5-100 w/32Mb EDO, 4Gb I0010201 1 J & B Construction 1,210.00 T00006755 P5-100 w/32Mb EDO, 4Gb I0010202 1 J & B Construction 10.00 T00006756 Furniture P0006786 I0010206 1 Office Supply Co. SRC00666 DCR 1,100.00 Y T00006757 Furniture P0006788 I0010207 1 Office Supply Co. 3.00 Y T00006758 Furniture P0006785 I0010208 1 Office Supply Co. 3.00 T00006759 Furniture I0010211 1 Office Supply Co. 1,100.00 Y T00006760 P5-100 w/32Mb EDO, 4Gb I0010212 1 J & B Construction 1,210.00 Y T00006761 Furniture P0006786 I0010213 1 Office Supply Co. SRC00666 DCR 1,100.00 Y T00006762 Furniture P0006788 I0010214 1 Office Supply Co. 3.00 Y T00006763 Furniture P0006785 I0010215 1 Office Supply Co. SRC00666 DCR 3.00 T00006764 P5-100 w/32Mb EDO, 4Gb P0006787 I0010216 1 J & B Construction 3.30 T00006765 Furniture I0010217 1 Office Supply Co. 1,100.00 Y T00006766 Furniture I0010218 1 Office Supply Co. 3.00 T00006767 P5-100 w/32Mb EDO, 4Gb P0006777 I0010219 1 J & B Construction 1,210.00 Y T00006768 P5-100 w/32Mb EDO, 4Gb P0006787 I0010220 1 J & B Construction 3.30 T00006771 Furniture P0006790 I0010222 1 Office Supply Co. 1.00 T00006772 Furniture P0006793 I0010223 1 Office Supply Co. 1,100.00 Y T00006773 test Grand Total 131,419.67
4-134
November 2010
Report Sample (Selection Criteria = 3) (Page 2 of 2)
PAGE REPORT : FFRPROC 5.3.1 RUN DATE 10/29/2002 RUN TIME 02:26 PM * * * REPORT CONTROL INFORMATION (FFRPROC release 5.3.1) * * * DEVELOPMENT Fixed Asset Procurement Report Reporting Period: 01-JAN-2002 To: 29-OCT-2002
Parameters have been entered via Job Submission. Parameter Name _____________________________ Parameter Seq No: Chart of Accounts Capitalized assets only Parameter Selection Criteria Document type option Document Code From Date To Date System Status Code User Status Code Vendor Code Funding Source Fund Funding Source Account Line Count Number of records selected Value ________________ 978560 B N 3 01-JAN-2002 29-OCT-2002 Message ____________________________________________________________ Chart of Accounts B Select master attributes
55 412
4-135
November 2010
Fixed Asset Property Report (FFRPROP)

Description
This is a report that may be used when taking a physical inventory of your fixed and moveable assets. It produces a single-line display of the responsible party information from the Asset Master record (FFBMAST) for each selected asset.
Parameters
Name
Required?
Description
Values
Chart of Accounts Inventory Selection Option
No No
Chart of accounts for which the assets are to be inventoried. Determines whether inventoried, uninventoried, or both types of tags are reported. 1 2 3 Inventoried tags Uninventoried tags Both (default)
From Date
No
Starting Origination Tag date for the range of assets to be included in the report. Leave the From Date and To Date parameters blank to include all tags. Ending Origination Tag date for the range of assets to be included in the report. Leave the From Date and To Date parameters blank to include all tags. The current system status of the fixed asset master record. D R I G C V M Disposed Origination tag created from receiving document Origination tag created from invoice document Gift/donation Cancelled invoice or check Converted incomplete Converted complete
To Date
No
System Status Code
No
4-136
November 2010
Parameters (cont)
Name
Required?
Description
Values
User Status Code
No
One-character user-defined status code for this asset. Validated against FTVSDAT; the Entity is FFBMAST and the Attribute is User_Status_Code. Permanent tag number of the parent asset. Commodity code associated with the asset tag. User-defined code which describes a category or grouping of assets. Identification number for the party responsible for the custody of an asset or group of assets.
Primary Asset Tag Commodity Code Asset Type Custodian ID Title To Code Acquisition Method Code Responsible Organization Responsible Location
No No No No
No
Organization responsible for the custody of an asset or group of assets. Multiple entries and wildcard characters are permitted. Physical location where an asset or group of assets is located. Multiple entries and wildcard characters are permitted. Primary and secondary sort order for the items in the report. 1 2 3 4 Custodian/Permanent Tag Responsible Location/Permanent Tag Responsible Organization/ Permanent Tag Permanent Tag Only (default value)
No
Sort Option
No
4-137
November 2010
PAGE REPORT : FFRPROP 3.0 RUN DATE 12/12/1996 RUN TIME 12:26 PM Location: 01 Urban Campus Banner Development Environment Fixed Asset Property Report Reporting Period: 01-OCT-1996 To: 31-OCT-1996
----------------------------------------------------------------------- ----------------------------------------------------------Permanent Origination Asset Primary Sub Status Cond Custodian Locn Orgn Cost Tag Tag Description Asset Tag typ Sys Usr code ----------------------------------------------------------------------- ----------------------------------------------------------AP0061 T00000061 Computer I GD Edwards, L 11001 1,200.00 T00000266 Equipment AP0061 A I GD Edwards, L 11001 1,000.00 JC0001 T00000028 Vehicles I L GD 11002 6,600.00 T00000002 Furniture I PR 500.00 Location Total 9,300.00
4-138
November 2010
PAGE REPORT : FFRPROP 3.0 RUN DATE 12/12/1996 RUN TIME 12:26 PM Location: 01 Urban Campus Banner Development Environment Fixed Asset Property Report Reporting Period: 01-OCT-1996 To: 31-OCT-1996
----------------------------------------------------------------------- ----------------------------------------------------------Permanent Origination Asset Primary Sub Status Cond Custodian Locn Orgn Cost Tag Tag Description Asset Tag typ Sys Usr code ----------------------------------------------------------------------- ----------------------------------------------------------AP0001 T00000001 Constructed/Acquired B G G GD Robertson, S 10 11009 501,078.00 T00000070 Vehicles AP0001 A I R GD Robertson, S 10 11009 1,078.00 AP0004 T00000004 Temporary Buildings I PR Martin, F 10 11001 11,000.00 AP0005 T00000005 Temporary Buildings AP0004 C I R GD Martin, F 10 11001 14,750.00 T00000003 Roof material AP0005 A I GD Martin, F 10 11001 3,750.00 AP0006 T00000006 Vehicles I I EXL McIntyre, P 10 11003 7,000.00 AP0010 T00000010 Vehicles I GD McIntyre, P 10 11001 5,940.00 AP0011 T00000011 Vehicles I L GD McIntyre, P 10 11001 5,940.00 AP0012 T00000012 Vehicles I L GD McIntyre, P 10 11001 5,940.00 AP0016 T00000016 Furniture I N PR McIntyre, P 10 11001 2,344.45 AP0025 T00000025 Constructed/Acquired B I L GD McIntyre, P 10 11003 501,078.00 TP82 T00000082 Equipment TP72 C G G EXL Martin, F 10 126012 1,100.00 T00000083 Furniture TP82 A G I EXL Martin, F 10 126012 300.00 Location Total Grand Total 1,061,298.45 1,070,598.45
4-139
November 2010
PAGE REPORT : FFRPROP 3.0 RUN DATE 12/12/1996 RUN TIME 12:26 PM * * * REPORT CONTROL INFORMATION (FFRPROP release 3.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Parameter Seq No : Chart of Accounts Tag Selection Option From Last Inventoried Date To Last Inventoried Date From Tag Date To Tag Date System Status Code User Status Code Primary Asset Tag Commodity Code Asset Type Custodian ID Parameter Sort Option Responsible Organization Responsible Location Line Count Permanent tags selected Attachments selected Value ________________ 27027 B 3 01-OCT-1996 31-OCT-1996 Message ____________________________________________________________ Banner University Both Inventoried and Uninventoried Tags Banner Development Environment Fixed Asset Property Report Reporting Period: 01-OCT-1996 To: 31-OCT-1996
2 Y Y 55 13 4
Sort on Location/Permanent Tag All Organizations All Locations
4-140
November 2010
General Ledger Module

This section describes each report in the General Ledger module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their sevencharacter names.
Note Some reports in this module are grouped according to functionality.
4-141
November 2010
Data Extract Process (FGPGEXT)

Description
This process runs via job submission to generate GASB reports. The Data Extract Process uses the parameters you enter to extract the appropriate information from the General Ledger (FGBGENL) and Operating Ledger (FGBOPAL) tables to the FGWREPT table. For additional information about GASB, refer to Chapter 2, Processing. If the extract is run for a Chart and End Date that already exists in the table, all records will be replaced. Reclassification entries are stored separately and are not affected. If the extract is run in Purge mode, then records for the Chart, End Date, and Report Type(s) indicated are removed and not replaced. If any changes are made to Attribute associations or any additional transactions are posted to the ledgers, the extract must be re-run before the changes are reflected in the reports. This is not required for reclassification entries via FGARCLE. If any FOAPAL elements do not have attributes selected, or have duplicate associations, this process generates error reports. Another report identifies FOAPAL elements intentionally excluded from the GASB statements. For samples of each of these error reports, refer to the GASB Report Examples section at the end of this chapter.
Parameters
Name
Required?
Description
Values
Chart of Accounts End Date of Period Reported
Yes Yes
Chart of accounts for which data is to be extracted. End date for reporting. (This is converted to the fiscal year and period in which the date entered falls. The extract includes all data to the end of that period.) Indicates if accrual should be included. Extract for GASB 34 Statement of Net Assets and Statement of Activities Extract for GASB 34 Balance Sheet and Statement of Revenues, Expenditures, and Changes in Fund Balances
Valid Chart of Accounts Valid end date
Include Accrual Government Wide Financials Governmental Funds Financials
No No No
Y/N Y/N Y/N
4-142
November 2010
Parameters (cont)
Name
Required?
Description
Values
Public Inst BTA Financials Processing Mode
No
Extract for GASB 35 Statement of Net Assets and Statement of Revenues, Expenses, and Changes in Net Assets Processing mode
Y/N
Yes
Extract data (replaces existing data for chart, fiscal year/period and report pairs indicated Purge data for chart, fiscal year/ period, and report pair(s) indicated
4-143
November 2010
Account Index Report (FGRACCI)

Description
This report displays a list of account indexes and the default accounting distribution associated with each index.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date (DD-MON-YYYY)
Yes Yes
Chart of Accounts for reporting (validated against FTVCOAS). Date to select data for reporting. DD-MON-YYYY Default = current date
Report Sample
REPORT FGRACCI CHART: A
Banner University Account Index Report AS OF 18-DEC-1996 FUND O ORGN O Y Y Y N Y Y Y Y Y Y ACCT 5010 5020 5030 7013 7012 7011 8010 O N N N Y N N Y N Y N PROG 100 100 100 100 100 500 100 O Y Y Y Y Y Y Y Y Y Y ACTV O N N N Y N N Y N N N LOCN O STATUS N N N Y N N Y N N N A A A A A A A A A A
RUN DATE: 12/18/1996 TIME: 10:15 AM PAGE: 1 ********* DATES ********* EFF TERM NEXTCHANGE
INDEX 91-10 91-20 91-30 CASH COMP DUPE HEALTH OFFICE PARK TRAVEL
DESCRIPTION General Tax Revenues - FY 90/91 Sales Tax Revenues - FY 90/91 Property Tax Revenues - FY 90/91 Fund Raising Computing Supplies Duplicating Supplies Health Department Office Supplies Grounds Maintenance Travel Reimbursement
101000 Y 11-14 101000 Y 11-14 101000 Y 11-14 Y 11-14 101000 Y 101000 Y Y 101000 Y 201040 N Y
01-OCT-1995 01-OCT-1995 01-OCT-1995 13-MAR-1994 01-OCT-1995 01-OCT-1995 13-MAR-1994 01-OCT-1995 13-MAR-1993 13-MAR-1993
4-144
November 2010
Posting Process (FGRACTG)

Description
This process generates the postings to the financial ledgers for those transactions that have been edited, completed, and approved. Posting can be executed using a sleep/wake routine. This is the only program that updates finance ledgers. There is no output for this process. It is recommended that this process be run in background or sleep/wake-up mode. For additional information on sleep/wake-up mode, refer to the Reports and Processes chapter in the Banner Finance TRM Supplement. Document Management If you cancel a purchase order which was created from the requisition, the requisition items are released to be assigned to new purchase orders. In addition, the requisition encumbrance will be reinstated. FGRACTG uses the Cancel Date as the transaction date for canceling requisitions, purchase orders, and invoices. Encumbrances are marked closed when a purchase order or a requisition is cancelled. Currency Conversion When processing an invoice for which foreign currency was used, FGRACTG: selects the Accounts Payable Account from the currency conversion table as the posting modifier for the invoice rule and computes the difference between the invoice amount and the converted amount (both values are stored on FARINVA) and posts the difference to the exchange account from the currency conversion table. Commodity Level Tax At invoice processing time, FGRACTG calculates exemption percents as defined on the Tax Rate Table (FTVTRAT). This process also reverses the exempt tax expense and creates the appropriate receivable. Grant Accounting Transactions When grant activity is posted using rules containing a 0030 process code, the associated revenue recognition, indirect cost recovery, and cost share transactions are automatically generated.
4-145
November 2010
Print Current Release Version Numbers The posting process prints the current release version numbers of each of the Pro*C objects that are compiled and linked together to form the executable FGRACTG. When posting is started via the operating system prompt, the release numbers will be displayed on the screen. If the posting process is started via job submission, the release numbers will be printed in the log file. Zero Payment Invoices This process posts the debit and credit side of the invoice accounting lines and marks a zero payment invoice as paid. No check will ever be attached to zero payment invoices marked as "Paid". e-Procurement for HigherMarkets If you are using Finance e-Procurement with HigherMarkets, this process publishes messages whenever a Banner Requisition or Purchase Order that originated from a HigherMarkets document is posted or rolled back. For detailed information, please refer to the Finance eProcurement with HigherMarkets Banner Handbook.
Report Sample
Starting Starting Starting Starting Starting Starting Starting Starting Starting Starting Starting Starting Starting
FGRACTG (Rel 2.0.7) at 05-AUG-1996 04:35:44 document J0000108 (Document type 20 ) at 05-AUG-96 document J0000109 (Document type 20 ) at 05-AUG-96 document J0000110 (Document type 20 ) at 05-AUG-96 document J0000111 (Document type 20 ) at 05-AUG-96 document J0000112 (Document type 20 ) at 05-AUG-96 document J0000113 (Document type 20 ) at 05-AUG-96 document J0000114 (Document type 20 ) at 05-AUG-96 document J0000115 (Document type 20 ) at 05-AUG-96 document J0000116 (Document type 20 ) at 05-AUG-96 document J0000117 (Document type 20 ) at 05-AUG-96 document J0000118 (Document type 20 ) at 05-AUG-96 document J0000119 (Document type 20 ) at 05-AUG-96
04:35:50 04:36:30 04:36:38 04:36:47 04:36:54 04:37:07 04:37:22 04:37:39 04:37:59 04:38:09 04:38:16 04:38:32
4-146
November 2010
Account Hierarchy Report (FGRACTH)

Description
This report displays the hierarchical relationship of the account type and account code structures.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date (DD-MON-YYYY) Account Type Code
Yes Yes
Chart of Accounts for reporting (validated against FTVCOAS) Date that the report will use to select account codes for reporting. If an account type is entered, the report only includes account codes for this account type (validated against FTVATYP). DD-MON-YYYY Default = current date
No
4-147
November 2010
Report Sample
REPORT FGRACTH CHART: A
Banner University Account Hierarchy Report AS OF 18-DEC-1996 DESCRIPTION Current Assets Current Assets Cash Accounts Operating Cash Account Operating Cash Account Payroll Cash Account Accounts Receivable Cash Awaiting Deposit Checks Awaiting Deposit Visa Receipts Master Card Receipts Payroll Clearing for Payroll Accounts Receivable Student Accounts Receivable Faculty Accounts Receivable Federal Grants Receivable State Grants Receivable State contracts Grad Student Accounts Receivable Interfund Accounts Due To/From Other Funds Cash Interfund Account Due From Other Funds Due To Other Funds Due From Other Funds Interchart Clearing Accounts Interchart A Clearing Accounts Due To/From Other Charts Equipment Assets Fixed Assets Equipment and Furniture Equipment - Computers Equipment - Classroom DATA ENTRY N Y Y Y N Y Y Y Y Y N Y N Y N Y Y N N N N Y N N N N N Y N STATUS A A A A A A A A A A A A A A A A A A A A A A A A A A A A A POOL ACCT
RUN DATE: 12/18/1996 TIME: 10:16 AM PAGE: 1 ********* DATES ********* EFF TERM NEXTCHANGE 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 26-OCT-1994 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 11-APR-1992 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995
TYP 01 10
ACCOUNT 1000 1010 1040 1020 1030 1050 1051 1052 1053 1060 1100 1110 1120 1130 1140 1150 1115 1200 1201 1210 1203 1205 1206 1300 1320 1301
15 A1 1800 1810 1820
4-148
November 2010
Activity Codes Report (FGRACTV)

Description
This report displays a list of activity codes for a specific chart of account.
Parameters
Name
Required?
Description
Values
Yes Yes
Chart of Accounts for reporting (validated against FTVCOAS) Date to select activity codes for reporting. DD-MON-YYYY Default = current date
4-149
November 2010
Report Sample
REPORT FGRACTV CHART: A
Banner University Activity Codes Report AS OF 18-DEC-1996 DESCRIPTION Course 001 Executive Management Financial Management Financial Cost Studies Course 101 Course 107 Financial Grants Management Systems Development Internal Audit Course 1200 Course 121 Course 123 Institutional Research Course 151 Research Proposals Course 205 R-21 Compliance Activities Benefit Analysis Telethons - Annual Support Capital Campaign - Theater Capital Campaign - Engineering Course 315 College Administration - Academic Department Chairs Technological Studies Business Studies Security Services Grounds Maintenance - Landscape Grounds Maintenance - Lawns Grounds Maintenance - Athletic Operations & Maintenance Health Services STATUS A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A ********* DATES ********* EFF TERM NEXTCHANGE 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995 01-OCT-1995
ACTIVITY 001 01 10 100 101 107 110 111 120 1200 121 123 130 151 200 205 210 212 300 310 312 315 40 400 410 430 50 500 502 504 506 60
4-150
November 2010
Available Balance Rebuild Process (FGRBAVL)

Description
This process is run on request and rebuilds the Budget Availability Ledger Table (FGBBAVL) when necessary. The budget rebuild process is based on the entire FOAPAL distribution for that budget. FGRBAVL needs to be run only if the rules controlling the available balance checking process are changed. The Available Balance Rebuild Process does not produce report output. The Budget Rebuild Process (FGRBAVL) requires exclusive access to the Budget Availability Ledger Table (FGBBAVL). The FGRBAVL process also makes extensive updates to the database since it deletes and rebuilds the entire FGBBAVL table. If you run it with only a single Save command at the end of the process, you may need an excessive number of rollback segments. If you use multiple commits, there is a risk that another available balance related process may update the table before you can relock the table. To alleviate this problem, the Budget Availability Ledger Process (FGRBAVL) uses a table called FGBBAVL_WORK. This table name is not referenced in any other Banner Finance Component. Using this method, FGRBAVL can perform multiple commits without the risk of other processes making updates. During the period this process runs, no other Banner Finance process or form which references FGBBAVL can run since the FGBBAVL table does not exist by that name. Because of this restriction, as well as the amount of processing that this process requires, you should always run FGRBAVL during off hours when no other Banner Finance process occurs. Banner Finance updates the FGBBAVL table during the normal posting of all accounting transactions by the Posting Process (FGRACTG). You only need to run FGRBAVL if the rules that control the available balance checking process change.
1. Before running FGRBAVL, export the FGBBAVL and FGRBAKO tables. This creates a backup of these
tables in case the process terminates abnormally.

2. Sign on to SQL*Plus as FIMSMGR. 3. Start FIMSBVL1 to rename FGBBAVL to FGBBAVL_WORK and to rename FGRBAKO to FGRBAKO_WORK,
respectively.
4. Run the FGRBAVL report from the command line. 5. After FGRBAVL finishes successfully, sign on to SQLPLUS as FIMSMGR and start FIMSBVL2 to rename
the FGBBAVL_WORK and FGRBAKO_WORK tables to their original names. Remember that you cannot execute any other process or forms which use FGBBAVL or FGRBAKO while you run FGRBAVL. If you do, an Oracle error displays stating that the Table or View does not exist.
4-151
November 2010
6. If the process terminates abnormally, import data from the export tables. Run FGRBAVL again.
Parameters
Name
Required?
Description
Values
Chart of Accounts Fiscal Year Fund Type Code Fund Code Start Range Fund Code End Range
Yes Yes No No No
Chart of Accounts for reporting Fiscal year for reporting Fund type code for reporting Fund code starting range for reporting Fund code ending range for reporting YY
4-152
November 2010
Cash Receipts Report (FGRCSRP)

Description
This report prints header and detail information for selected direct cash receipts. FGRCSRP can be used to print comprehensive information for one or more cash receipts based on the Document Number, Transaction Date, or Vendor Code. The default sort order for this report is by Vendor Code. You may run this report from job submission or online from the Direct Cash Receipt Form (FGADCSR). Access this report by selecting the Print Cash Receipt button on FGADCSR.
Parameters
Name
Required?
Description
Values
From Document Number No
Enter a value in this parameter to only print cash receipts with a document number greater than or equal to the document number specified. If left blank, there is no lower limit. Enter a value in this parameter to only print cash receipts with a document number less than or equal to the document number specified. If left blank, there is no upper limit. Enter a date in this parameter to print only cash receipts with a transaction date on or after the date specified. If left blank, there is no lower limit. Enter a date in this parameter to print only cash receipts with a transaction date on or before the transaction date specified. If left blank, there is no upper limit. Enter a value in this parameter to print only cash receipts for the vendor code specified. If this parameter is left blank, no vendors will be excluded and documents without a vendor code will be included. DD-MON-YYYY
To Document Number
No
From Transaction Date
No
To Transaction Date
No
DD-MON-YYYY
Vendor Code
No
4-153
November 2010
FGRCSRP
2.1.11
Banner Development Environment Cash Receipt Report National Supplies TRANS DATE: 27-NOV-1996 FSYR ---97 COAS ----B INDEX -----DOC TOTAL: 100.00 DOC STATUS: C
27-NOV-1996 11:22:20 Page
VENDOR CODE:
00010
DOC #: H0000358 SEQ NUM -------1 TXGRP ----SRG1
FUND ORGN ACCT PROG ACTV LOCN ------ ------ ------ ------ ------ -----1000 125 7210 100 BANK ---A1 CURR CODE --------TRANS AMT -----------20.00 CONV AMT ----------0.00 TAX AMT -----------3.00 REBATE AMT -----------1.40
DESCRIPTION ----------------------------------cash receipt DEP # -------DOC REF # ---------
________________________________________________________________________________________________________________ SEQ NUM -------2 TXGRP ----SRG1 FSYR ---97 COAS ----B INDEX -----FUND ORGN ACCT PROG ACTV LOCN ------ ------ ------ ------ ------ -----1010 125 6111 100 BANK ---A1 CURR CODE --------TRANS AMT -----------80.00 CONV AMT ----------0.00 TAX AMT -----------12.00 REBATE AMT -----------5.60
DESCRIPTION ----------------------------------cash receipt DEP # -------DOC REF # ---------
VENDOR TOTAL:
100.00
FGRCSRP
2.1.11
Banner Development Environment Cash Receipt Report
27-NOV-1996 11:22:20 Page
PARAMETER SEQUENCE NUMBER : 26322 FROM DOCUMENT NUMBER: H0000358 TO DOCUMENT NUMBER: H0000358 FROM TRANSACTION DATE: TO TRANSACTION DATE: VENDOR CODE: % NUMBER OF PRINTED LINES PER PAGE: NUMBER OF RECORDS PROCESSED: 1
55
4-154
November 2010
Grant Rebuild Process (FGRGRBD)

Description
This process is run on request and rebuilds the Grant Ledger Table (FRRGRNL) when necessary.
Note Grant transactions that occur after the project end date are not posted in period 14. Instead, the system posts these transactions to the actual grant year and period.
The Grant Rebuild Process (FGRGRBD) requires exclusive access to the Grant Ledger Table (FRRGRNL). The FGRGRBD process also makes extensive updates to the database since it deletes and rebuilds the entire FRRGRNL table. If you run it with only a single Save command at the end of the process, you may need an excessive number of rollback segments. If you use multiple commits, there is a risk that another grant related process may update the table before you can relock the table. To alleviate this problem, the Grant Rebuild Process (FGRGRBD) uses a table called FRRGRNL_WORK. This table name is not referenced in any other Banner Finance Component. Using this method, FGRGRBD can perform multiple commits without the risk of other processes making updates. During the period this process runs, no other Banner Finance process or form which references FRRGRNL can run since the FRRGRNL table does not exist by that name. Because of this restriction, as well as the amount of processing that this process requires, you should always run FGRGRBD during off hours when no other Banner Finance process occurs.
1. Before running FGRGRBD, export the FRRGRNL table. This creates a backup of this table in case the
process terminates abnormally.

2. Sign on to SQL*Plus as FIMSMGR. 3. Start FGRNBLD1 to rename FRRGRNL to FRRGRNL_WORK. 4. Run the FGRGRBD report from the command line; it is not available through job submission. 5. After FGRGRBD finishes successfully, sign on to SQLPLUS as FIMSMGR and start FGRNBLD2 to rename
to its original name. Remember that you cannot execute any other process or forms which use FRRGRNL while you run FGRGRBD. If you do, an Oracle error displays stating that the Table or View does not exist.
FRRGRNL_WORK
4-155
November 2010
6. If the process terminates abnormally, import data from the export tables. Run FGRGRBD again.
Parameters
Name
Required?
Description
Values
Chart of Accounts Grant Option
Yes Yes
Chart of Accounts for processing grants. Option for processing and rebuilding grants. A R Processes all grants Processes a range of grants; you must specify a value in the From Grant and To Grant parameters. Processes a specific grant; specify the grant code in the Grant Code parameter. Processes grants which fall within a wildcard value (for example, 21% processes all grants which begin with 21). Processes all grants (default)
A From Grant No You must have entered an R in the Grant Option parameter to use this parameter. Use this parameter to enter the first grant in the range. You must have entered an R in the Grant Option parameter to use this parameter. Use this parameter to enter the last grant in the range. This parameter is required only if you entered S or W in the Grant Option parameter.
To Grant
No
Grant Code
No
4-156
November 2010
08:43:38
Banner Development Environment Grant Rebuild Process 215501 215601 Grant rebuilt... Grant rebuilt...
PAGE 1 FGRGRBD
08:43:38
Banner Development Environment Grant Rebuild Process * * * REPORT CONTROL INFORMATION * * * Parameters have been entered from Host Prompt.
PAGE 2 FGRGRBD
Parameter Name _____________________________ Parameter Seq No: Chart: Grant Option Grant Grant Line Count:
Value ________________ 21931 B S 215501 215601 55
Message ____________________________________________________________ Specific
4-157
November 2010
End-of-Year Budget Carry Forward Report (FGRBDRL)

Description
This process rolls the remaining balance of any line item on OPAL elements to the new year. It will produce a hard copy report of the prior year's remaining budget balances that are carried forward into the current fiscal year. Current year records with Uncommitted Commit Type are retrieved for this report.
Report Sample
03/28/1996 08:52:01 FISCAL YEAR 96 Chart: A
Banner University End-of-Year Budget Carry Forward As of 01-NOV-1996
PAGE 1 FGRBDRL
Fund: 102000 Acct Type Revenue: Expense: Labor: Transfers: FUND TOTAL CHART TOTAL
Current Operating Funds Amount .00 -1,000.00 .00 .00 1,000.00 1,000.00 Rule J020 J020 J020 J020 Table COAS COAS COAS COAS
4-158
November 2010
Budget Status (Current Period) Report (FGRBDSC)

Description
This report is sorted by fund for each organization. The report displays adjusted budget, current and year-to-date activity, budget reservations, and the available balance for each account. This report prints both uncommitted and committed budget records, only uncommitted budget records, or only committed budget records. If the option to print both committed and uncommitted is selected, uncommitted records print first and committed records print separately.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts From Fund Code To Fund Code
Yes Yes No No
Fiscal year for reporting. Chart of accounts for reporting. First fund code in a series. Used to indicate which funds you want to include in the report. Last fund code in a series. Used to indicate which funds you want to include in the report. First organization code in a series. Used to indicate which organizations you want to include in the report. Last organization code in a series. Used to indicate which organizations you want to include in the report. First account code in a series. Used to indicate which accounts you want to include in the report. Last account code in a series. Used to indicate which accounts you want to include in the report. Date to select data for reporting.
YY
From Organization Code No
To Organization Code
No
From Account Code To Account Code As of Date (DD-MON-YYYY)
No No No
DD-MON-YYYY Default = System date
4-159
November 2010
Parameters (cont)
Name
Required?
Description
Values
Include Accrual Period
No
Indicates whether you want to include accrual periods in the report.
Y N Y N Y N U C
Include accrual periods. Do not include accrual periods. (default value) Print report totals. (default value) Do not print report totals. Print net totals. (default value) Do not print net totals. Print information about uncommitted budget records. Print information about committed budget records.
Print Report Totals
No
Indicates whether you want to print report totals on the report. Indicates whether you want to print net totals on the report. Indicates whether you want to print information about committed budget records, uncommitted budget records, or both.
Print Net Totals
No
Commitment Type Indicator
No
Blank Print information about both committed and uncommitted budget records. (default value)
4-160
November 2010
Report Sample
23-MAY-90 07:37:23 FISCAL YEAR 96
Banner University Budget Status (Current Period) As Of 31-OCT-1995 General Fund Environmental Services Waste Management ADJUSTED BUDGET .00 .00 .00 .00 .00 70.00 .00 .00 100.00 .00 .00 170.00 CURRENT PERIOD ACTIVITY .00 .00 .00 -200.00 .00 .00 .00 .00 .00 7,632.00 1,070.00 8,502.00 YEAR TO DATE ACTIVITY .00 .00 .00 -200.00 .00 .00 .00 .00 .00 7,632.00 1,070.00 8,502.00 BUDGET RESERVATIONS .00 .00 .00 .00 .00 .00 1,300.00 50.00 .00 .00 .00 1,350.00 AVAILABLE BALANCE
PAGE 1 FGRBDSC
FUND: PRED ORG: ORG: ACCOUNT 4150 4330 TOTAL 6010 6111 6120 6155 6160 6165 6170 6210 TOTAL
1000 110 120
ACCOUNT TITLE Other Income Indirect Cost Federal Grants Other Income Supplies Accounts Office Supply Accounts Travel Consulting Services Consulting Services Auditing Services Institution Match on Grants Interdepartmental Transfers General Expense
CMT TYP .00 .00 .00 U U
200.00 .00 70.00 -1,300.00 -50.00 100.00 -7,632.00 -1,070.00 -9,682.00
U U U U U U U U
4-161
November 2010
Balance Sheet Report (FGRBLSH)

Description
This report selects and prints balance sheet information for selected funds and fund types.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY) Include Accrual for Last Prd From Fund To Fund Excluding Fund
Yes Yes No
Fiscal year for reporting Chart of accounts used for reporting. Date to select data for reporting.
YY
DD-MON-YYYY Default is the system date.
No
Enter Y to include accruals for last period.
Y N
Yes No (default)
Yes Yes No
Fund for the beginning range of funds to be reported. Fund for the ending range of funds to be reported. If you have selected a range using the From Fund and To Fund parameters, you may enter any fund code that you do not wish to include in the range in this parameter. Fund code for a specific fund to be reported.
Fund Type
Yes
4-162
November 2010
Report Sample
16-OCT-92 09:22:58 FISCAL YEAR 96 COAS: FUND: A 1000 Government Chart General Fund Current Assets ACCOUNT 1201 1210 TOTAL: TITLE Due To/From Other Funds Cash Interfund Account Current Assets Liabilities ACCOUNT 2100 TOTAL: TOTAL TITLE Accounts Payable - Operations Accounts Payable Accounts Liabilities Ledger Control Accounts ACCOUNT 3010 3020 3040 3050 3060 3070 3099 TOTAL: TOTAL TITLE Revenue Control Account Expenditure Control Account Encumbrance Control Account Encumbrance Reserve Account Budgeted Revenue Control Account Budgeted Expenditure Control Acct Budgeted Change to Fund Balance Control Accounts Ledger Control Accounts
Banner University Balance Sheet AS OF 30-NOV-1995
PAGE 1 FGRBLSH
CURRENT YEAR AS OF 30-NOV-1995 87,152.70 1,249,646.00 1,336,798.70
PRIOR YEAR AS OF 30-NOV-1994 19,970.00 1,009,503.00 1,029,473.00
******** VARIANCE ********* CURRENT TO PRIOR PERCENT
67,182.70 240,143.00 307,325.70
336.418 23.788 29.853
.00 .00 .00
11,300.00 11,300.00 11,300.00
11,300.00 11,300.00 11,300.00
100.000 100.000 100.000
2,924,695.20 1,587,896.50 202,310.00 202,310.00 5,991,907.00 5,991,907.00 .00 1,336,798.70 C 1,336,798.70 C
2,706,770.00 1,688,597.00 112,250.00 112,250.00 5,482,500.00 5,482,500.00 .00 1,018,173.00 C
-217,925.20 -100,700.50 90,060.00 -90,060.00 509,407.00 -509,407.00 .00 -318,625.70 -31.294
-8.051 -5.964 80.232 -80.232 9.292 -9.292 .000 -31.294
1,018,173.00 C
-318,625.70
4-163
November 2010
Bank Cash Interfund Account Balance Exception Report (FGRBIEX)

Description
This report has two modes: summary mode and detail mode. The summary mode report balances the cash interfund account for each bank fund to the cash interfund accounts of the funds which have a claim on the bank fund. Only those accounts which are not balanced will print. If all interfund accounts are balanced, only the report control information is printed. Each chart of accounts is reported separately. In detail mode, the report prints each document which caused the exception condition. Only the chart of accounts and interfund accounts entered are reported. The detail report has four options for the cash interfund accounts: All cash interfund accounts in the chart Range of accounts Specific accounts using wildcard (%) Specific accounts without a wildcard
Parameters
Name
Required?
Description
Values
Fiscal Year As of Date
Yes No
Fiscal year for reporting Date to select data for reporting.
YY DD-MON-YYYY Default is the system date.
No
Enter a Y in this parameter if you wish to include the data in the Accrual Period for reporting. Report type (Summary or Detail mode) to be produced. Chart of account used for reporting.
Y N S D
Yes No (default) Summary (default) Detail
Report Type
No
Chart of Accounts
No
4-164
November 2010
Parameters (cont)
Name
Required?
Description
Values
Bank Interfund Account Option
No
Manner in which you wish to run the reports.
A R S W
All accounts (default) Range of accounts Specific accounts Wildcard accounts
From Account
No
This parameter is only required if you selected R (Range of Accounts) in the Bank Interfund Account Option parameter. Enter the first account that you wish to include in your range in this parameter. This parameter is only required if you selected R (Range of Accounts) in the Bank Interfund Account Option. Enter the last account that you wish to include in your range in this parameter. This parameter is only required if you selected S (Specific accounts) or W (Wildcard accounts) in the Bank Interfund Account Option parameter. This parameter allows you to enter specific bank interfund accounts or specific accounts using the wildcard (%)option.
To Account
No
Bank Interfund Account
No
4-165
November 2010
Report Sample
REPORT FGRBIEX FISCAL YEAR: 96
Banner - SEED Data Bank I/F Exception Report AS OF 25-MAR-1995 List of Out of Balance Cash Interfund Accounts
RUN DATE: 25-MAR-1995 RUN TIME: 02:07 PM PAGE: 1
COAS: A
Institute of Technology 1010 <4,815.78> <1,154,284.91> -----------------<1,159,100.69> -----------------<1,159,063.05> 1,154,247.27 -----------------<4,815.78> -----------------<1,795.00> 3,795.00 -----------------2,000.00 ------------------
Cash Interfund Account:
TOTAL PARTICIPATING FUNDS: TOTAL BANK FUNDS: Difference: Cash Interfund Account: 1210
TOTAL PARTICIPATING FUNDS: TOTAL BANK FUNDS: Difference: Cash Interfund Account: 1211
TOTAL PARTICIPATING FUNDS: TOTAL BANK FUNDS: Difference: COAS: Z Institute of Technology 1010
Cash Interfund Account:
TOTAL PARTICIPATING FUNDS: TOTAL BANK FUNDS: Difference:
20,248,500.00 -----------------20,248,500.00 ------------------
4-166
November 2010
Bank Interfund Account Control Report (FGRCASH)

Description
This report compares the cash interfund account for each bank fund to the cash accounts of each fund which have a claim on the bank fund. Each Chart of Accounts is reported separately. .
Parameters
Name
Required?
Description
Values
Yes
4-167
November 2010
Report Sample
REPORT FGRCASH
Banner University Bank Interfund Account Control AS OF 18-DEC-1996
INTERFUND ACCOUNT: 1000 COAS FUND A G G G G G G G G G G G G G G G G G G G G 102000 101000 102000 201000 201010 201020 201030 201040 201050 201060 201070 301000 401000 501000 601000 701000 801000 802000 803000 804000 805000 DESCRIPTION Current Operating Funds General Fund Unrestricted Funds Special Revenue Fund Unrestricted Fund Motor Vehicle Licenses Fuel and Tax Parking Lot Revenue Day Care Facility Income State Grants Federal Grants Capital Projects Fund Capital Campaign Alumni Special Assessments Fund Fund Raising Events Grounds Maintenance Landscape Grounds Maintenance Athletic Buildings Research Proposals Department Chair Funds Pension Trust Funds Interdepartmental Expenses TOTAL PARTICIPATING FUNDS G 101010 Bank Fund TOTAL BANK FUNDS TOTAL ENDING BALANCE <70,802.35> 1,204,050.00 <1,437.99> 2,200.00 270,000.00 130,000.00 145,000.00 155,000.00 85,000.00 22,500.00 2,500.00 140,500.00 25,110.00 205,000.00 111,640.00 1,000.00 <35,820.00> 100,000.00 <425.00> <212.50> <1,037.50> ------------------2,489,764.66 <2,562,005.00> ------------------<2,562,005.00> ------------------<72,240.34>
OUT OF BALANCE
4-168
November 2010
Comprehensive Annual Financial Reports - Overview

The Comprehensive Annual Financial Report (CAFR) is a government's official annual report. It is primarily intended to meet the information needs of governing boards and other parties external to a government. The Comprehensive Annual Financial Report covers all funds and account groups of the government and all financial transactions during the year. The Comprehensive Annual Financial Report contains basic financial statements for each of the government's funds and account groups and five Combined Statements. Fund types are classified into three broad categories: Governmental, Proprietary, and Fiduciary fund types. A fourth category is called an Account Group which includes General Fixed Assets and General Long Term Debt. Fixed Assets not used in proprietary fund operations or accounted for in trust funds are considered General Fixed Assets. Long term debt (other than special assessment bonds) intended to be financed from governmental funds is considered General Long Term Debt. The four categories are represented by the following Fund Type Group Codes:
Code
Description
01 02 03 04
Governmental Fund Types Proprietary Fund Types Fiduciary Fund Types Account Groups
Banner Finance contains nine Comprehensive Annual Financial Reports. CAFR reports include: Combined Balance Sheet - All Fund Types and Account Groups Report (FGRCOBS) Combined Statement of Revenues, Expenditures, and Changes in Fund Balances Report - All Governmental Fund Types and Expendable Trust Funds (FGRCREF) Combined Statement of Revenue, Expenditures, and Changes in Fund Balances Report - Budget and Actual- General, Special Revenue, and Debt Service Funds (FGRCSBA)
4-169
November 2010
Combined Statement of Revenue, Expenditures, and Changes in Retained Earnings/Fund Balances Report All Proprietary Fund Types and Similar Trust Funds (FGRCSRE) Combining Financial Statements of Individual Funds: Combining Balance Sheets Report (FGRCBSR) Comparative Balance Sheets (FGRCGBS) Combining Statement of Revenue, Expenditures, and Changes in Fund Balances Report (FGRCSSR) Comparative Statement of Revenues, Expenditures, and Changes in Fund Balances Report (FGRCSCF) Comparative Statements of Revenues, Expenditures, and Changes in Fund Balances Report - Budget and Actual (FGRCGBA) Refer to the Reports and Processes chapter in the Banner Finance TRM Supplement for a discussion of required fields in the CAFR reports.
4-170
November 2010
Combined Balance Sheet - All Fund Types and Account Groups (FGRCOBS)
Description
This report is sorted by fund type group which shows assets, liabilities, and fund equity accounts. Fund types are classified into the following broad categories:
Governmental:
Proprietary:
Fiduciary:
Account Groups:
General Funds Special Revenue Funds Capital Projects Funds Debt Service Funds Special Assessment Funds
Enterprise Funds Internal Service Funds
Trust Funds Agency Funds
Accountability for and control of the government's General Fixed Assets and General Long-Term Debt. General Long-Term Debt and General Fixed Assets are Account Groups, not fund types. They are associated with the 04 Fund Type Group Code for this report.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY) Include Accruals Period
Yes Yes Yes
Fiscal year for reporting. Chart of accounts code. Date to select data for reporting.
YY
Yes
Y N
Yes No (default)
Fund Type Group
Yes
Enter 01, 02, 03, or 04 for a specific group of fund types. Leave blank to select all fund type groups.
01, 02, 03, or 04
4-171
November 2010
REPORT FGRCOBS COAS: G FISCAL YEAR: 96
Banner University Combined Balance Sheet--All Fund Types and Account Groups June 30, 1996 (With comparative totals for June 30, 1995) (amounts expressed in thousands)
RUN DATE: 12/11/1996 TIME: 23:02:19 PAGE: 1
Governmental Fund Types ________________________________________________________________________ General Fund _____________ ASSETS: Operating Cash Payroll Cash Accounts Receivable Due From Other Funds Investments - Short Term Investments - Long Term Central Stores Inventory Emergency Supplies Inventory Equipment Inventory Buildings and Improvements Equipment - Furniture Equipment - Computers Equipment - Vehicles TOTAL ASSETS AND OTHER DEBITS: LIABILITIES: Accounts Payable Vouchers Payable TOTAL LIABILITIES: 1,539 1,000 7 25 1 20 4 Special Revenue Funds _____________ ---1 15 -------_____________ 16 1 -_____________ 1 Capital Projects Fund _____________ --4 3 11 100 -------_____________ 118 5 -_____________ 5 Debt Service Fund _____________ --4 -15 -------_____________ 19 --_____________ Special Assessments Fund _____________ ----------_____________
_____________ 2,597 41 _____________ 41
--_____________
*********************** CONTINUED ON NEXT PAGE ***********************
4-172
November 2010
******************** CONTINUED FROM PREVIOUS PAGE ******************** EQUITY AND OTHER CREDITS: Revenue Control Expenditure Control Encumbrance Control Budget Reservation Control Budgeted Revenue Control Budgeted Expenditure Control Budgeted Change to Fund Balance Fund Balance
2,240 -219 -139 139 -8,000 7,782 218 152 _____________
1,620 -6 -100 -100 17 _____________ 1,632 _____________ 1,632 =============
270 -8 -----119 _____________ 381 _____________ 386 =============
50 -6 -61 61 ---19 _____________ 64 _____________ 64 =============
410 -7 -21 21 ---_____________ 403 _____________ 403 =============
TOTAL EQUITY AND OTHER CREDITS: TOTAL LIABILITIES, EQUITY AND OTHER CREDITS:
2,173 _____________ 2,214 =============
4-173
November 2010
REPORT FGRCOBS COAS: G FISCAL YEAR: 96
Banner University Combined Balance Sheet--All Fund Types and Account Groups June 30, 1996 (With comparative totals for June 30, 1995) (amounts expressed in thousands) Governmental Fund Types ___________________________ Current Year 1996 _____________ Prior Year 1995 _____________
ASSETS: Operating Cash Payroll Cash Accounts Receivable Due From Other Funds Investments - Short Term Investments - Long Term Emergency Supplies Inventory TOTAL ASSETS AND OTHER DEBITS: LIABILITIES: Accounts Payable TOTAL LIABILITIES: EQUITY AND OTHER CREDITS: Revenue Control Expenditure Control Encumbrance Control Budget Reservation Control Budgeted Revenue Control Budgeted Expenditure Control Budgeted Change to Fund Balance Fund Balance TOTAL EQUITY AND OTHER CREDITS: TOTAL LIABILITIES, EQUITY AND OTHER CREDITS:
1,539 1,000 16 29 12 150 4 _____________ 2,750 47 _____________ 47 4,590 -245 -221 221 -8,000 7,882 118 307 _____________ 4,652 _____________ 4,699 =============
_____________
_____________
_____________ _____________ =============
4-174
November 2010
Combined Statement of Revenues, Expenditures, and Changes in Fund Balances (FGRCREF)

Description
This report displays values for each governmental fund type and expendable trust fund. It also displays the summarized totals for the current and prior fiscal years. Fund type values and fiscal year totals are sorted by various revenues and expenditure accounts. Grand totals displayed on the last page of this report are changes in fund balance.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY) Include Accruals Period
Yes Yes Yes
YY
Yes
Y N
Yes No (default)
4-175
November 2010
REPORT FGRCREF COAS: G FISCAL YEAR: 96
Banner University Combined Statement of Revenues, Expenditures and Changes in Fund Balances All Governmental Fund Types and Expendable Trust Fund For the fiscal year ended June 30, 1996 (With comparative totals for the fiscal year ended June 29, 1995 ) (amounts expressed in thousands)
Governmental Fund Types _________________________________________________________________________ General Fund _____________ REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Parking Fines Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income TOTAL REVENUES: EXPENDITURES: General Administration Safety Awareness Street Repairs Sanitation Health Services Daycare Services Culture and Recreation Education Capital Outlay TOTAL EXPENDITURES: Special Revenue Funds _____________ Capital Projects Fund _____________ Debt Service Fund _____________ Special Assessments Fund _____________
Fiduciary Fund Types _____________ Expendable Trust Funds _____________
320 250 500 25
25 _____________ 1,120
70 125 100 170 225 70 25 25 _____________ 810
10 -100 ----25 _____________ 135
-25 ------_____________ 25
--150 25 5 --25 _____________ 205
20 20 20 20 20 ---_____________ 100
108 2 ---1 _____________ 109 --1 _____________ 3 -3 ----1 -_____________ 4
---2 -----_____________ 3
----2 1 1 --_____________ 4
10 10 10 10 11 ---_____________ 51
4-176
November 2010
Banner University Combined Statement of Revenues, Expenditures and Changes in Fund Balances All Governmental Fund Types and Expendable Trust Fund For the fiscal year ended June 30, 1996 (With comparative totals for the fiscal year ended June 29, 1995 ) (amounts expressed in thousands)
RUN DATE: 12/17/1996 TIME: 16:39:18 PAGE 2
EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, January 1 Fund Balances, June 30
1,011 152 _____________ 1,011
807 17 _____________ 807
131 119 _____________ 131
22 19 _____________ 22
201 -_____________ 201
49 -_____________ 49
4-177
November 2010
Banner University Combined Statement of Revenues, Expenditures and Changes in Fund Balances All Governmental Fund Types and Expendable Trust Fund For the fiscal year ended June 30, 1996 (With comparative totals for the fiscal year ended June 29, 1995) (amounts expressed in thousands) Current Year 1996 _____________ Prior Year 1995 _____________
REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Parking Fines Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income TOTAL REVENUES: EXPENDITURES: General Administration Safety Awareness Street Repairs Sanitation Health Services Daycare Services Culture and Recreation Education Capital Outlay TOTAL EXPENDITURES: EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, January 1 Fund Balances, June 30
400 400 850 220 230 70 25 100 _____________ 2,295 108 2 3 2 2 1 1 2 1 _____________ 122 2,173 307 _____________ 2,173
_____________
_____________
_____________
4-178
November 2010
Combined Statement of Revenues, Expenditures, and Changes in Fund Balance Budget and Actual (FGRCSBA)
Description
This report creates a statement showing revenues, expenditures, and changes in fund balances for General Funds, Special Revenue Funds, and Debt Service Funds. These three funds are from Governmental Fund Type category (category 01). This report summarizes the budget, actual, and variance amounts. This report includes the investment management fund balance total and residual equity total, if applicable.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY) Include Accrual Period
Yes Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Date to select budget data for reporting.
YY
Yes
Y N
Yes No (default)
4-179
November 2010
REPORT FGRCSBA COAS: G FISCAL YEAR: 96
Banner University Combined Statement of Revenues, Expenditures and Changes in Fund Balance Budget and Actual - General, Special Revenue and Debt Service Funds For the fiscal year ended June 30, 1996 (amounts expressed in thousands) General Fund ___________________________________________ VARIANCE FAVORABLE (UNFAVORABLE) ____________ 680 250 1,000 225 250 125 125 225 _____________ 2,880 2,864 867 53 53 53 53 53 -1 -1 _____________ 3,990 -1,110 _____________ -1,110 =============
Special Revenue Funds ___________________________________________ VARIANCE FAVORABLE (UNFAVORABLE) ____________ -70 -125 -100 -170 -225 -70 -25 -25 _____________ -810 35 35 35 13 13 13 13 -1 _____________ 155 -965 _____________ -965 =============
BUDGET ____________ REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Parking Fines Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income TOTAL REVENUES: EXPENDITURES: General Government Safety Awareness Street Repairs Sanitation Health Services Daycare Services Culture and Recreation Education Capital Outlay TOTAL EXPENDITURES: EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, July 1 Fund Balances, June 30 1,000 500 1,500 250 250 125 125 250 _____________ 4,000 2,972 867 53 53 53 53 53 _____________ 4,101 -101 152 _____________ 51 =============
ACTUAL ____________ 320 250 500 25
BUDGET ____________
ACTUAL ____________ 70 125 100 170 225 70 25 25 _____________ 810
25 _____________ 1,120 108
_____________
1 1 _____________ 111 1,009 152 _____________ 1,161 =============
38 38 38 13 13 13 13 _____________ 163 -163 17 _____________ -145 =============
2 2 2
1 _____________ 7 803 17 _____________ 820 =============
4-180
November 2010
REPORT FGRCSBA COAS: G FISCAL YEAR: 96
Banner University Combined Statement of Revenues, Expenditures and Changes in Fund Balance Budget and Actual - General, Special Revenue and Debt Service Funds For the fiscal year ended June 30, 1996 (amounts expressed in thousands) Debt Service Fund ______________________________________ VARIANCE FAVORABLE BUDGET ACTUAL (UNFAVORABLE) ----------------------------------
REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Parking Fines Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income _____________ TOTAL REVENUES: EXPENDITURES: General Government Safety Awareness Street Repairs Sanitation Health Services Daycare Services Culture and Recreation Education Capital Outlay _____________ TOTAL EXPENDITURES: EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, January 1 Fund Balances, June 30 19 _____________ 19 =============
25 25 25 25 25 25 25 _____________ 175
-25 -25 -25 -25 -25 -25 -25 _____________ -175
2 2 1 1 _____________ 6 169 19 _____________ 189 =============
-2 -2 -1 -1 _____________ -6 -169 _____________ -169 =============
4-181
November 2010
Combined Statement of Revenues, Expenses, and Changes in Retained Earnings/Fund Balances (FGRCSRE)
Description
The purpose of this report is to produce a combined statement of revenues, expenses, and changes in retained earnings/fund balances categorized by Proprietary Fund Type (Fund Type group 02), and Fiduciary Fund Type (Fund Type group 03).
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY) Include Accrual
Yes Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Date to select data for reporting.
YY
Yes
Enter Y to include accrual for last period.
Y N
Yes No (default) Level 1 accounts As exists
Account Level
Yes
Enter L for Level 1 accounts; or enter E for as exists. L E
4-182
November 2010
Report Sample
REPORT FGRCSRE COAS: G FISCAL YEAR: 96
Banner University Combined Statement of Revenues, Expenses and Changes in Retained Earnings/Fund Balances All Proprietary Fund Types and Similar Trust Funds For the fiscal year ended June 30, 1996 (With comparative totals for the fiscal year ended June 29, 1995 ) (amounts expressed in thousands) Proprietary Fund Types ____________________________ Enterprise Fund _____________ Internal Service Fund _____________ --_____________ Fiduciary Fund Types ____________________________ NonExpendable Trust _____________ --_____________ Current Year 1991 _____________ 50 50 _____________ 100 Prior Year 1990
_____________
OPERATING REVENUES: Property Tax Revenues Investment Income TOTAL OPERATING REVENUES: OPERATING EXPENSES: Health Welfare Culture and Recreation Education Capital Outlay TOTAL OPERATING EXPENSES: Operating income
50 50 _____________ 100
_____________
3 1 _____________ 5 96
--2 -1 _____________ 3 -3 32 _____________ 30 =============
----_____________
3 2 1 1 _____________ 7 93 342 _____________ 435 =============
_____________
--_____________ =============
Retained earnings/fund balances, January 1 309 _____________ Retained earnings/ 405 fund balances, June 30 =============
_____________ =============
4-183
November 2010
Combining Balance Sheets Report (FGRCBSR)

Description
This report produces a balance sheet displaying assets, liabilities, and fund balances for a parameter specified fund reflecting the current and prior years.
Parameters
Name
Required?
Description
Values
Yes Yes Yes
YY
Yes
Y N
Yes No (default)
Fund Type Fund Level Account Level
Yes Yes Yes
Fund type code for reporting. Fund level used for reporting. 1, 2, 3, 4, or 5 Level 1 accounts As exists
Enter L for level 1 accounts, or enter E for as exists. L E
4-184
November 2010
Report Sample
REPORT FGRCBSR COAS: G FISCAL YEAR: 96
Banner University General Fund Combining Balance Sheets June 30, 1996 (With comparative totals for June 29, 1995 ) (amounts expressed in thousands) ________________________________________________________________________________ General Fund _____________ Current Year 1996 _____________ -1,358 1,539 1,000 7 25 1 20 4 _____________ 1,239 Prior Year 1995 _____________
ASSETS: Cash Operating Cash Payroll Cash Accounts Receivable Due From Other Funds Investments - Short Term Investments - Long Term Emergency Supplies Inventory TOTAL ASSETS: LIABILITIES: Liabilities Accounts Payable Due To Other Funds TOTAL LIABILITIES: FUND BALANCES: Fund Balance TOTAL FUND BALANCES:
-1,358 1,539 1,000 7 25 1 20 4 _____________ 1,239
_____________
26 41 9 _____________ 76
26 41 9 _____________ 76
_____________
1,162 _____________ 1,162 _____________ 1,239 =============
1,162 _____________ 1,162 _____________ 1,239 =============
_____________
_____________ =============
TOTAL LIABILITIES AND FUND BALANCES
4-185
November 2010
Comparative Balance Sheets Report (FGRCGBS)

Description
The purpose of this report is to produce a balance sheet for comparing current and prior years for assets, liabilities, and fund balances. You may select a fund type and an account level for reporting purposes. The report will produce a balance sheet for the fund type entered at the parameter prompt. The account level is the level at which you wish to view the breakdown of the accounts.
Parameters
Name
Required?
Description
Values
Yes No Yes
YY
Yes
Y N
Yes No (default)
Fund Type Account Level
Yes Yes
Fund type code for reporting. Enter L for level 1 accounts, or enter E for as exists. L E Level 1 accounts As exists
4-186
November 2010
Report Sample
REPORT FGRCGBS COAS: G FISCAL YEAR: 96
Banner University General Fund Comparative Balance Sheets June 30, 1996 and 1995 (amounts expressed in thousands) 1996 _____________ ASSETS: Cash Operating Cash Payroll Cash Accounts Receivable Due From Other Funds Investments - Short Term Investments - Long Term Emergency Supplies Inventory TOTAL ASSETS: LIABILITIES: Liabilities Accounts Payable Due To Other Funds TOTAL LIABILITIES: FUND BALANCES: Fund Balance TOTAL FUND BALANCES: -1,358 1,539 1,000 7 25 1 20 4 _____________ 1,239
1995 _____________
_____________
26 41 9 _____________ 76
_____________
1,162 _____________ 1,162 _____________ 1,239
_____________ _____________
4-187
November 2010
Combining Statement of Revenues, Expenditures and Changes in Fund Balance (FGRCSSR)

Description
The purpose of this report is to produce a statement of revenues, expenditures, and changes in fund balances for a user-specified fund reflecting the current and prior years. This report includes the investment management fund balance total and residual equity total, if applicable.
Parameters
Name
Required?
Description
Values
No Yes Yes
YY
Yes
Y N
Yes No (default)
Fund Type Fund Level Account Level
Yes Yes Yes
Fund type code for reporting. Fund level for reporting. 1, 2, 3, 4, or 5 Level 1 accounts As exists Level 1 programs (default) As exists)
Enter L for level 1 accounts, or enter E for as exists. L E
Program Level
Yes
Enter L for level 1 programs, or enter E for as exists.
L E
4-188
November 2010
Report Sample
REPORT FGRCSSR COAS: G FISCAL YEAR: 96
Banner University General Fund Combining Statement of Revenues, Expenditures and Changes in Fund Balance For the fiscal year ended June 30, 1996 (With comparative totals for the fiscal year ended June 29, 1995 ) (amounts expressed in thousands) ________________________________________________________________________________ Current Prior General Year Year Fund 1996 1995 _____________ _____________ 320 250 500 25 _____________
REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Fines and Forfeitures Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income TOTAL REVENUES: EXPENDITURES: General Government Public Safety Highways and Streets Education TOTAL EXPENDITURES: EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, January 1 Fund Balances, June 30
320 250 500 25
25 _____________ 1,120
25 _____________ 1,120
_____________
108 1 _____________ 109
108 1 _____________ 109
_____________
1,011 152 _____________ 1,162 =============
1,011 152 _____________ 1,162 =============
_____________ =============
4-189
November 2010
Comparative Statements of Revenues, Expenditures and Changes in Fund Balances(FGRCSCF)

Description
This report produces a statement of revenues, expenditures, and changes in fund balance for the current and prior years. Enter values for the fund type, account level, and program level parameters to narrow the scope of the report output. This report includes the investment management fund balance total and residual equity total, if applicable.
Parameters
Name
Required?
Description
Values
Yes Yes No
YY
No
Y N
Yes No (default)
Fund Type Code Account Level
Yes Yes
Fund type code for reporting. Enter L for level 1 accounts, or enter E for as exists. L E Level 1 accounts As exists (default) Level 1 programs (default) As exists
Program Level
Yes
Enter L for level 1 programs, or enter E for as exists.
L E
4-190
November 2010
Report Sample
REPORT FGRCSCF COAS: G FISCAL YEAR: 96
Banner University Special Revenue Funds Comparative Statements of Revenues, Expenditures and Changes in Fund Balances For the fiscal years ended June 30, 1996 and 1995 (amounts expressed in thousands) ________________________________________________________________________ 1996 _____________ REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Fines and Forfeitures Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income TOTAL REVENUES: EXPENDITURES: General Government Public Safety Capital Outlay TOTAL EXPENDITURES: EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, January 1 Fund Balances, June 30 70 125 100 170 225 70 25 25 _____________ 810
1995 _____________
_____________
2 1 _____________ 3
_____________
807 17 _____________ 825 =============
_____________ =============
4-191
November 2010
Comparative Statements of Revenues, Expenditures, and Changes in Fund Balances - Budget and Actual (FGRCGBA)
Description
This report produces a statement of revenues, expenditures, and changes in fund balance reflecting the budget, actual, and variance values for the current and prior years. The fund type reported on is user specified. This report includes investment management fund balance total and residual equity total, if applicable.
Parameters
Name
Required?
Description
Values
Yes Yes Yes
YY
Yes
Y N
Yes No (default)
Fund Type Code Account Level
Yes Yes
Fund type code for reporting. Enter L for Level 1 Accounts, or enter E for as exists. L E Level 1 accounts As exists Level 1 organizations As exists
Organization Level
Yes
Enter L for level 1 organizations, or enter E for as exists.
L E
4-192
November 2010
Report Sample
REPORT FGRCGBA COAS: G FISCAL YEAR: 96
Banner University Special Revenue Funds Comparative Statements of Revenues, Expenditures and Changes in Fund Balances--Budget and Actual For the fiscal years ended June 30, 1996 and 1995 (amounts expressed in thousands) 1996 __________________________________________ VARIANCE FAVORABLE BUDGET ACTUAL (UNFAVORABLE) ____________ ____________ ____________
1995 __________________________________________ VARIANCE FAVORABLE BUDGET ACTUAL (UNFAVORABLE) ____________ ____________ ____________
REVENUES: General Tax Revenues Sales Tax Revenues Property Tax Revenues Fines and Forfeitures Licenses and Fees Miscellaneous Revenues Grant Revenues Investment Income _____________ TOTAL REVENUES: EXPENDITURES: General Administration Law Enforcement Courts TOTAL EXPENDITURES: EXCESS (DEFICIENCY) OF REVENUES OVER (UNDER) EXPENDITURES Fund Balances, January 1 Fund Balances, June 30
70 125 100 170 225 70 25 25 _____________ 810
-70 -125 -100 -170 -225 -70 -25 -25 _____________ -810
_____________
_____________
_____________
3 38 13 _____________ 50 _____________ 3
-3 38 13 _____________ 47
_____________
_____________
_____________
-50 17 _____________ -33
807 17 _____________ 825
-857
_____________ -857
_____________
_____________
_____________
4-193
November 2010
Statement of Changes in Fund Balance Report (FGRCHFB)

Description
This report is sorted by fund. Information is displayed for each account by current year, prior year, and a comparison of current to prior year in dollars as well as percentage. Current year records with Uncommitted Commit Type are retrieved for this report.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY)
Yes Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Date to select data for reporting. This date should fall within the specified start and end dates of the chart and fiscal year; if it doesnt, the ending date of the fiscal period will be used for selection. Enter Y to include accruals for last period.
YY
DD-MON-YYYY
Include Accrual
Yes
Y N
Yes No (default)
Specific Fund
No
Specific fund for reporting.

Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
Specific Ftyp (Fund Type)
No
Level two fund type for reporting.

Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
4-194
November 2010
Parameters (cont) Name
Required?
Description
Values
Fund Level
No
Enter a 1 to indicate that you want all funds in the 1, 2, or E ledger to roll up to their Level 1 Fund Code and to be reported that way. Enter a 2 to indicate that you want all level 3, 4 and 5 funds to be rolled up to their Level 2 Fund Code and to be reported that way. Enter an E to report all funds as they exist in the ledger. Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
Ftyp Level (Fund Type Level)
No
Enter a 1 to indicate that you want all funds in the ledgers to roll up to their Level 1 Fund Type and to be reported that way. Enter a 2 to indicate that you want all funds with Level 2 Fund Type to be reported. Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
1 or 2
Account Level
Yes
Enter an L to roll all accounts in the ledger up to their Level 1 Account Code; the report will be displayed according to your entry. Enter an E to report all accounts as they exist in the ledger.
L E
Level 1 account code As exists
4-195
November 2010
Report Sample
05/22/90 16:07:40 FISCAL YEAR 97
Systems and Computer Technology Statement of Changes in Fund Balance AS OF 31-OCT-1997
PAGE 1 FGRCHFB
102000
Current Operating Funds CURRENT YEAR 31-OCT-1997 --------PRIOR YEAR 31-OCT-1996 --------******* COMPARISON ******** CURRENT TO PRIOR PERCENT ----------------------
EXPENDITURES AND OTHER DEDUCTIONS Full Time Admin Salaries Part Time Administrative Salaries Supplies Accounts Office Supply Accounts Legal Services Central Duplication Expense IDS - Services IDS - Supplies Capital Purchases - Vehicles Utilities Expense - Electric FUND BALANCE AT END OF YEAR
7,486.12 82,846.00 .00 .00 .00 .00 .00 .00 .00 .00 .00
.00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00
7,486.12 82,846.00 .00 .00 .00 .00 .00 .00 .00 .00 .00
.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000
4-196
November 2010
Statement of Changes in Net Assets Report (FGRCHNA)

Description
The Statement of Changes in Net Assets Report is one of the reports required by FASB (Financial Accounting Standards Board), and it is designed in adherence to the board's recommendations for financial accounting and reporting practices. This report, in conjunction with the Statement of Unrestricted Revenues, Expenses, and Other Changes in Unrestricted Net Assets Report (FGRCUNA), fulfills the Financial Accounting Standards Boards requirements for a Statement of Activities. The primary purpose of this report is to provide relevant information about the effects of transactions that change the amount and nature of net assets.
Parameters
Name
Required?
Description
Values
Consolidated Reports (Y/N)
No
Enter a Y to select the consolidated reports option. You may consolidate at the chart or fund type level. To consolidate at the fund level, enter a value for the Chart of Accounts parameter and leave the Specific Fund parameter blank. To consolidate at the fund type level, you must enter values for both the Chart of Accounts parameter and the Specific Fund Type parameter. Fiscal year for reporting. Chart of accounts used for reporting. Date to select data for reporting. The ending date of the fiscal period that the As of Date occurs in will actually be used for selection. If null, the As of Date defaults to the system date. This date should fall within the specified start and end dates of the chart and fiscal year. Enter Y if you wish to include accruals.
Y = Yes N = No
Fiscal Year (YY) Chart of Accounts As of Date (DD-MON-YYYY)
Yes Yes No
YY
DD-MON-YYYY Default = system date
Include Accrual (Y/N)
No
Y N
Yes No (default)
4-197
November 2010
Required?
Description
Values
Specific Fund
No
Specific fund for reporting.

Note: You may enter a value for only one of the following parameters: Specific Fund, Specific Fund Type, Fund Level, or Fund Type Level.
Specific Fund Type
No
Specific fund type for reporting. Note: You may value only one of the following parameters : Specific Fund, Specific Fund Type, Fund Level, or Fund Type Level. 1- Indicates that all funds in the ledger will roll up to their level 1 fund code and be reported accordingly 2- Indicates that all level 3, 4, 5 funds will be rolled up to their level 2 fund code. E -Indicates that all funds are reported as they exist in the ledger 1, 2, 3, 4, 5, or E
Fund Level (1, 2, 3, 4, 5, E)
No
Fund Type Level (1, 2)
No
1- Indicates that all funds in the ledgers will roll up to their level 1 fund type and will be reported accordingly 2- Indicates that all funds with a level 2 fund type will be reported
1 or 2
Account Level (L, E)
No
L- Indicates that all accounts in the ledger will roll up to the Level 1 account code and will be reported accordingly E- Reports all accounts as they exist in the ledger
L E
Level 1 account code As exists
4-198
November 2010
Report Sample
07/05/1996 12:23:14 FISCAL YEAR 96
Banner - SEED Data Consolidated Statement of Changes in Net Assets AS OF 30-JUN-1996
PAGE 2 FGRCHNA
Net Assets at end of Year and Fund Additions, Deductions and Transfers
Temporarily Restricted ----------------- --------------------------------- ----------------14,548,564.35 4,400.00
Unrestricted
Permanently Total Restricted ----------------- --------------------------------- ----------------705.00 14,553,669.35
4-199
November 2010
Close Operating Accounts Report (FGRCLOP)

Description
This report is a hard copy output of the closing of the operating ledger for the prior fiscal year. Control Accounts in the General Ledger are closed out to Fund Balance in the prior fiscal year. This is the last of four tasks involved in closing a fiscal year. The transactions generated from this process will write to the FGBTRNI table. You will need to execute the Transaction Interface Process (FGRTRNI) and the Transaction Error Report (FGRTRNR). Once all transactions have cleared the edits and posted, you must manually close the accrual period on the Fiscal Year Maintenance Form (FTMFSYR). This process interrogates the Multiple Fund Balance Indicator on the System Control Maintenance Table (FOASYSC). If the indicator is set to N (No), the process closes control account information and fund addition/ deduction balances into the fund balance account defined on FTMCOAS. If the indicator is set to Y (Yes), the process closes year-to-date control information and fund addition/ deduction balances to the fund balance account(s) defined on FTMFBAL. Budget and encumbrance control activity close to the fund balance account defined on FTMCOAS.
4-200
November 2010
04/02/1996 09:20:47 FISCAL YEAR 96 Chart: G Fund: 101000
Banner University Close Operating Accounts Report As of 30-JUN-1996
PAGE 1 FGRCLOP
------------------------PRIOR-YEAR BALANCES----------------------- ---------------------- CLOSING ENTRY ----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL Fund: 301000 ------------------------PRIOR-YEAR BALANCES----------------------- ---------------------- CLOSING ENTRY ----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL Fund: 401000 ------------------------PRIOR-YEAR BALANCES----------------------- ---------------------- CLOSING ENTRY ----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL 25.00 .00 25.00 .00 25.00 25.00 25.00 .00 25.00 .00 4010 25.00 4010 25.00 Fund Balance Fund Balance 1,700.00 .00 1,700.00 .00 1,700.00 1,700.00 1,700.00 .00 1,700.00 .00 4010 1,700.00 4010 1,700.00 Fund Balance Fund Balance 100.00 .00 100.00 .00 100.00 100.00 100.00 .00 100.00 .00 4010 100.00 4010 100.00 Fund Balance Fund Balance
4-201
November 2010
Banner University Close Operating Accounts Report As of 30-JUN-1996
PAGE 2 FGRCLOP
------------------------PRIOR-YEAR BALANCES----------------------- ---------------------- CLOSING ENTRY ----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL CHART TOTAL GRAND TOTALS 75.00 .00 75.00 1,900.00 1,900.00 .00 75.00 75.00 1,900.00 1,900.00 75.00 .00 75.00 1,900.00 1,900.00 .00 4010 75.00 4010 75.00 1,900.00 1,900.00 Fund Balance Fund Balance
4-202
November 2010
GL/Subsidiary Ledger Control Report (FGRCTRL)

Description
This report compares the balances in the open invoice, operating account, and open encumbrance ledgers to the appropriate control account balances in the general ledger. The Option Code parameter determines the report output as follows: Specify Option Code Parameter = 1 reports on all accounts within a chart of accounts Specify Option Code Parameter = 2 reports on a specific fund within a chart of accounts if entered; if left null, reports on all funds within a chart of accounts Specify Option Code Parameter = 3 reports on funds that are out of balance within a chart of accounts Enter a Y in the Re-create the Collector Tables parameter when you run this report the first time or when information regarding the control accounts or account types have changed. Otherwise, enter an N when you run this report, and it will use the same information regarding the control accounts and account types from the previous execution. (The default value is Y.) Currency Conversion For a given invoice, if foreign currency is used, FGRCTRL separates out the various A/P accounts from the currency conversion table for reconciling the invoice balances. In the following report sample, 3 was specified for the Option Code parameter.
4-203
November 2010
Parameters
Name
Required?
Description
Values
Fiscal Year Option Code
Yes Yes
Fiscal year for reporting. Option code for reporting.
YY 1 2 Reports on all accounts within a chart of accounts Reports on a specific fund within a chart of accounts if entered; if left null, reports on all funds within a chart of accounts Reports on funds that are out of balance within a chart of accounts
3 Chart of Accounts Fund Code Re-create the Collector Tables Yes No Yes Chart of accounts for reporting. Fund type code for reporting. Enter a Fund Code for option 2 or leave null to select all funds. Enter Y to recreate the collector tables, or enter N to override recreating the collector tables. Y N
Yes No (default)
4-204
November 2010
REPORT FGRCTRL COAS: A FISCAL: 96 ACCT. 2100 3070 3010 3020 3040 3050 ACCT. TITLE Accounts Payable - Operations Budgeted Expenditure Control Acct Revenue Control Account Expenditure Control Account Encumbrance Control Account Encumbrance Reserve Account
Banner University GL / Subsidiary Ledger Control OPERATING ACCT LEDGER OPEN ENCUMBRANCES OPEN INVOICES
RUN DATE: 10/17/1996 TIME: 10:28 AM PAGE: 1 BALANCE MESSAGE OUT OF BALANCE
GENERAL LEDGER 6,901.20 <100.00> 884.00 13,280.00 6,464.46 <6,464.46>
<1,100.80> <100.00> 884.00 <8,910.00> 6,464.46 6,464.46
OUT OF BALANCE
4-205
November 2010
REPORT FGRCTRL COAS: A FISCAL: 96 FUND CODE: 1000 ACCT. 2100 3070 3020 3040 3050 Current Unrestricted
Banner University GL / Subsidiary Ledger Control
RUN DATE: 10/17/1996 TIME: 10:28 AM PAGE: 2 OPEN ENCUMBRANCES OPEN INVOICES <100.00>
ACCT. TITLE Accounts Payable - Operations Budgeted Expenditure Control Acct Expenditure Control Account Encumbrance Control Account Encumbrance Reserve Account Ancilliary Operating - Durham
GENERAL LEDGER 8,352.00 <100.00> 3,120.00 6,445.46 <6,445.46>
OPERATING ACCT LEDGER <100.00> <1,270.00> 6,445.46
BALANCE MESSAGE OUT OF BALANCE OUT OF BALANCE
6,445.46
FUND CODE: 1500 2100 3010
Accounts Payable - Operations Revenue Control Account Federal Funds-1
<900.00> 884.00
<900.00> 884.00
FUND CODE: 2101 2100 3020 3040 3050
Accounts Payable - Operations Expenditure Control Account Encumbrance Control Account Encumbrance Reserve Account Federal Funds-2
.00 8,710.00 19.00 <19.00>
.00 <6,290.00> 19.00 OUT OF BALANCE 19.00
FUND CODE: 2102 2100 3020
Accounts Payable - Operations Expenditure Control Account NSF-Everglades Erosion - 89/90
.00 1,450.00
.00 <1,350.00> OUT OF BALANCE
FUND CODE: 2211 2100
Accounts Payable - Operations
<550.80>
<100.80>
OUT OF BALANCE
4-206
November 2010
Changes in Unrestricted Net Assets Report Statement of Revenues, Expenses, and Other Changes (FGRCUNA)
Description
The Statement of Unrestricted Revenues, Expenses, and Other Changes in Unrestricted Net Assets Report is one of the reports required by FASB (Financial Accounting Standards Board), and it is designed in adherence to the board's recommendations for financial accounting and reporting practices. This report, in conjunction with the Statement of Changes in Net Assets Report (FGRCHNA), fulfills the Financial Accounting Standards Boards requirements for a Statement of Activities. The primary purpose of this report is to provide relevant information about the effects of transactions that change the amount and nature of unrestricted net assets.
Parameters
Name
Required?
Description
Values
No
Enter a Y to select the consolidated reports option. You may consolidate at the chart or fund type level. To consolidate at the fund level, enter a value for the Chart of Accounts parameter and leave the Specific Fund parameter blank. To consolidate at the fund type level, you must enter values for both the Chart of Accounts parameter and the Specific Fund Type parameter. Fiscal year for reporting. Chart of accounts used for reporting. Date to select data for reporting. The ending date of the fiscal period that the As of Date occurs in will actually be used for selection. If null, the As of Date defaults to the system date. This date should fall within the specified start and end dates of the chart and fiscal year. Enter Y to include accruals.
Y = Yes N = No
Yes Yes No
YY
No
Y N
Yes No (default)
4-207
November 2010
Parameters (cont)
Name
Required?
Description
Values
Specific Fund
No
Specific fund for reporting. Either Specific Fund or Specific Fund Type is entered. The report is generated only for unrestricted funds. Specific fund type for reporting. Either Specific Fund or Specific Fund Type is entered. This parameter tells the system to generate the report for unrestricted funds within the specified fund type.
Specific Fund Type
No
4-208
November 2010
07/05/1996 12:22:20 FISCAL YEAR 96
Banner - SEED Data Consolidated Statement of Unrestricted Revenues, Expenses, and Other Changes in Unrestricted Net Assets AS OF 30-JUN-1996
PAGE 1 FGRCUNA
Unrestricted Revenues and Gains: Trust Investment Income Indirect Cost Federal Grants Federal Direct Income - Grants Institution Match on Grants Interest Income Extraordinary Gains Net Assets Released from Restrictions Total Unrestricted Revenues and Gains Expenses and Losses: Instruction Vocational/Technical Instruction Personal Interest & Leisure Nondeg Executive Management Financial Management & Operations Independent Operations/External Debt Service Institutional Research Auxiliary Enterprises Supplies & Services Non-Operating Account 1 Non-Operating Account 2 Extraordinary Losses Total Auxiliary Expenses Total Unrestricted Expenses and Losses Increase (Decrease) in Unrestricted Net Assets Fund Transfers: Mandatory Transfers Spendable Amount
11,250.00 26.38 602.87 76.14 1,000.00 115,250.00 500.00 -------------128,705.39 42,953.04 250.00 0.00 0.00 0.00 99,416.00 337,500.00 0.00 0.00 13,592.48 3,351.52 7,000.00 23,944.00 -------------504,063.04 ( 375,357.65) -------------300.00 ( 300.00)
4-209
November 2010
07/05/1996 12:22:20 FISCAL YEAR 96
Banner - SEED Data Consolidated Statement of Unrestricted Revenues, Expenses, and Other Changes in Unrestricted Net Assets AS OF 30-JUN-1996
PAGE 2 FGRCUNA
Fund Additions and Deductions: Funds Deductions Account Increase (Decrease) in Unrestricted Net Assets and Fund Additions, Deductions and Transfers
-50.00 ( 375,407.65) ==============
4-210
November 2010
End-of-Year Encumbrance Carry Forward Report (FGRENRL)

Description
This process rolls the open encumbrances based upon the criteria specified on the Chart of Accounts Validation Table (FTVCOAS) and on the Fund Type Maintenance Form (FTMFTYP). A hard copy report is produced indicating the encumbrances that were rolled to the new fiscal year and the encumbrances that were closed. On the Chart of Accounts Maintenance Form, specify the encumbrances that you wish to roll into the new year (requisitions, purchase orders, labor encumbrances, etc.). You will also need to specify the following: How you want the encumbrances to roll (Uncommitted or Committed) If you want the budget to roll to cover encumbrances What percentage of the budget you want to roll to cover encumbrances You can override the funds defaults at the Fund Type Level. This process first checks level 2 or level 1 external fund type values before using the defaults set at the chart level. The transaction generated from this process will write to the FGBTRNI table. You will need to execute FGRTRNI (Transaction Interface Process) and FGRTRNR (Transaction Error Report). Several documents will be generated from this process. If the client site performs this process and there are no documents to be rolled and no documents to be closed, the Ending Document Number field for the Roll Encumbrances record on the Year End Maintenance Form (FGAYRLM) will remain blank since no documents are created. The Performed Date field will be populated to inform the user that the process completed successfully, even though no documents were created. This process ignores L (labor) type records with an Encumbrance number of PR, since these records are processed by the new Roll HR Labor Encumbrances Process (FGRLENC).
4-211
November 2010
Report Sample
01/06/1996 13:58:51 FISCAL YEAR 96 Chart: A Fund: 103000 ENCUMB TITLE
Banner University End-of-Year Encumbrance Carry Forward As of 17-NOV-1996
PAGE 1 FGRENRL
Current Operating Funds AMOUNT 1,500.00 1,000.00 50.00 105.00 2,655.00 2,655.00 2,655.00 RULE TABLE E090 E090 E090 E090 COAS COAS COAS COAS BUDGET AMT RULE 1,500.00 BD01 1,000.00 BD01 50.00 BD01 105.00 BD01 2,655.00 2,655.00 2,655.00 CMT PCT U 100.000 U 100.000 U 100.000 U 100.000
E0000196 Computer Warehouse E0000196 Computer Warehouse E0000215 Laboratory Supplies E0000218 Office Supplies FUND TOTAL CHART TOTAL GRAND TOTALS
4-212
November 2010
Fund/Account Activity Report (FGRFAAC)

Description
This report is similar to the Trial Balance Report (FGRTBAL). FGRFAAC displays the beginning and ending balance for each account and the total amount of debits and credits for each account within a specified fiscal year.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date
Yes Yes No
YY
Include Accrual for Last Prd. From Fund To Fund From Account To Account
No
Enter Y to Include Accrual for last period.
Y N
Yes No (default)
No No No No
Fund for the beginning range of funds to be reported. Fund for the ending range of funds to be reported. Account for the beginning range of accounts to be reported. Account for the ending range of accounts to be reported.
4-213
November 2010
Report Sample
FGRFAAC FISCAL YEAR 96 COAS: FUND: ACCOUNT _______ 1210 2510 TOTAL: TOTAL: 2100 2107 2120 TOTAL: TOTAL: 3020 3040 3050 TOTAL: A 1000 Institute of Technology Current Unrestricted Fund
Development Fund/Account Activity Report AS OF 30-NOV-1996
NOV-1996 13:39:23 PAGE 1
ACCOUNT TITLE ______________________________________ Cash Interfund Account Rebate Receivable Current Assets Assets Accounts Payable - Operations Taxes Payable - Local Canadian Dollar AP Account Accounts Payable Accounts Liabilities Expenditure Control Account Encumbrance Control Account Encumbrance Reserve Account Control Accounts TOTAL LIABILITIES & FUND BALANCE: GRAND TOTAL:
BEGINNING BALANCE ________________ .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00 .00
DEBITS ________________ 525.60 .60 526.20 526.20 1,701.32 180.66 172.00 2,053.98 2,053.98 1,454.45 12,091.61 4,222.50 17,768.56 19,822.54 20,348.74
CREDITS ________________ 1,000.66 .45 1,001.11 1,001.11 1,496.66 240.66 201.60 1,938.92 1,938.92 1,094.60 4,222.50 12,091.61 17,408.71 19,347.63 20,348.74
ENDING BALANCE ________________ -475.06 .15 -474.91 -474.91 204.66 -60.00 -29.60 115.06 115.06 359.85 7,869.11 -7,869.11 359.85 474.91 .00
4-214
November 2010
Fund Balance Account Report (FGRFBAL)

Description
This report displays the information maintained through the Fund Balance Account Maintenance Form (FTMFBAL).
Parameters
Name
Required?
Description
Values
Yes Yes
Chart of accounts for reporting. Date to select data for reporting. Default is the current date. DD-MON-YYYY Default = current date
Report Sample
FGRFBAL
Banner University Fund Balance Account Report As of 02-NOV-1996
05-NOV-1996
15:19:03 PAGE: 1
CHART: A Banner University FUND TYPE 10 20 30 610001 610002 610003 610003 610004 610004 620001 620002 620003 620004 1150 14001 14002 14001 14001 FUND CODE ACCOUNT CODE FUND BALANCE ACCOUNT 3510 3510 3510 3510 3600 3510 3510 42001 42001 3510 3600 41001 42001 *********** EFFECTIVE 02-NOV-1993 02-NOV-1993 02-NOV-1993 01-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 02-NOV-1993 DATES NEXT CHANGE 31-DEC-2099 31-DEC-2099 31-DEC-2099 31-DEC-2099 31-DEC-2099 02-NOV-1993 31-DEC-2099 02-NOV-1993 31-DEC-2099 31-DEC-2099 31-DEC-2099 31-DEC-2099 31-DEC-2099 *********** TERMINATION
31-DEC-1996
4-215
November 2010
Inception to Date Activity Report (FGRFITD)

Description
This report displays the Inception to Date activity for account codes within fund codes. Credit balances display with a negative sign.
Parameters
Name
Required?
Description
Values
Chart of Accounts Code Starting Fund Code Ending Fund Code Ending Date
Yes Yes Yes Yes
Chart of accounts for reporting. Starting fund type code in the range for reporting. Ending fund type code in the range for reporting. Date to select data for reporting. DD-MON-YYYY Default = current date
Category Description
Yes
You can enter multiple values for this parameter. For example: 01 Expenses 02 Salaries
To enter a description, enter a value from 01 to 09, followed by a space and the category description.
Category Account Code Range
Yes
A Category Account Range parameter must exist for each Category Description. You can enter multiple ranges for this parameter. For example: 01 7100 7999 02 6100 6999
To enter a range, use the following format with a space between each element, as indicated:
Category Code space Beginning account code range space Ending account range
Print Account Codes (Y/N) [N]
Yes
Enter Y(Yes) to print account codes in the report. The Y default is N(No), suppress printing. N
Yes No (default)
4-216
November 2010
Report Sample
FGRFITD
2.1.11
Banner University Inception to Date Activity Rpt As of 22-NOV-1993
22-NOV-1993 15:00:20 Page 1
Chart: Fund: Category: Subtotal Category:
A 1000 Assets Investment in Pool Cash Interfund Account Assets Gifts Original Gift Subsequent Gift Transfers of Prior Year Gifts 6,500.00500.001,000.00 6,000.009,000.00 1,000.00 10,000.00
Subtotal Category:
Gifts Income Current Year Income Current Year Transfers Prior Year Income Transfers of Prior Year Income 100.00 75.00 2,000.0025.00-
Subtotal Category:
Income Gains Current Year Gains/Losses Current Year Gains Transfers Prior Year Gains/Losses Transfers of Prior Year Gains/Losses 150.00 25.00 1,900.00 25.00
2,000.00-
Subtotal Total
Gains 1000
2,000.000.00
4-217
November 2010
Fund Hierarchy Report (FGRFNDH)

Description
This report displays the hierarchy structure information related to fund type and fund code information by the order of fund type for the specific chart of accounts.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date (DD-MON-YYYY) Fund Type Code
Yes Yes
Chart of accounts for reporting. Date to select data for reporting. DD-MON-YYYY Default = current date
No
Fund type code for reporting.
4-218
November 2010
Report Sample
REPORT FGRFNDH CHART: A
Banner University Fund Hierarchy Report AS OF 18-DEC-1996 DESCRIPTION Current Unrestricted Funds Administration Overtime Current Unrestricted Fund Current Funds Current Operating funds Current Operating Funds - unrestric Current Operating Funds Current Operating Funds Deferred Payroll Liability Fund Current Operating Funds Current Funds - Unrestricted Mutual Fund Benefits#1 - Current Unrestricted Benefits#2 - Unrestricted Fund Current Operating Funds - Quigley Benefits #16 Benefits #17 - Current Unrestricted Benefits #19 Benefits #20 Sports #7 - Unrestricted Grant Sports #22 Sports #21 Sports #23 Operating Fund Recycling #24 Recycling #25 Recycling #26 Recycling #27 Recycling #28 DATA ENTRY STATUS CNTL FUND CMB
RUN DATE: 12/18/1996 TIME: 10:20 AM PAGE: 1 ********* DATES ********* EFF TERM NEXTCHANGE 01-OCT-1996 12-JUN-1996 31-AUG-1996 03-OCT-1996 01-OCT-1996 01-OCT-1996 01-OCT-1996 01-OCT-1996 01-OCT-1996 26-OCT-1996 01-OCT-1994 01-OCT-1994 01-NOV-1994 16-APR-1992 16-APR-1992 01-JUN-1992 14-JUN-1992 18-JUN-1992 04-JUL-1992 05-JUL-1992 06-JUL-1992 11-JUL-1992 11-JUL-1992 17-JUL-1992 18-JUL-1992 22-JUL-1992 23-JUL-1992 23-JUL-1992 23-JUL-1992 23-JUL-1992
TYP 01 TF RH 10
FUND
100000 101000 103000 104000 111000 103001 102000 1-000 MTFUND QAF1 QAF2 105000 QAF16 QAF17 QAF19 QAF20 QAF7 QAF22 QAF21 QAF23 OPT_FD QAF24 QAF25 QAF26 QAF27 QAF28
N N Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y Y Y N Y Y Y Y Y
A A A A A A A A A A A A A A A A A A A A A A A A A A
4-219
November 2010
Statement of Financial Position Report (FGRFPSN)

Description
The Statement of Financial Position Report is one of the reports required by FASB (Financial Accounting Standards Board), and it is designed in adherence to the board's recommendations for financial accounting and reporting practices. The primary purpose of this report is to provide relevant information about an organizations assets, liabilities, and net assets for a specific date supplied by the user via the As of Date parameter. The change (see last column on the report sample) from prior year to current year may be used as a worksheet for the preparation of a Statement of Cash Flows.
Parameters
Name
Required?
Description
Values
No
Enter a Y to select the consolidated reports option. You may consolidate at the chart or fund type level. To consolidate at the fund level, enter a value for the Chart of Accounts parameter and leave the Specific Fund parameter blank. To consolidate at the fund type level, you must enter values for both the Chart of Accounts parameter and the Specific Fund Type parameter. Fiscal year for reporting. Chart of accounts used for reporting. Date to select data for reporting. The ending date of the fiscal period that the As of Date occurs in will actually be used for selection. If null, the As of Date defaults to the system date. This date should fall within the specified start and end dates of the chart and fiscal year. Enter Y to include accrual options.
Y N
Yes No
Yes Yes No
YY
DD-MON-YYYY
No
Y N
Yes No (default)
4-220
November 2010
Parameters (cont)
Name
Required?
Description
Values
Specific Fund
No
Fund code for reporting, If null, then all fund codes will be printed. You may only enter one of the following parameters: Specific Fund or Specific Fund Type. Fund type for reporting. You may only enter one of the following parameters: Specific Fund or Specific Fund Type.
Specific Fund Type
No
Report Sample
07/05/1996 12:21:36 FISCAL YEAR 96 COAS: A
Banner - SEED Data Consolidated Statement of Financial Position AS OF 30-JUN-1996 Institute of Technology Current Year As of 30-JUN-1996 Prior Year As of 30-JUN-1995 -5,339.00 0.00 0.00 -----------------5,339.00 ----------------2,612.28
PAGE 2 FGRFPSN
Change
NET ASSETS: Unrestricted Temporarily Restricted Permanently Restricted TOTAL: TOTAL: Net Assets Liabilities and Net Assets 14,553,119.35 50.00 1,500.00 -----------------* 14,554,669.35 -----------------20,237,493.78 14,558,458.35 50.00 1,500.00 ----------------14,560,008.35 ----------------20,234,881.50
* NET ASSETS AS PER LEDGERS = 14,553,669.35 *** FUND(S) ARE OUT OF BALANCE. PLEASE RUN FGRTBEX TO DETERMINE SOURCE(S) OF OUT OF BALANCE CONDITION ***
4-221
November 2010
Balance Forward Processing Report (FGRGLRL)

Description
This report closes all prior year control account balances into the current fiscal year fund balance. It creates open balances in the current fiscal year and opens the accrual period in the prior fiscal year. Once the general ledger balances have been rolled, the system will maintain general ledger balances in both the prior and current fiscal years as appropriate. Do not execute FGRGLRL again. If the system encounters errors, this process rolls back. A message prints at the end of FGRGLRL indicating errors. The funds and accounts containing errors list in the body of FGRGLRL. This process interrogates the Multiple Fund Balance Indicator on the System Control Maintenance Table (FOASYSC). If the indicator is set to N (No), the process closes control account information and fund addition/ deduction balances into the fund balance account defined on FTMCOAS. If the indicator is set to Y (Yes), the process closes year-to-date control information and fund addition/ deduction balances to the fund balance account(s) defined on FTMFBAL. Budget and encumbrance control activity close to the fund balance account defined on FTMCOAS.
Parameters
Name
Required?
Description
Values
Report Mode
Yes
Enter A (Audit) to generate this report, or enter U (Update) to update the database and generate this report.
U A
Update Audit (default)
4-222
November 2010
Banner University Balance Forward Processing Report As of 01-JUL-1996
PAGE 1 FGRGLRL
------------------------PRIOR-YEAR BALANCES----------------------- ----------------------NEW-YEAR BALANCES----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL Fund: 301000 ------------------------PRIOR-YEAR BALANCES----------------------- ----------------------NEW-YEAR BALANCES----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 1110 2110 3040 3050 Accounts Receivable Accounts Payable Encumbrance Control Budget Reservation Contr FUND TOTAL Fund: 401000 ------------------------PRIOR-YEAR BALANCES----------------------- ----------------------NEW-YEAR BALANCES----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL 25.00 .00 25.00 .00 25.00 25.00 25.00 .00 25.00 .00 4010 25.00 4010 25.00 Fund Balance Fund Balance 650.00 75.00 1,700.00 .00 2,425.00 .00 112.50 .00 1,700.00 1,812.50 650.00 .00 1,700.00 .00 2,350.00 .00 37.50 .00 1,700.00 1,737.50 1110 2110 4010 4010 Accounts Receivable Accounts Payable Fund Balance Fund Balance 100.00 .00 100.00 .00 100.00 100.00 100.00 .00 100.00 .00 4010 100.00 4010 100.00 Fund Balance Fund Balance
4-223
November 2010
Banner University Balance Forward Processing Report As of 01-JUL-1996
PAGE 2 FGRGLRL
------------------------PRIOR-YEAR BALANCES----------------------- ----------------------NEW-YEAR BALANCES----------------------ACCT TITLE DEBIT CREDIT DEBIT CREDIT ACCT TITLE 3040 3050 Encumbrance Control Budget Reservation Contr FUND TOTAL CHART TOTAL GRAND TOTALS 75.00 .00 75.00 2,625.00 2,625.00 .00 75.00 75.00 2,012.50 2,012.50 75.00 .00 75.00 2,550.00 2,550.00 .00 4010 75.00 4010 75.00 1,937.50 1,937.50 Fund Balance Fund Balance
4-224
November 2010
G/L Transaction Activity Report (FGRGLTA)

Description
The General Ledger Transaction Activity Report displays by Chart of Accounts and by fund beginning/ending balances for general ledger accounts and all debit and credit activity against those accounts.
Note General Ledger accounts have debits, credits, and balances. Beginning and ending balances are obtained directly from the General Ledger Table (FGBGENL). Debit and credit activity is obtained from the Transaction Detail (FGRTRND) and Transaction History (FGRTRNH) tables.
When a From Date and a To Date are specified that are on period boundaries, beginning and ending balances display on this report. Otherwise, if these dates are not on period boundaries, activity displays within the date ranges, without beginning and ending balances. Balances that are opposite an account's normal balance, (i.e., credit, debit, or zero) are flagged with an indicator to the right of the balance. All summarized transactions printed on the report display the run date of the summarization process, not the actual transaction date. As a result, summarized transactions may have dates that are not within the specific date range parameters. Summarized transactions posted to the period of the date range are displayed no matter what the transaction date is. The description for summarized transactions is not the transaction history description but a description entered by the user for summarized control accounts on the System Data Maintenance Form (FTMSDAT). Totals by fund are provided when the Print Fund Totals parameter equals Y(Yes). Total Debits, Total Credits, and Ending Balances are provided for all account types having activity during the period specified (From Date and To Date). When the Include Accrual for Last Period parameter is Y (Yes), the report displays fund balances and transaction activity posted to the accrual period during the last period of the fiscal year. When this parameter is Y (Yes), the To Date must be equal to the last day of the last period of the fiscal year and the period status indicator must be C (Closed). Parameters are provided to select a range of funds and accounts or to select a specific fund. To select a specific fund, enter the fund in both the From Fund Code and the To Fund Code. To select a specific account code, enter the account code in both the From Account Code and the To Account Code parameters.
4-225
November 2010
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts From Fund Code To Fund Code From Account Code To Account Code From Date To Date Include Accrual for Last Prd Print Fund Totals
Yes Yes No No No No No No Yes
Fiscal year for reporting. Chart of accounts for reporting. Fund code for the beginning range of funds to be reported. Fund code for the ending range of funds to be reported. Account code for the beginning range of accounts to be reported. Account code for the ending range of accounts to be reported. Date from which you wish to report. Date up to which you wish to report. Enter Y to include accrual for last period.
YY
DD-MON-YYYY DD-MON-YYYY Y N Yes No (default) Yes (default) No
Yes
Enter Y to print fund totals.
Y N
4-226
November 2010
Report Sample
03-OCT-96 16:29:02 FISCAL YEAR 96
Banner University G/L Transaction Activity From 01-MAY-1996 To 31-MAY-1996 Institute of Technology Current Unrestricted
PAGE 1 FGRGLTA
COAS: A FUND: 1000 TRANS DATE TRAN TYPE
DOCUMENT DOCUMENT NUMBER REF #
DESCRIPTION
ACCOUNT 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100
DEBITS
CREDITS 3,623.97
BALANCE .00
BEGINNING BALANCE: Accounts Payable - Operations 05/15/1996 INNI I0000042 Laboratory Supplies, Inc. 05/15/1996 TAXL I0000042 Penn. State Tax 05/15/1996 TAXL I0000042 Philadelphia Sales TAx 05/16/1996 INNI I0000047 Laboratory Supplies, Inc. 05/16/1996 TAXL I0000047 Penn. State Tax 05/16/1996 TAXL I0000047 Philadelphia Sales TAx 05/21/1996 CTXI F0000098 I0000042 Penn. State Tax 05/21/1996 CTXI F0000098 I0000042 Penn. State Tax 05/21/1996 CTXI F0000098 I0000042 Philadelphia Sales TAx 05/21/1996 CTXI F0000098 I0000042 Philadelphia Sales TAx 05/21/1996 DNNI F0000098 I0000042 Laboratory Supplies, Inc. 05/23/1996 APS4 F0000091 American Express Pymt 05/23/1996 CSSC F0000091 American Express Pymt 05/23/1996 APS4 F0000092 American Express Pymt 05/23/1996 CSSC F0000092 American Express Pymt 05/23/1996 RES1 F0000092 Refund Code 05/24/1996 DNNI 91052401 I0000070 Prior Year Expenditure Control 05/24/1996 INNI I0000070 Prior Year Expenditure Control 05/24/1996 TAXL I0000070 Penn. State Tax 05/24/1996 TAXL I0000070 Philadelphia Sales TAx 05/28/1996 DNNI D0000001 G0000004 Encumbrance Reserve Account 05/31/1996 DNNI K0000102 I0000047 Laboratory Supplies, Inc. 05/31/1996 DNNI K0000104 G0000001 Operating Cash Account ENDING BALANCE: Accounts Payable - Operations
203.21 33.88 1,155.60 64.80 10.80 203.21 203.21 33.88 33.88 3,386.88 33.00 33.00 99.50 99.50 63.00 9,000.00 9,630.00 539.99 90.01 1,200.00 1,080.00 500.00 16,479.16 TOTAL DEBITS
14,842.16 TOTAL CREDITS 14,842.16
1,063.00 ENDING BALANCE 1,063.00
TOTAL FUND: 1000 Current Unrestricted Liabilities
02
16,479.16
4-227
November 2010
Incomplete Document Report(FGRIDOC)

Description
Use this report to identify incomplete documents so that the appropriate action may be taken to complete them. You can list any combination of the following types of documents. All Document Types Journal Vouchers Cash Receipts Purchase Orders Blanket Orders Change Orders Invoices/Credit Memos Procurement Requisitions Stores Requisitions Stores Adjustments Receiving Documents Stores Issues Stores Transfers General Encumbrances Fixed Asset Adjustments The report parameters allow you to select a single user ID, specific user IDs or all user IDs for each document type chosen. For each selected incomplete document, the printed report will include the basic header information for the document as well as a choice of including Vendor Information, where applicable. The displayed header information and the document totals will vary based on the type of incomplete document. The report will sort the incomplete documents by document type. A sort order parameter enables you to sort by document number or user ID within the document type.
4-228
November 2010
Definition/Determination of Incomplete Documents are deemed incomplete based on the following criteria.
Type of Document
Criterion for Incomplete Status
Cash Receipts Journal Vouchers Blanket Orders Purchase Orders Change Orders Invoices Requisitions Adjustments Receiving Documents Transfers Stores Issues General Encumbrances Fixed Assets
Status indicator value of I or a null value.
Completion indicator value of N or a null value. The blanket order must also be active (not terminated). Completion indicator value of N or a null value.
Status field value of I or a null value. Status field value of N or a null value.
4-229
November 2010
Journal Voucher Listing Report (FGRJVLR)

Description
This report prints header and detail information for selected pending journal vouchers. This report can be used to print comprehensive information for one or more pending journal vouchers based on the journal voucher number, transaction date, status, journal type, or user ID. The default sort order for this report is by document number. However, you can also choose to sort this report by transaction date/document number or by user ID/document number. You can run this report from either the job submission module or online from the Journal Voucher Entry Form (FGAJVCD) or from the Journal Voucher Quick Form (FGAJVCQ). This report can be accessed from the journal voucher entry forms by selecting the Print JV button or be selecting the menu option which automatically calls the Process Submission Control Form (GJAPCTL) with the parameters for FGRJVLR displayed. Upon exiting the Process Submission Control Form, you are returned to the calling form (either the Journal Voucher Entry Form or the Journal Voucher Quick Form).
Parameters
Name
Required?
Description
Values
From Document Number No
If data is entered into this parameter, all pending journal vouchers with a document number greater than the From Document Number are printed. If left blank, all documents less than the To Document Number are printed. If entered, all pending journal vouchers with a document number less than the To Document Number are printed. If left blank, all documents greater than the From Document Number are printed. If entered, all pending journal vouchers with a transaction date after the specified From Transaction Date are printed. If left blank, all documents less than the To Transaction Date are printed. DD-MON-YYYY
To Document Number
No
From Transaction Date
No
4-230
November 2010
Parameters (cont)
Name
Required?
Description
Values
To Transaction Date
No
If entered, all pending journal vouchers with a transaction date before the specified To Transaction Date are printed. If left blank, all documents greater than the From Transaction Date are printed. If entered, only pending journal vouchers of the specified journal type (i.e, rule class code) are printed. You can repeatedly enter one or more journal types to report on. If left blank, all journal types are printed. If entered, only pending journal vouchers entered by the specified user are printed. You can repeatedly enter one or more User ID. If left blank, journal vouchers entered by all users are printed. If entered, only pending journal vouchers for the specified document status are printed. You can repeatedly enter one or more document status codes. If left blank, all documents are printed regardless of the document status. If entered, only pending journal vouchers with the specified sequence status are printed. You can repeatedly enter one or more sequence status codes. If left blank, all journal vouchers sequences are printed regardless of the sequence status.
DD-MON-YYYY
Journal Type
No
User ID
No
Document Status
No
Sequence Status
No
4-231
November 2010
Parameters (cont)
Name
Required?
Description
Values
Include Text
No
Leave blank or enter Y to include document text in the report. Enter N if you do not wish to include document text in the report. There are four valid sort orders for this report.
Y N
Yes No Document number (Blank is the default.) Transaction date/ document number User ID/document number
Sort By
No
D or blank T U
4-232
November 2010
Report Sample
FGRJVLR
Development Journal Voucher Listing
30-OCT-1995 14:06:46 Page 1
TRANSACTION DOCUMENT DOCUMENT DEFER DOCUMENT# SUB# DATE TOTAL NSF STATUS APPROVED EDIT USER ID --------- -------------- ----------------------- -------- ----- -----------------------------J0001 0 25-OCT-1995 200.00 Y I N FIMSUSR =============================================================================================================================== SEQ# ---1 JOURNAL TYPE ------JE15 FS STATUS YR CHART INDEX FUND ORG ACCOUNT PROGRAM ACTIVITY LOCATION ------ -- ----- ------ ------ ------ ------- ------- -------- -------P 95 A 1000 125 6111 100 DOCUMENT BANK REF# ---- -------BUDGET PERIOD -----COMMIT TYPE PERCENT ---- ------ABAL OVERRIDE: Y CASH CODE -----DEP#: POST PERIOD -----04 PROJECT DISTRIB TRANSACTION CODE PERCENT AMOUNT -------- ------- ------------100.00 CHART POOL ----FUND POOL -----AMT: 0.00 DB/ CR --D
ENCUMBRANCE NUMBER ITEM SEQ# TYPE ACTION -------- ---- ---- ---- -----DESC: Amount for Math Department
ACCRUAL:
CURR CODE:
---------------------------------------------------------------------------------------------------------------------------SEQ# ---2 JOURNAL TYPE ------JE15 FS STATUS YR CHART INDEX FUND ORG ACCOUNT PROGRAM ACTIVITY LOCATION ------ -- ----- ------ ------ ------ ------- ------- -------- -------P 95 A 1000 155 6111 100 DOCUMENT BANK REF# ---- -------BUDGET PERIOD -----COMMIT TYPE PERCENT ---- ------CASH CODE -----DEP#: POST PERIOD -----04 PROJECT DISTRIB TRANSACTION CODE PERCENT AMOUNT -------- ------- ------------100.00 CHART POOL ----FUND POOL -----AMT: 0.00 DB/ CR --C
ENCUMBRANCE NUMBER ITEM SEQ# TYPE ACTION -------- ---- ---- ---- -----DESC: Amount for Math Department
ACCRUAL:
ABAL OVERRIDE: Y
CURR CODE:
4-233
November 2010
Roll Open Labor Encumbrances Process (FGRLENC)

This process is similar to the Roll Open Encumbrances Process (FGRENRL), but processes labor encumbrances only. The FGRLENC process is optional if you do not use the multiple year encumbrance enhancement. The standard four year end processes (G/L Roll, Encumbrance Roll, Budget Carry Forward and the Closing Process) need to be performed in the order displayed on FGAYRLM. The new FGRLENC process is an exception to this rule. FGRLENC is not dependent on the execution of other year-end processes and it does not need to be run if you are not using the multiple year encumbrance enhancement. The FGRLENC process enables institutions to perform the following tasks: Roll forward open multi-year future labor encumbrances into the new fiscal year, based on the criteria specified on the Chart of Accounts Validation Table (FTVCOAS) and the Year End Maintenance Form (FGAYRLM). Close non multi-year labor encumbrances in the current fiscal year Close rolled labor encumbrances in the new fiscal year
Note This process can be run any time after the last day of the old fiscal year and not does depend on any other Banner Finance year end process. This process does not need to be run if you are not using multiple year encumbrancing.
4-234
November 2010
Parameters
Name
Required?
Description
Values
Report Mode
Yes
When the FGRLENC process is run in Audit mode, A it provides a list of open HR labor encumbrances that U it will close or roll. If FGRLENC finds that some open encumbrance items are against a fund code with a termination or an expenditure end date that precedes the first day of your new fiscal year, it displays those exceptions in the .log file. This gives you the chance to re-instate the fund and include those items in this process, if desired. When the FGRLENC process is run in Update mode, it inserts records into the transaction interface table (FGBTRNI) for editing and processing to the ledgers.
Audit (default) Update
Process Current or Rolled
Yes
The FGRLENC process must be executed twice: first in C mode and then in R mode.
C R
Current year processing Rolled future encumbrances
4-235
November 2010
Required?
Description
Values
Current Year Process Because C mode rolls future items in the new fiscal year, you must verify that these items have posted before you attempt to close them using R mode. Due to this timing consideration, FGRLENC needs to be executed twice. When the FGRLENC process is run with a parameter value of C in Update mode, the Ending Document Number on FGAYRLM is updated, but the Performed Date remains blank. The FGRLENC process performs the following steps: Interrogates the Encumbrance Detail Table (FGBENCD) for all open current encumbrances (those items with an item number of 0,1, or 2). Validates that only HR labor encumbrances (encumbrance numbers starting with PR%) are selected, and closes those encumbrances in the old fiscal year. Interrogates open HR future encumbrance items (items with an item number of 3,4, or 5) and rolls those forward in the new fiscal year.
4-236
November 2010
Required?
Description
Values
Rolled Process When the FGRLENC process is run with a parameter value of R in Update mode, the Ending Document Number will be reviewed, and a one-up number will be generated for the next step of the process. When this process is completed, the FGAYRLM Ending Document Number is updated and the Performed Date is populated. If you attempt to run the process with a parameter value of R before first running it with a value of C, the system checks for an Ending Document number. If one does not exist, the FGRLENC process halts and displays the following error message: *ERROR* FGRLENC must be run in C mode before R mode can be processed.
Setup on FGAYRLM
Before you can use the FGRLENC process, you must enter the appropriate data on the Year End Maintenance Form (FGAYRLM).
1. Access FGAYRLM. 2. Enter Roll HR Labor Encumbrances values for the Starting Document Number and Scheduled Date fields.
The Starting Document Number must begin with PR.

3. Save.
4-237
November 2010
Setup on FTMCOAS
The new Roll HR Labor Encumbrances Process (FGRLENC) only looks to the Encumbrance Parameters block to pick up the Rule Class Code for processing. All other values pertain to previously existing processes, such as FGRENRL. Unlike non-HR encumbrances, the FGRLENC process does not carry over budget to cover the encumbrance balance. It looks only to the Chart or the Fund Type for the rule that will be used to roll encumbrance items.
1. Access the Chart of Accounts Maintenance Form (FTMCOAS). 2. Query on the chart and navigate to Encumbrance Parameters. 3. In the Encumbrance Parameter section, specify the Rule Class Code you wish to use for rolling HR labor
encumbrances. Verify that the rule class is valued. This is the rule that will be used in rolling future encumbrance items to the new fiscal year. Remember that you can override this rule by Fund Type using the FTMFTYP form. This rule is shared by the Encumbrance Roll Process (FRGENRL) and FGRLENC. The only difference between the two processes is that FGRLENC does not use information provided in the Document Roll parameters as FGRENRL does. FGRENRL uses the indicators as follows: If the Labor Encumbrance indicator is checked, FGRENRL will roll labor encumbrances as long as the encumbrance number does not begin with PR. If the Labor Encumbrance indicator is unchecked, FGRENRL will close all labor encumbrances not starting with a encumbrance number of PR. Those may be labor encumbrances interfaced from an outside system or labor encumbrances created in the Banner Finance System using the FGAENCB form.
Note The only way to differentiate labor encumbrances from Banner HR is by the first two characters of the encumbrance number. The encumbrance number always begins with PR.
4-238
November 2010
Setup on FTMSDAT
1. Access the System Data Maintenance Form (FTMSDAT) to verify that the rule class has been established for
closing encumbrance items.

2. In Enter Query mode, enter FGBTRNI in the Entity field, and FGBTRNI_ENC_CLOSE_RUCL_CODE in
the Attribute field. Execute the query.

3. The Data field displays the rule (E032 or similar as defined in FTMSDAT) used to perform an encumbrance
close.
FGRLENC Processing Steps

The FGRLENC process is run in a series of steps.
1. Run the FGRLENC process with a parameter of C to close the current year encumbrances and roll the future
encumbrances forward to the new fiscal year.

2. Manually run the FGRTRNI, FGRTRNR, and FGRACTG processes to edit and post FGRLENC documents. 3. Run the FGRLENC process with a parameter of R to close future encumbrances in the new fiscal year. 4. Manually run the FGRTRNI, FGRTRNR, and FGRACTG processes to edit and post FGRLENC documents.
Step 1: Run the FGRLENC process to close the current year encumbrances and roll the future encumbrances forward to the new fiscal year. When you run FGRLENC in C mode, the process performs the following steps:
1. FGRLENC looks at the FGBENCH encumbrance header table to select transactions with a Type of L (Labor),
Encumbrance number of PR, and a status of O (Open).

2. The process looks at the FGBENCD encumbrance detail table for the Item. 3. It selects items with a value of 0, 1, or 2 and a status of O (open). It determines the rule class to use from
FTVSDAT for closing encumbrances.
4-239
November 2010
4. Using the starting document number defined on FGAYRLM for Roll HR Labor Encumbrances, FGRLENC
inserts records into the FGBTRNI table to close the current fiscal year HR labor encumbrance amounts. When performing this process, FGRLENC uses the liquidation rule you supplied in ftvsdat with a transaction date set to the last day of the fiscal year. The FGRLENC process next performs future year encumbrance transactions dependent on Item number as described in the following steps:
5. FGRLENC looks at the FGBENCH encumbrance table and selects those transactions with a Type of L
(Labor), Encumbrance number of PR, and a status of O (Open).

6. The process looks at the Item field value for those records with a value of 3, 4, or 5. 7. If run in Update mode, FGRLENC assigns a new document from the last one used to perform the
encumbrance close of the current encumbrances. Then, FGRLENC inserts records into the FGBTRNI table to roll the remaining balance of the encumbrance to the new fiscal year, while maintaining the original encumbrance number. The existing Rule Class defined on the Fund Type Maintenance form (FTVFTYP_RUCL_CODE_ROLL_ENC) or Chart of Accounts Code form (FTVCOAS_RUCL_CODE_ROLL_ENC) is used for the transactions. A transaction date of the first day of the new fiscal year will be used.
8. The process produces a hard copy report listing the encumbrances closed and rolled encumbrances sorted by
fund within chart. It then updates the Ending document number in the FGBYRLM table. Step 2 - Manually run the FGRTRNI, FGRTRNR, and FGRACTG processes to edit and post FGRLENC documents. You need to perform the following steps:
1. Run the FGRTRNI process (or let Sleep/Wake kick off the process automatically, depending upon the
institutions setup) to edit the transactions and insert records into the FGBJVCH and FGBJVCD tables.
2. Run the FGRTRNR process to report any errors. If there are no errors, the FGRTRNI process updates the
FOBAPPD table.
3. Run the FGRACTG process (usually set up in Sleep/Wake mode) which updates the Banner Finance ledgers
and the FGBTRNH and FGBTRND tables.
4-240
November 2010
Step 3 - Run the FGRLENC process to close the rolled future encumbrances in the new fiscal year. When you run FGRLENC in R mode, the process performs the following steps:
1. Looks at the FGBENCH encumbrance table to select those transactions that have a Type of L (Labor),
Encumbrance number of PR, and a status of O (Open).

2. Looks at the FGBENCD encumbrance detail table for items that have a value of 3, 4, or 5. 3. Assigns a new document from the last one used, which is displayed as the ending document number in
FGBYRLM, to perform the encumbrance close of the future encumbrances.

4. Inserts records into the FGBTRNI table to liquidate the new multi-year rolled encumbrances using the
liquidation rule you supplied in ftvsdat in the new fiscal year, and the fiscal year begin date as the transaction date.
5. Produces a hard copy report listing closed encumbrance items, sorted by fund within chart. 6. Updates the Document Number and Performed Date on FGAYRLM.
Step 4 - Manually run the FGRTRNI, FGRTRNR, and FGRACTG processes to edit and post FGRLENC documents. You need to perform the following steps:
1. Run the FGRTRNI process (or let Sleep/Wake kick off the process automatically, depending upon the setup at
your institution) to edit the transactions and insert records into the FGBJVCH and FGBJVCD tables.
2. Run the FGRTRNR process to report any errors.If there are no errors, the FGRTRNI process updates the
FOBAPPD table.
3. Run the FGRACTG process (usually set up in Sleep/Wake mode) which updates the Banner Finance ledgers
and the FGBTRNH and FGBTRND tables.
4-241
November 2010
Location Hierarchy Report (FGRLOCH)

Description
This report displays the hierarchical relationship in the location code structure. Status, effective, termination, and next change dates are displayed for each location code printed on the report. Location codes display which have an effective date less than or equal to the as of date and where next change date is greater than the as of date.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date (DD-MON-YYYY) Location Code
Yes Yes
Yes
Location code for reporting. Leave blank for all location codes.
4-242
November 2010
Report Sample
REPORT FGRLOCH CHART: A
Banner University Location Hierarchy Report AS OF 21-AUG-1996 DESCRIPTION Administrative Services Bldg. Fellowship Building 4th Floor 4th Floor - Room 401 4th Floor - Room 402 Bursars Office - 110 Collections Office - 110 -A Student Accounts - 110 -B Travel Accounts - 110 -C 1st Floor 3rd Floor Admin. Accounting Office - 310 Disbursements Office - 310-A Payroll Office - 310-B Grant Accounting - 310-C Budget Office - 322 3rd Floor - Room 320 4th floor - Room 413 Menkins Technology Hall 1st Floor Deans Office - Suite 110 Auerbach Hall Beecher Auditorium Main Campus Main Campus, Section 0 Presidents Office - Suite 6 Provosts Office - Suite 8 Vice President Finance - Suite 10 Vice President Admin - Suite 10 V. P. Information Systems - Suite 9 Main Campus, Section L1 Secondary Campus Secondary Campus, Section 1 Operations & Maintenance Building Grounds Department 1st Floor Housekeeping - Room 210 Plumbing & Electrical - 2nd Floor STATUS A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A ********* EFF TERM 24-JUN-1995 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992 01-OCT-1992
RUN DATE: 08/21/1996 TIME: 12:15 PM PAGE: 1 DATES ********* NEXTCHANGE 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999
LOCATION 01 100 1000 1001 1002 1010 1015 1016 1018 110 1100 1120 1121 1130 1132 1201 1101 1003 200 2000 2010 2100 2110 1 10 11 12 14 16 18 1L1 2 21 20 400 412 420
4-243
November 2010
Organization Detail Activity Report (FGRODTA)

Description
This report is sorted by account and fund within each organization. This report displays expenses, budget and encumbrance activity (operating ledgers record budget and encumbrance activity) within a specified period. When a From Date and a To Date are specified that are on period boundaries, beginning and ending balances display on this report. Otherwise, if these dates are not on period boundaries, activity displays within the date ranges without beginning and ending balances.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts
Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Organization code for the beginning range of organizations to be reported. Organization code for the ending range of organizations to be reported. Fund code for the beginning range of funds to be reported. Fund code for the ending range of funds to be reported. Account code for the beginning range of accounts to be reported. Account code for the ending range of accounts to be reported. Beginning date of transactions to be reported.
YY
From Organization Code No To Organization Code From Fund Code To Fund Code From Account Code To Account Code From Date (DD-MON-YYYY) To Date (DD-MON-YYYY) No No No No No Yes
Yes
Ending date of transactions to be reported.
4-244
November 2010
Parameters (cont)
Name
Required?
Description
Values
Include Accrual for Last Prd
Yes
Y N
Yes No (default) Yes (default) No Uncommitted (default) Committed Both
Print Organization Totals Yes
Enter Y to print organization totals.
Y N
Commitment Type
Yes
Enter U for Uncommitted, C for Committed, or B for Both.
U C B
4-245
November 2010
Report Sample
13-JAN-1996 09:21:35 FISCAL YEAR 96
Banner University Organization Detail Activity From 01-JAN-1996 To 31-JAN-1996 Banner University Accounting Office
PAGE 1 FGRODTA
COAS: A ORG: 215 TRANS DATE TRAN TYPE
DESCRIPTION Current Unrestricted
ACCOUNT/ FUND 1000 5120 5120 5120 6010 6010 6010 6010 6155 6155 6155 6155
BUDGET ACTIVITY
TRANSACTION ACTIVITY
ENCUMBRANCE CMT ACTIVITY TYP
BEGINNING BALANCE: Full Time Administrative Salaries 01/04/1996 HGRS F0000092 Gross Earnings Payroll Expense ENDING BALANCE: Full Time Administrative Salaries BEGINNING BALANCE: Supplies Accounts 01/04/1996 INNI I0000662 ABC Supply House 01/05/1996 PORD P0000642 Office Supplies, Inc. ENDING BALANCE: Supplies Accounts BEGINNING BALANCE: Consulting Services 01/07/1996 BD02 Budget Adjustment 01/08/1996 PORD P0000645 Consulting Services, Inc. ENDING BALANCE: Consulting Services TOTAL ORGANIZATION: 215 Accounting Office Labor Expense General & Administrative Expense
4,500.00 4,500.00 450.00 450.00 .00 200.00 200.00
1,200.00 150.00 1,350.00 60.00 35.00 95.00 .00 .00
3,000.00 -150.00 2,850.00 45.00 75.00 120.00 .00 200.00 200.00 U U
06 06
.00 200.00
150.00 95.00
-150.00 275.00
4-246
November 2010
Open Encumbrance Report (FGROPNE)

Description
Use this report to print header information and remaining encumbered or reserved balance amounts for selected purchase orders, requisitions, and general encumbrances. Travel encumbrances are included with general encumbrances. Only records for documents that are open, completed, approved, and posted will be included in the report. The report contains the following three sections. Requisition section lists open procurement and stores requisitions Purchase Order section lists open purchase orders General Encumbrance section lists open general accounting encumbrances The report may be printed using either of two different layouts. Document layout prints open encumbrances for selected user IDs. FOAPAL layout prints open encumbrances for selected user IDs and for a range of FOAPAL elements sorted by chart of accounts. If the Document layout is chosen, the open encumbrances are automatically grouped by document type and are printed in number order within each group. If the FOAPAL layout is chosen, the user may sort documents by any one of the FOAPAL elements. The default is F (Fund); other options are O (Organization), A (Account), P (Program), V (Activity), or L (Location). Totals for the number of records and remaining balances will be printed whenever the FOAPAL element used to determine sort order changes. In either layout, the total number and remaining balance for the records will be printed on the last page of each document group.
4-247
November 2010
Report Sample 1 (Page 1 of 3)
FGROPNE
3.1 Requisitions
BANNER University Open Encumbrances Report
23-JAN-2001 14:52:44 Page 1
DOCUMENT TYPE: REQUEST NUMBER -------R0000083 R0000084 R0000087
REQUESTOR NAME ----------------------------------Jane Smith Jane Smith Jane Smith 3
REQUEST USER ID TYPE --------------- ------SYSTEST04 P SYSTEST04 P SYSTEST04 P
DELIVERY DATE ----------28-JAN-2001 31-JAN-2001 25-JAN-2001
TRANSACTION DATE ----------11-JAN-2001 11-JAN-2001 11-JAN-2001
ENCUMBRANCE AMOUNT ---------------250.00 382.20 10.00
REMAINING BALANCE ---------------250.00 382.20 10.00
Total Open Requisition Records:
Total Requisition Balance:
FGROPNE
3.1 Purchase Orders
23-JAN-2001 14:52:44 Page 2
DOCUMENT TYPE: P.O. NUMBER -------P0000049 P0000050 P0000053 P0000054
VENDOR/PAYEE NUMBER NAME --------- ----------------------------------711100001 Wu,Steven 711100001 Wu,Steven 711100001 Wu,Steven 711100001 Wu,Steven 4
USER ID --------------SYSTEST04 SYSTEST04 SYSTEST04 SYSTEST04
BLANKET NUMBER --------
TRANSACTION DATE ----------01-MAY-2000 01-AUG-2000 11-JAN-2001 11-JAN-2001
ENCUMBRANCE AMOUNT ---------------122.50 112.00 220.00 20.00 $
REMAINING BALANCE ---------------122.50 112.00 220.00 20.00 4
Total Open Purchase Order Records:
Total Purchase
Order Balance:
4-248
November 2010
FGROPNE
3.1
23-JAN-2001 14:52:44 Page 3
PARAMETER SEQUENCE NUMBER: 7236 REPORT LAYOUT: D USER ID: SYSTEST04 LINES PER PAGE: 55 TOTAL TOTAL TOTAL TOTAL TOTAL TOTAL OPEN REQUISITION RECORDS: 3 REQUISITON BALANCE: $642.20 OPEN PURCHASE ORDER RECORDS: 4 PURCHASE ORDER BALANCE: $474.50 OPEN GENERAL ENCUMBRANCE RECORDS: 0 GENERAL ENCUMBRANCE BALANCE: $0.00
NUMBER OF RECORDS PROCESSED: 7 TOTAL ENCUM
FGROPNE
3.1 Requisitions
23-JAN-2001 14:43:17 Page 1
DOCUMENT TYPE: FUND: COAS: 1110 B
FUND:
1110
ORGN:
11009
ACCT:
7120
PROG:
90
ACTV: DELIVERY DATE ----------24-DEC-2000
LOCN: TRANSACTION DATE ----------21-DEC-2000 ENCUMBRANCE AMOUNT ---------------12.00 $ $ REMAINING BALANCE ---------------12.00 12.00
REQUEST NUMBER -------R0000050
REQUESTOR NAME ----------------------------------stacie 1 1
REQUEST USER ID TYPE --------------- ------SYSTEST03 P
TOTALS FOR FUND: 1110 Open Requisition Records:
Requisition Balance: Total Requisition Balance:
Total Open Requisition Records:
4-249
November 2010
FGROPNE
3.1 Purchase Orders
23-JAN-2001 14:43:17 Page 2
DOCUMENT TYPE: FUND: COAS: 1110 B
FUND:
1110
ORGN:
11009
ACCT:
7210
PROG:
10
ACTV: BLANKET NUMBER -------ACTV: BLANKET NUMBER --------
LOCN: TRANSACTION DATE ----------07-JUL-2000 LOCN: TRANSACTION DATE ----------31-JUL-2000 ENCUMBRANCE AMOUNT ---------------1,399.50 $ $ REMAINING BALANCE ---------------1,399.50 1,439.88 ENCUMBRANCE AMOUNT ---------------98.00 REMAINING BALANCE ---------------40.38
P.O. NUMBER -------P0000015 COAS: B
VENDOR/PAYEE NUMBER NAME --------- ----------------------------------300000020 ARCO Manufacturing Co., Inc. FUND: 1110 ORGN: 11009 ACCT: 7510
USER ID --------------FIMSUSR PROG: 10
P.O. NUMBER -------P0000001
VENDOR/PAYEE NUMBER NAME --------- ----------------------------------300000009 FM Computer 2 2 Purchase
USER ID --------------OPS$BMOD3
TOTALS FOR FUND: 1110 Open Purchase Order Records:
Order Balance: Order Balance:
Total Open Purchase Order Records:
Total Purchase
4-250
November 2010
FGROPNE
3.1
23-JAN-2001 14:43:17 Page 3
PARAMETER SEQUENCE NUMBER: 7235 REPORT LAYOUT: F USER ID: ALL FROM FUND CODE: TO FUND CODE: FROM ORGANIZATION CODE: 11009 TO ORGANIZATION CODE: 11009 FROM ACCOUNT CODE: TO ACCOUNT CODE: FROM PROGRAM CODE: TO PROGRAM CODE: FROM ACTIVITY CODE: TO ACTIVITY CODE: FROM LOCATION CODE: TO LOCATION CODE: SORT ORDER: F LINES PER PAGE: 55 TOTAL TOTAL TOTAL TOTAL TOTAL TOTAL OPEN REQUISITION RECORDS: 1 REQUISITON BALANCE: $12.00 OPEN PURCHASE ORDER RECORDS: 2 PURCHASE ORDER BALANCE: $1,439.88 OPEN GENERAL ENCUMBRANCE RECORDS: 0 GENERAL ENCUMBRANCE BALANCE: $0.00
NUMBER OF RECORDS PROCESSED: 3 TOTAL ENCUMBRANCE BALANCE: $1,451.88
4-251
November 2010
Organization Hierarchy Report (FGRORGH)

Description
This report displays the hierarchical relationship in the organization code structure. Data entry indicator, status, budget control organization, combine budget control indicator, effective, termination, and next change dates are displayed for each organization code printed on the report. Organization codes display which have an effective date less than or equal to the As Of date and where the next change date is greater than the As Of Date.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date (DD-MON-YYYY) Organization
Yes Yes
No
Organization code for reporting. Leave blank to display all organization codes.
4-252
November 2010
Report Sample
REPORT FGRORGH CHART: A
Banner University Organization Hierarchy Report AS OF 21-AUG-1996 DESCRIPTION Office of the President Office of the Provost College of Arts & Sciences Biology Department Biology Chemical Department Biology Department - Org Def Test Mathematics Department Geology Department College of Engineering Electrical Engineering Chemical Engineering Mechanical Engineering Vice President Business & Finance Office of the Treasurer Accounting Office Payroll Office Budget Office Budget Office Physical Plant - Stores County Court County Court President-CU Vice President - Health Sciences School of Medicine - CU Clinical Surgery Cardiology Surgeon 1 Surgeon 2 Surgeon 3 DATA ENTRY N N N Y Y Y Y Y N Y Y Y N Y Y Y Y Y Y Y Y N N N N N Y Y Y Y STATUS A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A CNTL ORGN CMB
RUN DATE: 08/21/1996 TIME: 12:11 PM PAGE: 1 ********* DATES ********* EFF TERM NEXTCHANGE 01-JUL-1996 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 18-MAR-1996 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 01-JUL-1994 31-DEC-1999 20-FEB-1996 31-DEC-1999 25-JUL-1995 31-DEC-1999 27-JAN-1996 27-JAN-1996 13-JUN-1992 13-JUN-1992 13-JUN-1992 13-JUN-1992 13-JUN-1992 13-JUN-1992 13-JUN-1992 13-JUN-1992 13-JUN-1992 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999
ORGANIZATION 001 100 110 120 121 122 125 135 150 155 160 165 200 210 215 220 250 260 261 2010 2020 PRES VP_HS SCHMED CLIN SURG CARDIO SURG1 SURG2 SURG3
200
4-253
November 2010
Program Detail Activity Report (FGRPDTA)

Description
This report displays expense, budget, and encumbrance activity for the period sorted by program and fund within an organization. The operating ledgers record budget and encumbrance activity. When a From Date and a To Date are specified that are on period boundaries, beginning and ending balances display on this report. If these dates are not on period boundaries, activity displays within the date ranges without beginning and ending balances. Balances that are opposite an account's normal balance, (that is, credit, debit, or zero) are flagged with an indicator to the right of the balance.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts
Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Organization code for the beginning range of accounts to be reported. Organization code for the ending range of accounts to be reported. Fund code for the beginning range of funds to be reported. Fund code for the ending range of funds to be reported. Program code for the beginning range of programs to be reported. Program code for the ending range of programs to be reported. Account code for the beginning range of accounts to be reported. Account code for the ending range of accounts to be reported.
YY
From Organization Code No To Organization Code From Fund Code To Fund Code From Program Code To Program Code From Account Code To Account Code No No No No No No No
4-254
November 2010
Required?
Description
Values
From Date (DD-MON-YYYY) To Date (DD-MON-YYYY) Include Accrual for Last Prd
Yes
Beginning date of transactions to be reported.
Yes
Ending date of transactions to be reported.
Yes
Y N
Yes No (default) Yes (default) No Committed Uncommitted (default) Both
Print Organization Totals Yes
Enter Y to print organization totals.
Y N
Commitment Type
Yes
Enter C for Committed, U for Uncommitted, or B for Both.
C U B
4-255
November 2010
Report Sample
13-JAN-1996 09:21:35 FISCAL YEAR 96
Banner University Program Detail Activity From 01-JAN-1996 To 31-JAN-1996 Banner University Accounting Office
PAGE 1 FGRPDTA
COAS: A ORG: 215 TRANS DATE TRAN TYPE
DESCRIPTION Current Unrestricted Administration
FUND/PRG ACCT 1000 100 5120 5120 5120 6010 6010 6010 6010 6155 6155 6155 6155
BUDGET ACTIVITY
TRANSACTION ACTIVITY
ENCUMBRANCE CMT ACTIVITY TYP
BEGINNING BALANCE: Full Time Administrative Salaries 01/04/1996 HGRS F0000092 Gross Earnings Payroll Expense ENDING BALANCE: Full Time Administrative Salaries BEGINNING BALANCE: Supplies Accounts 01/04/1996 INNI I0000662 ABC Supply House 01/05/1996 PORD P0000642 Office Supplies, Inc. ENDING BALANCE: Supplies Accounts BEGINNING BALANCE: Consulting Services 01/07/1996 BD02 Budget Adjustment 01/08/1996 PORD P0000645 Consulting Services, Inc. ENDING BALANCE: Consulting Services TOTAL ORGANIZATION: 215 Accounting Office Labor Expense General & Administrative Expense
4,500.00 4,500.00 450.00 450.00 .00 200.00 200.00
1,200.00 150.00 1,350.00 60.00 35.00 95.00 .00 .00
3,000.00 -150.00 2,850.00 45.00 75.00 120.00 .00 200.00 200.00 U U
06 06
.00 200.00
150.00 95.00
-150.00 275.00
4-256
November 2010
Pro Rata Allocation Process (FGRPRAP)

Description
The Pro Rata Allocation Process prepares allocations for existing transactions based on user-defined parameters. All eligible transactions which fit the criteria established in these parameters are selected from the FGBTRND table. Overlapping Allocation Source Organization/Account/Program strings are applied to the transaction to be allocated according to a predetermined hierarchy from the most detailed entry to the least detailed entry (see Chapter 2, Processing, for the specific hierarchy used by the Pro-Rata Allocation Process). The process also creates totals for all of the eligible transactions and, if requested, produces an Allocation Control Report. A detailed or summary version of the report may be selected by the user.
Parameters
Name
Required?
Description
Values
Allocation Begin Date Allocation End Date Allocation Transaction Date Chart of Accounts Source Funds Internal Account Type
No No No Yes No No
Beginning date of transactions to be allocated. Leave DD-MON-YYYY blank to default the current system date. Ending date of transactions to be allocated. Leave blank to default the current system date. Date assigned to allocation transactions. Leave blank to default the current system date. Chart of accounts for transactions to be selected for allocation and for the allocation transactions. Fund(s) from which transactions will be selected for allocation. Leave blank to select from all funds. Internal account type(s) from which transactions will be selected for allocation. Leave blank to select from internal account types: 50, 60, and 70. Bank code used for allocation target posting. Bank code used for allocation contra posting. Default = blank (all) Default = 50, 60, 70 DD-MON-YYYY DD-MON-YYYY
Allocation Target Bank Code Allocation Contra Bank Code
Yes Yes
4-257
November 2010
Parameters (cont)
Name
Required?
Description
Values
Report Execution Mode
No
Enter P (Preview) in this parameter to generate this report, or U (Update) in this parameter to update the database and generate this report.
P U
Preview (default) Update
Report Type
No
Enter S (Summary) in this parameter to produce a S or blank Summary (default) summary report, enter D (Detail) in this parameter to produce a detailed report, or enter N (No report) to D Detail produce no report. N (No report) is not an available N No report option in P (Preview) mode. If this parameter is left blank, the summary report is produced.
4-258
November 2010
FGRPRAP 2.1.11 Chart of Accounts: X Source Fund: 1020 Target Fund: 3120
Banner Development Environment Pro-Rata Allocation Process Transaction Date: 30-JUN-1995
17-MAY-1996 *** PREVIEW Mode ***
PAGE
Source Transactions ------------------------------------------------------Orgn Acct Prog Fld Doc. Nr. Amount 101 6111 11 YTD I0000591 -254.32 TOTAL: -254.32 101 101 101 101 102 102 6121 6220 7210 7510 7110 7220 11 21 31 21 32 22 YTD RSV YTD RSV RSV RSV I0000591 TOTAL: R0000170 TOTAL: J0000247 TOTAL: R0000171 TOTAL: R0000171 TOTAL: R0000169 R0000170 TOTAL: R0000170 TOTAL: R0000171 TOTAL: -1017.28 -1017.28 35.00 35.00 1500.00 1500.00 34.38 34.38 34.38 34.38 10.31 17.50 27.81 17.50 17.50 34.38 34.38
Allocation ----------------------Pct. Amount 1.00 1.00 1.00 1.00 1.00 40.00 -2.54 -10.17 0.35 15.00 0.34 13.75
Source Contra-Account ----------------------Orgn Acct Prog 100 100 100 100 100 100 6111 6121 6220 7210 7510 7920 11 11 21 31 21 20
1.00 1.00 15.00
0.28 0.18 5.16
300 100 100
7220 7920 7920
30 32 10
102 103
7220 6111
32 12
RSV RSV
4-259
November 2010
PAGE
Source Transactions Allocation ------------------------------------------------------Orgn Acct Prog Fld Doc. Nr. Amount 103 7230 12 YTD I0000566 625.00 I0000569 625.00 TOTAL: 1250.00 103 7230 12 ENC P0000213 P0000219 P0000219 TOTAL: R0000132 R0000136 TOTAL: J0000246 TOTAL: J0000247 TOTAL: R0000172 TOTAL: R0000169 TOTAL: R0000171 TOTAL: 1250.00 1250.00 1500.00 4000.00 1000.00 1000.00 2000.00 1500.00 1500.00 -1500.00 -1500.00 51.56 51.56 10.32 10.32 34.38 34.38
Source Contra-Account --------------------------------------------Pct. Amount Orgn Acct Prog 0.00 Allocation Percentage is Zero
0.00
Allocation Percentage is Zero
103
7230
12
RSV
0.00 5.00 5.00 5.00 10.00 10.00 75.00 -75.00 2.58 1.03 3.44
Allocation Percentage is Zero 200 200 200 200 200 4005 6111 7110 6210 7110 21 22 31 30 30
201 201 201 202 202
4005 6111 7110 6210 7110
21 22 31 22 22
YTD YTD RSV RSV RSV
4-260
November 2010
Report Sample- Detail Report (Page 3 of 4)
PAGE
Source Transactions ------------------------------------------------------Orgn Acct Prog Fld Doc. Nr. Amount 202 7220 22 RSV R0000170 17.50 TOTAL: 17.50 202 301 301 302 302 303 7520 7110 7810 6210 7110 7210 32 31 22 32 22 32 RSV YTD RSV RSV RSV RSV R0000169 TOTAL: J0000246 TOTAL: R0000169 TOTAL: R0000171 TOTAL: R0000170 TOTAL: R0000169 TOTAL: 10.31 10.31 -1000.00 -1000.00 10.31 10.31 206.23 206.23 87.50 87.50 10.31 10.31
Allocation ----------------------Pct. Amount 10.00 20.00 10.00 30.00 25.00 25.00 25.00 1.75 2.06 -100.00 3.09 51.56 21.88 2.58
Source Contra-Account ----------------------Orgn Acct Prog 200 300 300 100 300 300 300 7220 7920 7110 7810 6210 7110 7920 30 10 31 22 32 22 30
4-261
November 2010
FGRPRAP 2.1.11 Chart of Accounts: X
PAGE
* * * REPORT CONTROL INFORMATION * * * Run Sequence Number: Allocation Begin Date: Allocation End Date: Allocation Trans Date: Chart of Accounts: Source Fund(s): Int. Account Types(s): Report Execution Mode: Report Type: Allocation Target Bank: Allocation Contra Bank: Nr. Lines per Page: Number of Transactions: Number of Allocations: Total Allocation Amount: *** ERRORS *** Document: J0000172--Fund: 1020 Orgn: 202 Acct: 4090 Prog: 21 Internal atyps of Source Acct 4090 (50) and Contra-acct 7920 (70) are incompatible. None Specified 01-APR-1995 30-JUN-1995 30-JUN-1995 X 1020 50 60 70 Preview Detail 55 29 21 12.32
4-262
November 2010
Banner Development Environment Pro-Rata Allocation Process Transaction Date: 30-JUN-1995 JV Doc: J0000250
17-MAY-1996 *** UPDATE Mode ***
PAGE
Summarized Source Transactions --------------------------------------------Orgn Acct Prog Fld Total Amount 101 6111 11 YTD -254.32 101 6121 11 YTD -1017.28 101 6220 21 RSV 35.00 101 7210 31 YTD 1500.00 101 7510 21 RSV 34.38 102 7110 32 RSV 34.38 102 7220 22 RSV 27.81 102 7220 32 RSV 17.50 103 6111 12 RSV 34.38 103 7230 12 YTD 1250.00 103 7230 12 ENC 4000.00 103 7230 12 RSV 2000.00 201 4005 21 YTD 1500.00 201 6111 22 YTD -1500.00 201 7110 31 RSV 51.56 202 6210 22 RSV 10.32 202 7110 22 RSV 34.38 202 7220 22 RSV 17.50 202 7520 32 RSV 10.31 301 7110 31 YTD -1000.00 301 7810 22 RSV 10.31 302 6210 32 RSV 206.23 302 7110 22 RSV 87.50 303 7210 32 RSV 10.31
Allocation Source Contra-Account --------------------------------------------Pct. Amount Orgn Acct Prog 1.00 -2.54 100 6111 11 1.00 -10.17 100 6121 11 1.00 0.35 100 6220 21 1.00 15.00 100 7210 31 1.00 0.34 100 7510 21 40.00 13.75 100 7920 20 1.00 0.28 300 7220 30 1.00 0.18 100 7920 32 15.00 5.16 100 7920 10 0.00 Allocation Percentage is Zero 0.00 Allocation Percentage is Zero 0.00 Allocation Percentage is Zero 5.00 75.00 200 4005 21 5.00 -75.00 200 6111 22 5.00 2.58 200 7110 31 10.00 1.03 200 6210 30 10.00 3.44 200 7110 30 10.00 1.75 200 7220 30 20.00 2.06 300 7920 10 10.00 -100.00 300 7110 31 30.00 3.09 100 7810 22 25.00 51.56 300 6210 32 25.00 21.88 300 7110 22 25.00 2.58 300 7920 30
4-263
November 2010
Report Sample - Report Summary (Page 2 of 2)
FGRPRAP 2.1.11 Chart of Accounts: X
Banner Development Environment Pro-Rata Allocation Process Transaction Date: 30-JUN-1995 JV Doc: J0000250
17-MAY-1996 *** UPDATE Mode ***
PAGE
* * * REPORT CONTROL INFORMATION * * * Run Sequence Number: Allocation Begin Date: Allocation End Date: Allocation Trans Date: Chart of Accounts: Source Fund(s): Int. Account Types(s): Report Execution Mode: Report Type: Allocation Target Bank: Allocation Contra Bank: Nr. Lines per Page: Number of Transactions: Number of Allocations: Total Allocation Amount: *** ERRORS *** Document: J0000172--Fund: 1020 Orgn: 202 Acct: 4090 Prog: 21 Internal atyps of Source Acct 4090 (50) and Contra-acct 7920 (70) are incompatible. None Specified 01-APR-1995 30-JUN-1995 30-JUN-1995 X 1020 50 60 70 Update Summary X1 X2 55 29 21 12.32
4-264
November 2010
Pro Rata Allocation Report (FGRPRAR)

Description
The Pro Rata Allocation Report allows you to re-create a list of the source transactions for any allocation transactions produced by the Allocation Process. The summary version of the report only includes the summary totals developed for each Allocation Source record and the Allocated Amounts for each derived total line of account distribution. The detailed version produces the full Fund/Organization/Account/Program account string detail of all the eligible transactions selected to create an allocation entry and includes the summary totals developed for each Allocation Source record. The detailed version also includes Allocated Amounts for each derived total line of account distribution.
Parameters
Name
Required?
Description
Values
Journal Voucher Document Num.
No
Journal voucher document from which allocations are selected for reporting. If this parameter is populated, the Report Begin Date, Report End Date, and Chart of Accounts are not prompted. Beginning date from which allocations will be reported. Leave blank to default the current system date. DD-MON-YYYY
Report Begin Date
No
Report End Date Chart of Accounts Report Type
No Yes No
Ending date from which allocations will be reported. DD-MON-YYYY Leave blank to default the current system date. Chart of accounts from which allocations are selected for reporting. Enter S (Summary) in this parameter to produce a summary report or D (Detail) in this parameter to produce a detailed report. If left blank, the summary report is produced. S D Summary (default) Detail
4-265
November 2010
FGRPRAR 3.0
Banner Development Environment Pro-Rata Allocation Report Transaction Date: 30-JUN-1995 JV Doc: J0000250
17-MAY-1996
PAGE
Chart of Accounts: X Source Fund: 1020 Target Fund: 3120
Source Transactions ------------------------------------------------------Orgn Acct Prog Fld Doc. Nr. Amount 101 6111 11 YTD I0000591 -254.32 TOTAL: -254.32 101 101 101 101 102 102 6121 6220 7210 7510 7110 7220 11 21 31 21 32 22 YTD RSV YTD RSV RSV RSV I0000591 TOTAL: R0000170 TOTAL: J0000247 TOTAL: R0000171 TOTAL: R0000171 TOTAL: R0000169 R0000170 TOTAL: R0000170 TOTAL: R0000171 TOTAL: -1017.28 -1017.28 35.00 35.00 1500.00 1500.00 34.38 34.38 34.38 34.38 10.31 17.50 27.81 17.50 17.50 34.38 34.38
Allocation ----------------------Pct. Amount 1.00 1.00 1.00 1.00 1.00 40.00 -2.54 -10.17 0.35 15.00 0.34 13.75
Source Contra-Account ----------------------Orgn Acct Prog 100 100 100 100 100 100 6111 6121 6220 7210 7510 7920 11 11 21 31 21 20
1.00 1.00 15.00
0.28 0.18 5.16
300 100 100
7220 7920 7920
30 32 10
102 103
7220 6111
32 12
RSV RSV
4-266
November 2010
FGRPRAR 3.0
17-MAY-1996
PAGE
Source Transactions ------------------------------------------------------Orgn Acct Prog Fld Doc. Nr. Amount 103 7230 12 YTD I0000566 625.00 I0000569 625.00 TOTAL: 1250.00 103 7230 12 ENC P0000213 P0000219 P0000219 TOTAL: R0000132 R0000136 TOTAL: J0000246 TOTAL: J0000247 TOTAL: R0000172 TOTAL: R0000169 TOTAL: R0000171 TOTAL: 1250.00 1250.00 1500.00 4000.00 1000.00 1000.00 2000.00 1500.00 1500.00 -1500.00 -1500.00 51.56 51.56 10.32 10.32 34.38 34.38
Allocation ----------------------Pct. Amount 0.00
Source Contra-Account ----------------------Orgn Acct Prog Allocation Percentage is Zero
0.00
Allocation Percentage is Zero
103
7230
12
RSV
0.00 5.00 5.00 5.00 10.00 10.00 75.00 -75.00 2.58 1.03 3.44
Allocation Percentage is Zero 200 200 200 200 200 4005 6111 7110 6210 7110 21 22 31 30 30
201 201 201 202 202
4005 6111 7110 6210 7110
21 22 31 22 22
YTD YTD RSV RSV RSV
4-267
November 2010
FGRPRAR 3.0
17-MAY-1996
PAGE
Source Transactions ------------------------------------------------------Orgn Acct Prog Fld Doc. Nr. Amount 202 7220 22 RSV R0000170 17.50 TOTAL: 17.50 202 301 301 302 302 303 7520 7110 7810 6210 7110 7210 32 31 22 32 22 32 RSV YTD RSV RSV RSV RSV R0000169 TOTAL: J0000246 TOTAL: R0000169 TOTAL: R0000171 TOTAL: R0000170 TOTAL: R0000169 TOTAL: 10.31 10.31 -1000.00 -1000.00 10.31 10.31 206.23 206.23 87.50 87.50 10.31 10.31
Allocation ----------------------Pct. Amount 10.00 20.00 10.00 30.00 25.00 25.00 25.00 1.75 2.06 -100.00 3.09 51.56 21.88 2.58
Source Contra-Account ----------------------Orgn Acct Prog 200 300 300 100 300 300 300 7220 7920 7110 7810 6210 7110 7920 30 10 31 22 32 22 30
4-268
November 2010
FGRPRAR 3.0
Banner Development Environment Pro-Rata Allocation Report
17-MAY-1996
PAGE
* * * REPORT CONTROL INFORMATION * * * Run Sequence Number: Allocation Doc Number: Report Begin Date: Report End Date: Chart of Accounts: Report Type: Nr. Lines per Page: Number of Transactions: Number of Allocations: Total Allocation Amount: None Specified J0000250 None Specified None Specified None Specified Detail 55 29 21 12.32
4-269
November 2010
FGRPRAR 3.0
17-MAY-1996
PAGE
Summarized Source Transactions --------------------------------------------Orgn Acct Prog Fld Total Amount 101 6111 11 YTD -254.32 101 6121 11 YTD -1017.28 101 6220 21 RSV 35.00 101 7210 31 YTD 1500.00 101 7510 21 RSV 34.38 102 7110 32 RSV 34.38 102 7220 22 RSV 27.81 102 7220 32 RSV 17.50 103 6111 12 RSV 34.38 103 7230 12 YTD 1250.00 103 7230 12 ENC 4000.00 103 7230 12 RSV 2000.00 201 4005 21 YTD 1500.00 201 6111 22 YTD -1500.00 201 7110 31 RSV 51.56 202 6210 22 RSV 10.32 202 7110 22 RSV 34.38 202 7220 22 RSV 17.50 202 7520 32 RSV 10.31 301 7110 31 YTD -1000.00 301 7810 22 RSV 10.31 302 6210 32 RSV 206.23 302 7110 22 RSV 87.50 303 7210 32 RSV 10.31
Allocation Source Contra-Account --------------------------------------------Pct. Amount Orgn Acct Prog 1.00 -2.54 100 6111 11 1.00 -10.17 100 6121 11 1.00 0.35 100 6220 21 1.00 15.00 100 7210 31 1.00 0.34 100 7510 21 40.00 13.75 100 7920 20 1.00 0.28 300 7220 30 1.00 0.18 100 7920 32 15.00 5.16 100 7920 10 0.00 Allocation Percentage is Zero 0.00 Allocation Percentage is Zero 0.00 Allocation Percentage is Zero 5.00 75.00 200 4005 21 5.00 -75.00 200 6111 22 5.00 2.58 200 7110 31 10.00 1.03 200 6210 30 10.00 3.44 200 7110 30 10.00 1.75 200 7220 30 20.00 2.06 300 7920 10 10.00 -100.00 300 7110 31 30.00 3.09 100 7810 22 25.00 51.56 300 6210 32 25.00 21.88 300 7110 22 25.00 2.58 300 7920 30
4-270
November 2010
FGRPRAR 3.0
Banner Development Environment Pro-Rata Allocation Report
17-MAY-1996
PAGE
* * * REPORT CONTROL INFORMATION * * * Run Sequence Number: Allocation Doc Number: Report Begin Date: Report End Date: Chart of Accounts: Report Type: Nr. Lines per Page: Number of Transactions: Number of Allocations: Total Allocation Amount: None Specified J0000250 None Specified None Specified None Specified Summary 55 29 21 12.32
4-271
November 2010
Program Hierarchy Report (FGRPRGH)

Description
This report displays the hierarchical relationship in the program code structure. The data entry indicator, status, effective, termination, and next change dates are displayed for each program code printed on the report. Program codes display which have an effective date less than or equal to the As of date and where the next change date is greater than the as of date.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date (DD-MON-YYYY) Program Code
Yes Yes
Yes
Program code for reporting. Leave blank to display all program codes.
Default = blank (all)
4-272
November 2010
Report Sample
REPORT FGRPRGH CHART: A
Banner University Program Hierarchy Report AS OF 21-AUG-1996 DESCRIPTION Instruction General Academic Instruction Degree Math Programs Biology Programs Biology Lab Vocational/Technical Instruction Requisite Preparatory/Remedial Inst General Studies - Nondegree General Studies - Degree Occupation Related Instruction Social Roles/Interaction Nondegree Home & Family Instruction Nondegree Research Institute & Research Centers Individual or Project Research Public Service Program Direct Patient Care Health Care Supportive Services Community Services Cooperative Extension Services Public Broadcasting Services Academic Support Program Library Services Museums and Galleries Educational Media Services Academic Computing Support Ancillary Support Academic Administration Course & Curriculum Development Student Service Program Student Service Administration Social And Cultural Development Counseling And Career Guidance Financial Aid Administration Student Auxiliary Services Intercollegiate Athletics Student Health/Medical Services DATA ENTRY Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y STATUS A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A ********* EFF TERM 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 24-OCT-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989 01-JUL-1989
RUN DATE: 08/21/1996 TIME: 11:51 AM PAGE: 1 DATES ********* NEXTCHANGE 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999 31-DEC-1999
PROGRAM 100 110 111 112 1121 120 130 140 145 150 160 170 200 210 220 300 310 320 330 340 350 400 410 420 430 440 450 460 470 500 510 520 530 540 550 560 570
4-273
November 2010
Statement of Revenues, Expenditures, Other Changes (FGRREOB)

Description
This report compares actual activity-to-date for revenues and expenditures to the budgeted activity-to-date with prior year activity and budget for the period specified in the As of Date parameter. Included is a calculation for the net change in fund balance, increase/decrease, as well as a calculation of the percentage of used budget. Variances are calculated for comparison.
Note Current year records with Uncommitted Commit Type are retrieved for this report.
Revenue is sorted by the specified level of account codes. Expenditures are sorted by level 1 program codes. However, expenditures and transfers for the auxiliary funds (internal fund type of 30) are sorted by the specified level account codes. The different display of expenditures for auxiliary funds is based upon the assumption that expenses are entered with auxiliary program codes. These program codes may roll up to the same level 1 program code. In order to display detailed auxiliary fund expenditures (30), activity is categorized by the specified account level.
4-274
November 2010
Parameters
Name
Required?
Description
Values
Yes Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Date to select data for reporting. The ending date of the fiscal period that the As of Date occurs in will actually be used for selection. This date should fall within the specified start and end dates of the chart and fiscal year. Enter Y to include accrual for last period.
YY
Include Accrual for Last Prd Specific Fund
Yes
Y N
Yes (default) No
No
Specific fund for reporting. You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
Specific Fund Type
No
Level two fund type for reporting. You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
4-275
November 2010
Required?
Description
Values
Fund Level
No
1 (one) indicates that all funds in the ledger will roll up to their Level 1 Fund Code and will be reported that way. 2 (two) indicates that all level 3, 4, and 5 funds will be rolled up to their Level 2 Fund Code and will be reported that way. E indicates to report all funds as they exist in the ledger. You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
1, 2, or E
Fund Type Level
No
1 (one) indicates that all funds in the ledgers will roll up to their Level 1 Fund Type and will be reported that way. 2 (two) indicates all funds with a Level 2 Fund Type will be reported. You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
1 or 2
Account Level
Yes
Enter L to have all accounts in the ledger roll up to L or E their Level 1 Account Code and be reported that way. Enter E to report all accounts as they exist in the ledger. If the Account Level parameter is not specified, then the report will process level 1 accounts.
Note Although Specific Fund, Specific Fund Type, Fund Level, and Fund Type Level are optional parameters, only one of the parameters must be entered for the report to run. If you enter two or more of these parameters, the output will most likely be invalid. The report process uses the first parameter it finds to control the report run.
4-276
November 2010
Report Sample
06/03/96 09:55:49 FISCAL YEAR 96
Banner University Statement of Rev,Exp,Other Revenues, Expenditures, Other Changes AS OF 30-JUN-1996 Percentage of time through the Budget: 99.726
PAGE 1 FGRREOB
1000
Current Unrestricted Funds ADJUSTED BUDGET -------YEAR-TO-DATE ACTUAL -----------VARIANCE TO BUDGET ----------PERCENT OF BUDGET ----------
REVENUES: Indirect Cost Federal Grants Federal Direct Income - Grants Indirect Cost State Contracts TOTAL REVENUES: EXPENDITURES: Instruction Research Institutional Administration Independent Operations TOTAL EXPENDITURES:
.00 .00 .00 ----------------.00
1,392.00 10,000.00 4,815.00 ----------------16,207.00
1,392.00 10,000.00 4,815.00 ----------------16,207.00
######## ######## ######## -------########
1,014,511.53 .00 .00 .00 ----------------1,014,511.53
144,257.18 -154,868.00 .00 1,070.00 -----------------9,540.82
-870,254.35 -154,868.00 .00 1,070.00 -----------------1,024,052.35
-85.781 ######## .000 ######## -------########
NET INCREASE/DECREASE IN FUND BALANCE
-1,014,511.53
25,747.82
1,040,259.35
########
4-277
November 2010
Statement of Revenues, Expenditures, Other Changes (FGRREOC)

Description
This report compares actual activity for revenues and expenditures to the budgeted activity in the prior fiscal year. Included are calculations for total revenues, total expenditures, and change in fund balance (net increase/decrease).
Note Current year records with an Uncommitted Commit Type are retrieved for this report.
Revenue is sorted by the specified level of account codes. Expenditures are sorted by level 1 program codes. Expenditures are sorted by level 1 program codes. However, expenditures and transfers for the auxiliary funds (internal fund type of 30) are sorted by the specified level account codes. The different display of expenditures for auxiliary funds is based upon the assumption that expenses are entered with auxiliary program codes. These program codes may roll up to the same level 1 program code. Therefore, in order to display detailed auxiliary fund expenditures (30), activity is categorized by the specified account level.
4-278
November 2010
Parameters
Name
Required?
Description
Values
Yes Yes Yes
Fiscal year for reporting. Chart of accounts for reporting. Date to select data for reporting. The ending date of the fiscal period that the as of date occurs in will actually be used for selection. This date should fall within the specified start and end dates of the chart and fiscal year. Enter Y to include accrual for last period.
YY
DD-MON-YYYY Default current date
Include Accrual for Last Prd Specific Fund
Yes
Y N
Yes (default) No
No
Specific fund for reporting. Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
Specific Fund Type
No
Level two fund type for reporting. Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
4-279
November 2010
Required?
Description
Values
Fund Level
No
1 (one) indicates that all funds in the ledger will roll up to their Level 1 Fund Code and will be reported that way. 2 (two) indicates that all level 3, 4 and 5 funds will be rolled up to their Level 2 Fund Code and will be reported that way. E indicates that you want to report all funds as they exist in the ledger. Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
1, 2, 3, 4, 5, or E
Fund Type Level
No
1 (one) indicates that all funds in the ledgers will roll up to their Level 1 Fund Type and will be reported that way. 2 (two) indicates all funds with a Level 2 Fund Type will be reported. Note: You may enter a value for only one of the following parameters for a given report run: Specific Fund, Specific Fund Type (Ftyp), Fund Level, or Fund Type (Ftyp) Level.
1 or 2
Account Level
Yes
Enter L and accounts in the ledger will roll up to their L or E Level 1 Account Code and will be reported that way. Enter E to report all accounts as they exist in the ledger. If the Acct Level parameter is not specified, then the report will process level 1 accounts.
Note Although Specific Fund, Specific Fund Type, Fund Level, and Fund Type Level are optional parameters, only one of the parameters must be entered for the report to run. If you enter two or more of these parameters, the output will most likely be invalid. The report process uses the first parameter it finds to control the report run.
4-280
November 2010
Report Sample
06/03/1996 09:58:26 FISCAL YEAR 96
Banner University Statement of Revenues, Expenditures, Other Changes AS OF 30-JUN-1996
PAGE 1 FGRREOC
1000
Current Unrestricted Funds CURRENT YEAR 30-JUN-1996 --------PRIOR YEAR 30-JUN-1995 --------******** COMPARISON ******* CURRENT TO PRIOR PERCENT ----------------------
REVENUES: Indirect Cost Federal Grants Federal Direct Income - Grants Indirect Cost State Contracts TOTAL REVENUES: EXPENDITURES: Instruction Research Institutional Administration Independent Operations TOTAL EXPENDITURES:
1,392.00 10,000.00 4,815.00 ----------------16,207.00
.00 .00 .00 ----------------.00
1,392.00 10,000.00 4,815.00 ----------------16,207.00
######## ######## ######## -------########
144,257.18 -154,868.00 .00 1,070.00 -----------------9,540.82
.00 .00 .00 .00 ----------------.00
144,257.18 -154,868.00 .00 1,070.00 -----------------9,540.82
######## ######## .000 ######## -------########
NET INCREASE/DECREASE IN FUND BALANCE
25,747.82
.00
25,747.82
########
4-281
November 2010
Statement of Taxes and Rebates Report (FGRTAXR)

Description
This reports prints tax and rebate information related to invoices and direct cash receipts. This report has three modes: Summary, Detail, and Both. The Summary mode and Both mode have two sort options: Fund Type and Fund. The Fund Type and Fund sort options print one line for each tax rate code within that Fund Type or Fund and print a total line for each Fund Type or Fund. The Detail mode has six sort options: Fund Type, Fund, Organization, Account, Program, and Document. The Detail mode prints the Fund, Organization, Account, Program, and the document information, including Cancel and Credit Memo indicators. When you select Both as the report mode, a summary report followed by a detail report will be printed. All the sort options except for the Document option have the following values: (A)All, (R)Range, and (S)Specific.
Parameters
Name
Required?
Description
Values
Report Begin Date
Yes
Beginning date for reporting.
Report End Date
Yes
Ending date for reporting.
Chart of Accounts Tax Group Code
Yes No
You may only enter one Chart of Accounts code. One or more specific tax group code(s) or all tax group codes. After you enter a tax group code and press Enter, the system will prompt you to enter another tax group code. If you do not want to enter another tax group code, do not enter another tax group code and press Enter. Enter S to produce a report in Summary mode only, enter D to produce a report in Detail mode only, or enter B to produce a report for Both modes. Default = All tax groups
Report Mode
No
S D B
Summary (default) Detail Both
4-282
November 2010
Parameters (cont)
Name
Required?
Description
Values
Sort Option
Yes
Sort option.
T F O A P D
Fund type Fund Organization (detail mode only) Account (detail mode only) Program (detail mode only) Documents (detail mode only)
Note For the following parameters, only those that apply to the Report Mode and Sort Options you selected are presented if you run this report from the host.
Fund Type Option
No
You may select a specific fund type, a range of fund A types, or all fund types using this parameter. The From Fund Type and To Fund Type parameters are R required if you enter an R (Range) in this parameter. S
Note: If you run this report from the host, this parameter is presented only if you entered a T in the Sort Option parameter.
All (default) Range Specific
From Fund Type To Fund Type Specific Fund Type
No No No
Beginning fund type in this parameter if you entered an R (Range) in the Fund Type Option parameter. Ending fund type in this parameter if you entered an R (Range) in the Fund Type Option parameter. Specific fund type. You must have entered an S (Specific) in the Fund Type Option parameter. You may enter one or more fund types.
4-283
November 2010
Parameters (cont)
Name
Required?
Description
Values
Fund Option
No
You may select a specific fund, a range of funds, or all funds using this parameter. The From Fund and To Fund parameters are required if you enter an R (Range) in this parameter.
Note: If you run this report from the host, this parameter is presented only if you entered an F in the Sort Option parameter.
A R S
From Fund To Fund Specific Fund
No No No
Beginning fund in this parameter if you entered an R (Range) in the Fund Option parameter. Ending fund in this parameter if you entered an R (Range) in the Fund Option parameter. Specific fund in this parameter if you entered an S (Specific) in the Fund Option parameter. You may enter one or more funds. You may select a specific organization, a range of organizations, or all organizations using this parameter. The From Orgn and To Orgn parameters are required if you enter an R (Range) in this parameter. Note: If you run this report from the host, this parameter is presented only if you entered an O in the Sort Option parameter. A R S All (default) Range Specific
Orgn Option (Detail Only) (Organization)
No
From Orgn
No
Beginning organization for this parameter if you entered an R (Range) in the Organization Option parameter. Ending organization for this parameter if you entered an R (Range) in the Organization Option parameter.
To Orgn
No
4-284
November 2010
Parameters (cont)
Name
Required?
Description
Values
Specific Orgn
No
Specific organization in this parameter if you entered an S (Specific) in the Organization Option parameter. You may enter one or more organizations. You may select a specific account, a range of accounts, or all accounts using this parameter. The From Acct and To Acct parameters are required if you enter an R (Range) in this parameter.
Note: If you run this report from the host, this parameter is presented only if you entered an A in the Sort Option parameter.
Account Option (Detail Only)
No
A R S
From Acct To Acct Specific Acct
No No No
Beginning account for this parameter if you entered an R (Range) in the Account Option parameter. Ending account for this parameter if you entered an R (Range) in the Account Option parameter. Specific account in this parameter if you entered an S (Specific) in the Account Option parameter. You may enter one or more accounts. You may select a specific program, a range of programs, or all programs using this parameter. The From Prog and To Prog parameters are required if you enter an R (Range) in this parameter.
Note: If you run this report from the host, this parameter is presented only if you entered a P in the Sort Option parameter.
Prog Option (Detail Only) (Program)
No
A R S
From Prog To Prog
No No
Beginning program for this parameter if you entered an R (Range) in the Program Option parameter. Ending account for this parameter if you entered an R (Range) in the Program Option parameter.
4-285
November 2010
Parameters (cont)
Name
Required?
Description
Values
Specific Prog
No
Specific program in this parameter if you entered an S (Specific) in the Program Option parameter. You may enter one or more programs. This parameter allows you to sort all documents by document number.
Note: If you run this report from the host, this parameter is presented only if you entered a D in the Sort Option parameter.
Document Option (Detail Only)
No
Default = A (All)
PAGE 1 FGRTAXR 2.1.11
Banner Development Environment Statement Of Taxes and Rebates Summary Information - Invoices 01-NOV-1996 To 14-NOV-1996 Tax Group: ABG1 ABGST Tax Group 1
UN DATE 11/14/1996 RUN TIME 09:49 PM
COAS: B Fund Code ---- ---AB1000 AB1 AB1000 AB2 Fund Code
Tax Rate --- ----
Tax Amount --- -----11.25 22.74
Rebate Amount ------ -----.12 11.37 11.49 11.49
AB1000 Total
33.99 33.99
Tax Group ABG1 Total
4-286
November 2010
PAGE 1 FGRTAXR 2.1.11
Banner Development Environment Statement Of Taxes and Rebates Detail Information - Invoices 01-NOV-1996 To 05-NOV-1996 Tax Group: ABG1 ABGST Tax Group 1
RUN DATE 11/15/1996 RUN TIME 12:38 AM
COAS: B Fund : AB1000 Fund AB1000 Orgn 11003
Acct ABGST Seq# ---1 1
Prog ABGST Commodity --------1000000000 1000000000 Trt --AB1 AB2 Pr -2 3 Tax % --- 1.00 2.00 Total Total Tax Amount --- -----3.75 7.58 11.33 11.33 Rebt% ----1.00 50.00 Rebate Amount ------ -----.04 3.79 3.83 3.83 Can --N N C/M --N N
Document# --------ABGSTI22 ABGSTI22 Fund AB1000
Item ---0 0
Tax Group ABG1
4-287
November 2010
Trial Balance Report (FGRTBAL)

Description
This report prints a trial balance for all funds, a range of funds, or specific funds within a chart of account and fiscal year. Account codes for each fund are sorted in ascending order. Two balance columns are printed for each line on the report: one for the current period and one for the prior period. The current period is the As of Date and the prior period is one year less than the current period. Account balance (either debit or credit) is indicated to the right of each balance amount. For each fund in the general ledger, a total is printed for each low level account type followed by the predecessor account code total. After all account types have been printed and totaled, a Liabilities and Fund Balance total is printed which includes all account code balance amounts except those with an internal account type of ten. A grand total is printed at the end of the report for all fund codes. When the Include Accrual for Last Period parameter is Y (Yes), the report includes account balances posted to the accrual period. When this parameter is Y (Yes), the As of Date must be equal to the last period of the fiscal year.
Parameters
Name
Required?
Description
Values
Fiscal Year Chart of Accounts As of Date (DD-MON-YYYY) Include Accrual for Last Prd. Fund Option
Yes Yes Yes
YY
Yes
Y N
Yes No (default) All funds (default) Range of funds Wildcard funds Specific fund
Yes
Fund options include: A, R, W, or S
A R W S
4-288
November 2010
Required?
Description
Values
No No No
Beginning fund code of a range. This parameter is only required if the Fund Option = R. Ending fund code of a range. This parameter is only required if the Fund Option = R. Fund code. This parameter is only required if the Fund Option = S or W.
4-289
November 2010
02-SEP-1996 09:20:34 FISCAL YEAR 96 COAS: FUND: A 1000 Financial Ledgers Current Unrestricted
Banner University Trial Balance AS OF 30-JUN-1996
PAGE 1 FGRTBAL
ACCOUNT 1000 1001 1010 1020 1040 1050 1060 1090 1110 1130 1201 1210 2020 4020 TOTAL: 1831 1832 TOTAL:
Current Assets TITLE Cash Accounts Operating Cash-CU Operating Cash Account Payroll Cash Account Operating Cash Account Canadian Dollars Cash Account Payroll Clearing for Payroll Cash Interfund Account Student Accounts Receivable Federal Grants Receivable Due To/From Other Funds Cash Interfund Account Cash I/F-CU Investment I/F-CU Current Assets Equipment - Chairs Equipment - Desks Fixed Assets TOTAL Current Assets
******************* CURRENT AS OF 30-JUN-1996 82,723.23 155.52 100.00 250.00 250.00 1.22 1,010,067.02 105,406.70 6,336.20 371.25 147,478.05 386,631.67 11,000.00 1,500.00 C D D C D C D D D D D C C D
BALANCE ******************* PRIOR AS OF 01-JUL-1995 .00 .00 .00 50.00 50.00 .00 20.00 265.00 667.24 83.25 29,587.52 76,596.09 2,200.00 300.00 D D D C D D C D D D D C C D
791,058.62 D .00 D 500.00 D 500.00 D 791,558.62 D
47,913.08 C .00 D .00 D .00 D 47,913.08 C
*************** PAGE 1 CONTINUED ***************
4-290
November 2010
*************** CONTINUED FROM PREVIOUS PAGE *************** Liabilities TITLE Accounts Payable - Operations Student Refunds Payable Accounts Payable - Grants Payroll Clearing Account PA Use Tax Philadelphia Use Tax Goods & Service Tax Exemption Liab Accounts Payable Accounts TOTAL Liabilities 979,781.92 9,719.65 10.00 500.00 1,849.19 286.80 70,210.43 C D C D C C C 6,106.70 1,943.93 .00 100.00 226.80 37.80 .00 D D C D C C C
ACCOUNT 2100 2140 2150 2250 2501 2502 2510 TOTAL:
1,041,918.69 C 1,041,918.69 C
7,886.03 D 7,886.03 D
4-291
November 2010
02-SEP-1996 09:20:34 FISCAL YEAR 96 COAS: FUND: A 1000 Financial Ledgers Current Unrestricted
Banner University Trial Balance AS OF 30-JUN-1996
PAGE 2 FGRTBAL
ACCOUNT ACCOUNT 3010 3020 3040 3050 3060 3061 3070 3080 3099 TOTAL:
Ledger Control Accounts TITLE Ledger Control Accounts TITLE Revenue Control Account Expenditure Control Account Encumbrance Control Account Encumbrance Reserve Account Budgeted Revenue Control Account Adj. to Budgeted Rev. Control Budgeted Expenditure Control Acct Budgeted Transfer Control Account Budgeted Change to Fund Balance Control Accounts TOTAL Ledger Control Accounts
******************* CURRENT AS OF 30-JUN-1996
BALANCE ******************* PRIOR AS OF 01-JUL-1995
105,467.45 92,871.14 322,969.74 322,969.74 5,044.44 22.22 94,170.32 271.80 98,965.18
C D D C D D D C 0
44,007.01 100,494.06 101,418.09 101,418.09 .00 .00 6,507,700.00 .00 6,507,700.00
C D D C D D C D 0
12,596.31 C 12,596.31 C
56,487.05 D 56,487.05 D
ACCOUNT 3510 TOTAL:
Fund Balance Accounts TITLE Fund Balance Fund Balance Accounts TOTAL Fund Balance Accounts General & Administrative Expense 192,745.95 D 192,745.95 D 192,745.95 D 16,460.00 C 16,460.00 C 16,460.00 C
*************** PAGE 2 CONTINUED ***************
4-292
November 2010
*************** CONTINUED FROM PREVIOUS PAGE *************** ACCOUNT 6111 TOTAL: TITLE Office Supply Accounts General Expense 70,210.43 D 70,210.43 D .00 D .00 D
TOTAL General & Administrative Expense TOTAL LIABILITIES & FUND BALANCE: GRAND TOTAL:
70,210.43 D 509,123.37 C .00
.00 D 47,914.08 D .00
4-293
November 2010
Trial Balance Exception Report (FGRTBEX)

Description
This report was designed to analyze all funds for potential out of balance conditions. FGRTBEX can be run in either summary or detail mode. When this report is run in summary mode, it displays any out of balance funds for each chart of accounts. If there are no out of balance funds, a report saying that all funds are balanced displays. In detail mode, the report provides a list of all documents that are associated with that out of balance fund. This report is not designed to be used in conjunction with summarized postings.
Parameters
Name
Required?
Description
Values
Fiscal Year As of Date
Yes No
Fiscal year for reporting. Date to select data for reporting. The ending date of the fiscal period that the As of Date occurs in will actually be used for selection. If null, the As of Date defaults to the system date. This date should fall within the specified start and end dates of the chart and fiscal year. Enter Y to include accrual period.
YY DD-MON-YYYY
No
Y N
Yes No Summary mode Detail mode
Report Type
No
Report mode.
S D
Chart of Accounts Fund Option
No No
Chart of accounts for reporting. Leave blank to report on all charts of accounts in the general ledger. Fund option. A R S W All funds Range of funds Specific fund Wildcard funds
4-294
November 2010
Required?
Description
Values
No No No
Fund code for the beginning range of funds to be reported. Fund code for the ending range of funds to be reported. Fund code for a specific fund to be reported.
Report Sample
23-AUG-1996 10:33:16 FISCAL YEAR 96
Banner University Trial Balance Exception Report AS OF 31-AUG-1996 List of out of balance Funds
PAGE 1 FGRTBEX
COAS: A Fund: ----1000 2211 2422
Systems and Computer Technology Fund Title ---------Current Unrestricted Fund NSF- Everglades Erosion NIH- Lung Cancer Research Balance -------1,676.29 C 60.00 D 15.00 D -----------1,601.29 C -----------
Total balance for Chart of Accounts A is :
4-295
November 2010
Due To/Due From Control Report (FGRTOFR)

Description
The Due To/Due From Control Report displays fund number and description, due from balance and due to balance, and the difference between the balances for all chart of accounts and fiscal years with an entry in the general ledger which satisfies the parameter selection. Information displayed on the report is acquired by retrieving the Interfund Due/To Account and Interfund Due/ From Account Codes from the Chart of Accounts Table (FTVCOAS). Balances are obtained for every entry posted to an Interfund Due To/Due From Account Code in the general ledger. Balances are calculated by subtracting the summary of all debit entries from all credit entries in the general ledger for each Interfund Due Account Code. The Difference column is calculated by subtracting the Due From Balance from the Due To Balance for each Interfund Account Code. A total for all funds is displayed for each chart of accounts and fiscal year matching the parameter selection criteria.
Parameters
Name
Required?
Description
Values
Chart of Accounts Fiscal Year
No No
Chart of accounts for reporting. Leave blank to report on all charts of accounts in the general ledger. Fiscal year for reporting. Leave blank to report on all fiscal years in the general ledger. YY
4-296
November 2010
Report Sample
REPORT FGRTOFR COAS: G FISCAL YEAR: 91 FUND NUMBER ----------101000 101010 201000 201010 201020 201030 201040 201050 201060 201070 301000 401000 501000 601000 701000 801000 802000 803000 804000 805000 901000 902000 FUND NAME ---------
Banner University Due To/Due From Control Report DUE FROM BALANCE 1120 ---------------25,430.00 .00 .00 .00 .00 .00 .00 .00 .00 .00 3,400.00 .00 .00 400.00 1,250.00 .00 .00 .00 .00 .00 .00 .00 DUE TO BALANCE 2120 -------------<9,250.00> .00 .00 <2,150.00> <700.00> .00 .00 .00 .00 .00 <3,800.00> <2,850.00> <3,550.00> <13,287.00> <2,550.00> .00 .00 .00 .00 .00 .00 .00 DIFFERENCE ---------16,180.00 .00 .00 <2,150.00> <700.00> .00 .00 .00 .00 .00 <400.00> <2,850.00> <3,550.00> <12,887.00> <1,300.00> .00 .00 .00 .00 .00 .00 .00
General Fund Bank Fund Unrestricted Fund Motor Vehicle Expense Fuels Tax Parking Lot Revenues Financial Grants Mgt Day Care Facility Income State Grants Federal Grants Capital Projects Fund Capital Campaign - Alumni Capital Campaign - Fund Raising Financial Cost Studies Research Proposals Systems Development Operations and Maintenance Grounds Maintenance - Landscape Grounds Maintenance - Athletic Building Interdepartmental Funds General Fixed Assets General Long-Term Debt
-------------------------------------------------------------------------------------------------------------TOTALS 30,480.00 <38,137.00> <7,657.00>
4-297
November 2010
Daily Transaction Control Report (FGRTRNH)

Description
This report displays the daily transaction information (i.e., transaction history) by order of the activity date, document type, and document number from the date which is entered in the From Date and To Date parameters. Parameters are provided to select a range of fund, organization, account, activity, and location codes. To select a specific code type, enter that code in both the To and From parameters.
Parameters
Name
Required?
Description
Values
From Date (DD-MON-YYYY) To Date (DD-MON-YYYY) Document Type From Fund Code To Fund Code
Yes Yes No No No
Beginning date of transactions to be reported. Ending date of transactions to be reported. Document type for which you want to report. Fund code for the beginning range of funds to be reported. Fund code for the ending range of funds to be reported. Organization code for the beginning range of organizations to be reported. Organization code for the ending range of organizations to be reported. Account code for the beginning range of accounts to be reported. Account code for the ending range of accounts to be reported. Program code for the beginning range of programs to be reported.
DD-MON-YYYY DD-MON-YYYY
From Organization Code No To Organization Code From Account Code To Account Code From Program Code No No No No
4-298
November 2010
Parameters (cont)
Name
Required?
Description
Values
To Program Code From Activity Code To Activity Code From Location Code To Location Code
No No No No No
Program code for the ending range of programs to be reported. Activity code for the beginning range of activities to be reported. Activity code for the ending range of activities to be reported. Location code for the beginning range of locations to be reported. Location code for the ending range of locations to be reported.
4-299
November 2010
Report Sample
REPORT FGRTRNH
Banner University Daily Transaction Control Rep Original Entry Listing From 01-DEC-1995 TO 16-DEC-1995
ACTIVITY DATE 02-DEC-1995 DOC TYPE INV DOCUMENT DESCRIPTION Invoice RULE CODE INNI ITEM 1 DOC SEQ 3 SEQ NUM 1 SERIAL 1 DOC REFERENCE TRNS DATE 02-DEC-1995 PROJECT BANK A1 DEPOSIT POST PRD 06 AUTO JV SUBMISSION REV N
DOCUMENT I0000646
********************** ENCUMBRANCE DATA *********************** NUMBER ITEM SEQ ACTION TYPE CMT TYPE CMT PCT DISP 1 U CHART A ACCI FUND 2211 ORGN 210 ACCT 6155 PROG 210 ACTY
BUDG PRD
BUDG OVRD Y SIGN +
ACCRL IND
LOCN 1121
TRANSACTION AMOUNT CURRENCY 165.00
VENDOR/DESCRIPTION Discount PC's
USER IDENTIFICATION FIMSUSR
DOCUMENT I0000646
RULE CODE TAXL
ITEM 1
DOC SEQ 3
SEQ NUM 1
SERIAL 2
DOC REFERENCE
TRNS DATE 02-DEC-1995 PROJECT
BANK A1 DEPOSIT
POST PRD 06
AUTO JV
SUBMISSION
REV N
********************** ENCUMBRANCE DATA *********************** NUMBER ITEM SEQ ACTION TYPE CMT TYPE CMT PCT DISP 1 U CHART A ACCI FUND 2211 ORGN 210 ACCT 6155 PROG 210 ACTY
BUDG PRD
BUDG OVRD Y SIGN +
ACCRL IND
LOCN 1121
TRANSACTION AMOUNT CURRENCY 4.50
VENDOR/DESCRIPTION Computer Software
USER IDENTIFICATION FIMSUSR
4-300
November 2010
Transaction Interface Process (FGRTRNI)

Description
The Transaction Interface Process is used to edit the following: Documents interfaced from other systems. If the record type (rec_type) for a document is equal to 1, this process moves the document from the FGBTRNI table to the FGBJVCH table. If the record type is set to 2, this process moves the document from FGBTRNI table to the FGBJVCD table. This process also moves text from GURTEXT table to the FOBTEXT table. Documents completed in Defer Edit Automatic Journal Vouchers
Note If a client has Rule Class Security turned on, and then uses deferred editing of journals, the person who creates a deferred journal voucher must be authorized to use the rule classes with FGAJVCD. This is true whether the deferred journal is entered on FGAJVCD, FGAJVCQ, or FGAJVCM.
It is recommended that this process be run in background or sleep/wake-up mode. For additional information on sleep/wake-up mode, refer to the Reports and Processes chapter in the Banner Finance TRM Supplement. Refer to the report sample provided with the Transaction Error Report (FGRTRNR) on page 4-302.
4-301
November 2010
Transaction Error Report (FGRTRNR)

Description
This report prints the errors which have been generated from the Transactions Interface Process (FGRTRNI). FGRTRNR should be executed each time FGRTRNI is executed to obtain a list of all transactions which have been suspended due to edit errors. The Report Control Information page contains the record count identifying the number of errors that were encountered.
Report Sample
22-OCT-1996 15:20:56
Banner University Transaction Error Report AS OF 22-OCT-1996
PAGE 1 FGRTRNR
USER IDENTIFICATION FIMSMNT RULE CLASS RH05 COA T ACCI FUND 2900 ORGN 210
DOC DOCUMENT TYPE NUMBER 20 J0000774 ACCT 6160 PROG 330 ACTV 60
SUBM ITEM NUM NUM 0 LOCN 01
SEQ TRANSACTION NUM DATE 1 21-OCT-1996 NUM
TRANSACTION AMOUNT 75.00
TRANSACTION DESCRIPTION test new 0003 code VENDOR ONE-TIME VENDOR BANK T1 PROJECT
DR/CR IND +
ENCUMBRANCE ITEM SEQ TYPE
ACTION IND
DEPOSIT NUMBER
ID
BUDGET BUDGET PHASE DURATION PERIOD DISPOSITION
COMMITMENT TYPE PCT U
ACCRUAL DOCUMENT IND REF NUM
AVAILABLE BALANCE OVERRIDE Y EDIT CODE 0003
REVERSAL POOL POOL IND CoA FUND
ERROR MESSAGE Field does not satisfy specified condition.
FIELD NAME LOCN_CODE
TITLE
4-302
November 2010
Approval Process (FORAPPL)

Description
The Approval Process interrogates the records in the Unapproved Documents Table (FOBUAPP) against queue and routing information that you have already defined. This process determines all the levels required for final approval and inserts a record for each level in the Approvals In Process Table (FOBAINP). As documents are approved, values are updated to the Approval History Table. When final approval is performed, the document is inserted into the Approval Document Table (FOBAPPD). To use the Approval Process, appropriate approval queues and routings must be established. The Approval Override Indicator on the System Control Maintenance Form (FOASYSC) must be set to N or I for the Document Types that you wish to use with Approvals. For more information on approval processing, refer to Chapter 2, Processing. It is recommended that this process be run in background or sleep/wake-up mode. For additional information on sleep/wake-up mode, refer to the Reports and Processes chapter in the Banner Finance TRM Supplement.
Output Sample
Starting document E0000399 Starting document I0007202 Starting document P0004920 Starting document P0004996 Unable to locate an appropriate item number : : sequence number Unable to locate an appropriate item number : : sequence number Starting document P0004997 Unable to locate an appropriate item number : : sequence number Unable to locate an appropriate item number : : sequence number Starting document P0005320 Starting document P0005183 Starting document I0007897
document document document document queue id. : 1 : queue id. : 2 : document queue id. : 1 : queue id. : 2 : document document document
type number 25 change sequence type number 3 change sequence type number 2 change sequence type number 2 change sequence Approval process aborted. Approval process aborted.
number number number 3 number 1
submission submission submission submission
number number 0 number number
type number 2 change sequence number 2 Approval process aborted. Approval process aborted. type number 2 type number 2 type number 3 change sequence number change sequence number change sequence number
submission number
submission number submission number submission number 0
4-303
November 2010
Purchasing and Procurement Module

This section describes each report in the Purchasing and Procurement module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
Note For information about eProcurement, refer to the Finance eProcurement for HigherMarkets Banner Handbook.
4-304
November 2010
Bid Form Print (FPABIDD)

Description
This report prints either a specific bid or all of the bids which were approved but never printed. Output will vary based on your pre-printed form requirements.
Parameters
Name
Required?
Description
Values
Bid Number
No
Specific bid number that you wish to print or leave the parameter blank to print all bids that have never been printed. The Print Indicator is null on the Bid Header Information Table (FPBBIDH) if this bid has never been printed.
4-305
November 2010
Change Order Form Print (FPACORD)

Description
This report contains a specific purchase order that has change orders associated with it. It may also contain all of the change orders that have been completed, approved, and posted without being printed. FPACORD prints individual tax amounts by commodity on the change order. This report contains three sections: Previous Order Change Revised Order This information is not required for an original or unchanged purchase order. These items pertain to change orders only. FPACORD processing begins by prompting you to enter a specific purchase order number that has change orders associated with it or by running through all of the change orders that are completed, approved, posted, and have not yet been printed. In the case where you enter a specific PO, you are prompted to enter a specific change order sequence number within the sequence of change orders that may exist for that PO (for example, #3 of 6) or you may leave it blank to print all unprinted change orders for referenced purchase orders. When both parameters have been supplied, the change order prints again regardless of whether it has been previously printed. Changes are reported in two ways due to the nature of the data. The following items are treated as header changes: Vendor address Date required Ship-To address Payment terms Buyer name FOB (Freight On Board) Point Ship via PO header text
4-306
November 2010
The current values for these fields are printed on the form. If any of these items have changed with this change order, the changes are noted in the COMMODITY DESCRIPTION area with a short message. Following is an example: LIST OF HEADER CHANGES SHIP-TO ADDRESS CHANGE BUYER NAME CHANGE Processing continues with the individual items on this change order. If the item has been skipped over for this change, FPACORD prints the item number and a message, as follows, and then continues with the next item: 1 THIS ITEM WAS NOT ON THIS CHANGE ORDER PREVIOUS ORDER In the case where an item was changed on this change order, FPACORD compiles the items previous history and prints a previous order line. (Spacing is compressed here for presentation purposes.)
ITEM
PREVIOUS ORDER
AST386
AST 386 PC
1.00 EA
2,000.0000
2,000.00
Any commodity text, line item text, agreement number, or part number that exists with this item also prints here. CHANGE If the item was newly added as part of this change order, it is reported as follows (rather than in the PREVIOUS ORDER line from previous page): THIS ITEM (# 5 ) IS NEW WITH THIS ORDER The individual item changes supported are: Quantity Unit of measure
4-307
November 2010
Unit price Extended amount Discount Additional charge Tax Line item text FPACORD evaluates the value in each of these fields for the current item and prints a descriptive message and the particular value when that value is not zero as follows. (Spacing is compressed here for presentation purposes):
Change:
Quantity Increase 2.00 Unit of Measure Unit Price Increase Extended Amount Increase Discount Increase Tax Decrease
EA 100.00 4,300.00 430.00 -180.00
The Extended Amount Increase field is 4,300.00 because we started by ordering 1 PC for 2000.00 and ended by ordering three (1 previous + 2 quantity increase), both at the increased price of:
2100.00 (2000.00 previous + 100.00 unit price increase) for a new Extended Amount of 6300.00, such that: 6300.00 - 2000.00 = 4300.00. The discount shown here is stored as 10% of the change listed above in Extended Amount, which is 430.00. Previously assessed taxes have been rescinded by this order, so tax shows as an overall decrease of 180.00. The Additional Charge field was 0.0, and no line is printed for it. The change total for this item is printed next:
CHANGE TOTAL:
* 3,690.00 *
The asterisks surround the value indicating that this value contributed to the Net Change for the whole document.
4-308
Banner Finance 8.5 User Guide Reports and Processes November 2010
REVISED ORDER Item processing concludes by printing the REVISED ORDER where the changed Quantity, Unit Price, and Extended Amount Increase fields all have been added to previous values to arrive at the revised values of those fields. In the case of a change in Unit of Measure, the changed value is printed.
ITEM 1
REVISED ORDER AST386
AST 386 PC
3.00 EA
2,100.0000
6,300.00
As with the PREVIOUS ORDER, any commodity text, line item text, agreement number, and part number that exists with this item also prints here. After all items are processed, FPACORD prints the following summary totals for the document:
CHANGE IN DISCOUNT: CHANGE IN ADDL CHARGES: CHANGE IN TOTAL TAXES: NET CHANGE: Error Condition Handling
434.60 0.00 -186.75 3,724.65
FPACORD makes several checks on the input parameters supplied to it before executing. When the change order number has been specified, a check is performed to assure that at least one change order with that value which has been completed, approved, and posted exists for further processing. Otherwise, it terminates with the message: At least one completed, approved, and posted change order with that value must exist prior to running this job, aborting job. Assuming that a value for a change order has been entered and passes the completed, approved, and posted requirements, a second parameter is requested. The second parameter allows you to specify a particular change sequence number for the change order. FPACORD makes a final check as to whether it is still in posting. If it is still in posting, FPACORD terminates with the message: That change order/sequence has not yet been posted, aborting job. FPACORD processes change orders that has been cancelled as unique and prints the following message: THIS CHANGE ORDER WAS CANCELLED ON DD-MON-YY
4-309
November 2010
FPACORD continues processing any remaining change orders. No totals will be printed for remaining change orders, but change orders will be flagged as printed and not be processed a second time.
Note If a foreign currency is used, the currency description prints on the change order. Output will vary based on your pre-printed form requirements.
Parameters
Name
Required?
Description
Values
Change Order Number
No
Specific purchase order change order number that you wish to print, or leave this parameter blank to print all change orders that have never been printed. Specific change sequence number for a specific purchase order change order that you wish to print, or leave this parameter blank to print all change orders that have never been printed. The Change Order Print Date is null in the Purchase Order Header Table (FPBPOHD) if the change order has never been printed. Type of purchase order to be printed if a specific document is not entered. 1, 2, 3...to 999
Change Order Sequence
No
Purchase Order Type
Yes
R S A
Regular Standing All (default) Yes No
Include E-Procurement POs?
No
Indicates if e-procurement purchase orders should be printed.
Y N
4-310
November 2010
Purchase Order Form Print (FPAPORD)

Description
This process can print either a specific Purchase Order or all of the Purchase Orders which have been approved but have never been printed as you may print all unprinted Purchase Orders based on the purchase order type. This process can also print blanket orders. FPAPORD prints individual tax amounts by commodity on the purchase order. Output will vary based on your pre-printed form requirements. All lines of the vendor or ship-to address print, if they exist. In addition, if address data in any line is blank, then all data beneath it will move up a line. The format of the address displays as follows:
Line #
Vendor Address
Ship-to Address
1 2 3 4 5 6 7 8
Vendor Code Ship Address Line 1 Vendor Name Vendor Address Line 1 Vendor Address Line 2 Vendor Address Line 3 Vendor City, State, Zip Vendor Nation Ship Address Line 2 Ship Address Line 3 Ship Building and Floor Ship City, State, Zip Ship Nation Ship Attention To
Note If you are using Finance e-Procurement with HigherMarkets, this process publishes an update message whenever a Purchase Order that originated from a HigherMarkets purchase order is printed. For detailed information, refer to the Finance eProcurement with HigherMarkets Banner Handbook.
4-311
November 2010
Parameters
Name
Required?
Description
Values
Purchase Order Number
No
Specific purchase order number that you wish to print, or leave this parameter blank to print all purchase orders that have never been printed. The Purchase Order Print Date is null in the Purchase Order Header Table (FPBPOHD) if the purchase order has never been printed. C (Current) is the default value for this parameter. The O (Original) order does not exist until the first change order is created. Type of purchase order to be printed if a specific document is not entered. C O R S B Current Original Regular Standing Both (default) Yes No
Status
No
Purchase Order Print Option
Yes
No
Indicates if eProcurement purchase orders should be printed.
Y N
4-312
November 2010
Requisition Form Print (FPARQST)

Description
Use this report to print a specific requisition by entering the requisition number. Leave the Requisition Number parameter blank to print all of the requisitions that have been approved but have never been printed. You may enter P (Procurement) or S (Stores) to print only procurement requisitions or only stores requisitions. If a foreign currency is used, the currency description prints on the requisition. Output varies based on your pre-printed form requirements.
Parameters
Name
Required?
Description
Values
Requisition Number
No
The Requisition Print Indicator is null in the Request Header Table (FPBREQH) if the requisition has never been printed. Indicates if eProcurement purchase orders should be printed. Y N Yes No
No
4-313
November 2010
PO Batch Close Process (FPPPOBC)

Description
Use this process to close purchase orders with encumbrance balances below a specified dollar threshold. The PO Batch Close Process produces a report that identifies all purchase orders that were closed. The selected documents are listed by document number, by vendor, and by FOAPAL string. The report also includes a list of documents that met the various selection criteria but could not be closed because of an error condition. The Purchase Order Batch Close Process creates document numbers that begin with an asterisk (*), and will generate multiple document numbers, as shown in the report sample. When you run this process in Audit mode (Report Mode = A), you can examine the report to verify the documents that will be closed and correct any error conditions. When you run this process in Update mode (Report Mode = U), Banner liquidates the encumbrance for the purchase orders and changes the status of the documents from open to closed. In Update mode, the PO Batch Close Process creates a document with a document prefix of * and a rule class of POBC - Purchase Order Batch Close. Banner then forwards this document to posting. You must run the Finance Posting Process (FGRACTG) to update the encumbrance and its related tables.
Note To identify purchase orders that were closed with the Purchase Order Batch Close Process (FPPPOBC), look for the POBC - Purchase Order Batch Close rule class.
Parameters
Name
Required?
Description
Values
Posting Date Purchase Order Activity Date
Yes Yes
Date on which Banner will post the encumbrance liquidation to the ledgers. Date used to select purchase orders for processing. Banner will select purchase orders with activity dates less than or equal to the date you enter in this parameter.
DD-MON-YYYY DD-MON-YYYY
4-314
November 2010
Parameters (cont)
Name
Required?
Description
Values
Purchase Order Select Option
Yes
Way in which you want to enter purchase orders.
A R W S
Automatically enter all applicable purchase orders. Enter a range of purchase orders. Search for specific purchase orders using a wildcard. Enter specific purchase orders.
From Purchase Order Number To Purchase Order Number PO Number or Wildcard Criteria
Yes Yes Yes
First purchase order in a series. Enter only if Purchase Order Selection Option = R. Last purchase order in a series. Enter only if Purchase Order Selection Option = R. Purchase order numbers that you would like to include in the PO Batch Close Process. Enter only if Purchase Order Selection Option = W or S. You may use a wildcard (%) if Purchase Order Selection Option = W. Encumbrance amount used to select purchase orders for processing. Banner will select purchase orders with encumbrance balances that are less than or equal to the value you enter in this parameter. Indicates whether you want the system to print a report and update database records, or print a report only. A U Audit mode. Print a report. (default) Update mode. Print a report and update database records.
Maximum Encumbrance Yes Amount
Report Mode
Yes
4-315
November 2010
FPPPOBC
Banner University Purchase Order Batch Close Process As of 30-JUN-2004 List of Encumbrance open/close document(s) created by the process
RUN DATE 02-NOV-2004 Run Time 10:19:45 PAGE 1
Open/Close Doc -------------*0000041 *0000042 *0000043 *0000044 *0000045 *0000046 *0000047 *0000048
Total Amount -----------91.26 318.72 227.30 184.50 166.00 311.77 149.00 13.65
FPPPOBC
Banner University Purchase Order Batch Close Process As of 30-JUN-2004 List of Purchase orders by vendors that will be closed by the process
Vendor V1 Open/Close Doc ------------------*0000041 *0000041 *0000041 *0000043 *0000043
Office Max Purchase Order# --------------P0000469 P0000472 P0000669 P0000490 P0000519
Transaction Date ---------------12-AUG-2003 15-AUG-2003 10-JUN-2003 08-OCT-2003 22-OCT-2003
Encumbrance Liquidated ----------------------3.82 11.46 49.00 7.64 18.00 -----------------------
4-316
November 2010
FPPPOBC
Banner University Purchase Order Batch Close Process As of 30-JUN-2004 List of Purchase orders not closed due to invalid accounting sequence
Purchase Order# --------------P0000463
FPPPOBC
Banner University Purchase Order Batch Close Process As of 30-JUN-2004 * * * REPORT CONTROL INFORMATION * * *
RPTNAME: VERSION: PARAMETER SEQUENCE NUMBER: POST DATE: PO ACTIVITY DATE: PURCHASE ORDER SELECTION OPTION: REPORT MODE: NUMBER OF LINES PRINTED PER PAGE:
FPPPOBC 6.1.0.1 118717 30-JUN-2004 11/02/2004 A A-AUDIT MODE 55
4-317
November 2010
Bid Evaluation Report (FPRBEVL)

Description
This report provides a summary of bid data for comparison of vendor unit pricing on a particular bid. FPRBEVL displays vendor, commodity description, quantity, unit price, extended price, and individual vendor and commodity totals.
Parameters
Name
Required?
Description
Values
Bid Number
No
Specific bid number that you wish to report on, or leave this parameter blank to print all bids based on the Awarded or Not Awarded parameter. Enter Y for awarded bid, or enter N for not awarded. Y N Yes No (default)
Awarded or Not Awarded
No
4-318
November 2010
Report Sample
REPORT FPRBEVL
Banner University Bid Evaluation Report
BID: B0000005 - Laboratory Equipment Purchases VENDOR COMMODITY NUMBER NAME CODE DESCRIPTION U/M QUANTITY UNIT PRICE EXTENDED PRICE --------- ------------------------------ ---------- ---------------------------- --- ---------- -------------- ---------------00001 Laboratory Supplies Inc. 55 Lab Tables EA 4977.00 73 Lab Stools EA 477.00 54 Glassware EA 999.00 27 Protective Gloves EA 102.00 86 Lab Table Shelves EA 227.00 15 Solvents and Solutions EA 310.00 03 Sinks EA 1000.00 Vendor 00002 Fischer Scientific. Total 55 73 54 27 86 15 03 Vendor Total Lab Tables EA Lab Stools EA Glassware EA Protective Gloves EA Lab Table Shelves EA Solvents and Solutions EA Sinks EA 1050.00 $6040.00 315.00 225.00 109.00 899.00 427.00 3015.00 $8092.00
4-319
November 2010
Delivery Log (FPRDELV)

Description
This report shows delivery and routing of goods received including: delivery date, address register, and description of goods received.
Parameters
Name
Required?
Description
Values
From Date To Date
Yes No
Beginning date for reporting. Ending date for reporting.
DD-MON-YYYY DD-MON-YYYY Default = Current date
Report Sample
REPORT FPRDELV
Banner University Delivery Log
Delivery Date: 04/17/1996 Route Code: RT66 Address: Main Storeroom Business Drive Main Storeroom First Floor Camden, NJ. 08101 REQUEST CODE NAME -------- ----------------------------------R90-017 Michael DiCroce R90-034 Michael DiCroce R90-049 Michael DiCroce COMMODITY CODE DESCRIPTION ---------- -------------------------------------------------CEPR2003 Epson FX 1050 Printer SLE00004 Graduated Cylinders SLEM0005 Metallurgical Microscopes
U/M QUANTITY --- ---------EA 1.00 EA 1.00 EA 3.00
4-320
November 2010
Open Purchase Orders Report (FPROPNP)

Description
FPROPNP is a hard copy report of open purchase orders as of a particular date and sorted by purchase order type and then purchase order number. If values are entered in the parameters that are not required, only open purchase orders corresponding to the parameters display. Otherwise, all open purchase orders for the purchase order type will display.
Parameters
Name
Required?
Description
Values
No
Open purchase order number. If specified, the report displays information about that particular open purchase order only. Leave blank to display all open purchase orders. If a vendor code is specified, the report displays information about purchase orders pertaining only to the specific vendor. Leave blank to display all open purchase orders. Type of purchase order to be printed if a specific document is not entered. R S B Regular Standing Both (default)
Vendor Code
No
Purchase Order Print Option
Yes
4-321
November 2010
REPORT FPROPNP
Banner University Open Purchase Orders Report BUYER CODE ---CE01 NAME ----------------------------------Mike Jones
P.O. NUMBER -------P0000012
VENDOR/PAYEE NUMBER NAME --------- -----------------------------00007 Computer Land
COMMODITY ORDERED ACCEPTED APPROVED ** ITEM CODE DESCRIPTION QUANTITY UNIT PRICE U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE ---- ---------- ----------------------------- ---------- -------------- --- ---------- ---------- -------------- ---------------1 CEPR2003 Epson FX 1050 Printer 4.00 $1,300.0000 EA .00 14.00 $1,300.0000 $18,200.00 EA .00 .00 $.0000 $.00 ---------------Total $18,200.00 P.O. NUMBER -------P0000640 VENDOR/PAYEE NUMBER NAME --------- -----------------------------00007 Computer Land BUYER CODE ---C001 NAME ----------------------------------Software Service - (C. Boyce)
COMMODITY ORDERED ITEM CODE DESCRIPTION QUANTITY UNIT PRICE ---- ---------- ----------------------------- ---------- -------------1 10110200 CHAIR, Standard Desk 5.00 $10.0000 2 Gateway 386 5.00 $2,000.0000 Total ******************* CONTINUED ON NEXT PAGE*******************
ACCEPTED APPROVED ** U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE --- ---------- ---------- -------------- ---------------EA EA .00 .00 5.00 5.00 $10.0000 $2,000.0000 $50.00 $10,000.00 ---------------$10,050.00
4-322
November 2010
******************* CONTINUED FROM PREVIOUS PAGE******************* P.O. NUMBER -------P91-005 VENDOR/PAYEE NUMBER NAME --------- -----------------------------00007 Computer Land BUYER CODE ---CE01 NAME ----------------------------------Mike Jones
COMMODITY ORDERED ACCEPTED APPROVED ** ITEM CODE DESCRIPTION QUANTITY UNIT PRICE U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE ---- ---------- ----------------------------- ---------- -------------- --- ---------- ---------- -------------- ---------------1 CEPR2003 Epson FX 1050 Printer 2.00 $1,100.0000 EA .00 2.00 $1,100.0000 $2,200.00 P.O. NUMBER -------P91-006 VENDOR/PAYEE NUMBER NAME --------- -----------------------------00007 Computer Land BUYER CODE ---CE01 NAME ----------------------------------Mike Jones ACCEPTED APPROVED ** U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE --- ---------- ---------- -------------- ---------------EA EA .00 .00 1.00 2.00 $1,000.0000 $1,350.0000 $1,000.00 $2,700.00 ---------------$3,700.00
COMMODITY ORDERED ITEM CODE DESCRIPTION QUANTITY UNIT PRICE ---- ---------- ----------------------------- ---------- -------------1 CEPC0003 PC Brand 386/20 3.00 $1,000.0000 2 CEPC1005 PC Brand 386/25 3.00 $1,350.0000 Total ** MAY INCLUDE INVOICES NOT YET APPROVED
4-323
November 2010
REPORT FPROPNP
Banner University Open Purchase Orders Report
P.O. NUMBER -------TSTA9164
BUYER CODE ---C001 NAME ----------------------------------Software Service - (C. Boyce) ACCEPTED APPROVED ** U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE --- ---------- ---------- -------------- ---------------BOX BOX BOX .00 .00 .00 2.00 2.00 .00 $6.0000 $8.0000 $.0000 $12.00 $16.00 $.00 ---------------$28.00
COMMODITY ORDERED ITEM CODE DESCRIPTION QUANTITY UNIT PRICE ---- ---------- ----------------------------- ---------- -------------1 books order with 1 unit 1.00 $6.0000 2 book order for 2 units 2.00 $8.0000 Total P.O. NUMBER -------TSTB9450 VENDOR/PAYEE NUMBER NAME --------- -----------------------------00007 Computer Land BUYER CODE ---C001
NAME ----------------------------------Software Service - (C. Boyce)
COMMODITY ORDERED ACCEPTED APPROVED ** ITEM CODE DESCRIPTION QUANTITY UNIT PRICE U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE ---- ---------- ----------------------------- ---------- -------------- --- ---------- ---------- -------------- ---------------1 User Manuals 20.00 $100.0000 BOX .00 20.00 $100.0000 $2,000.00 ** MAY INCLUDE INVOICES NOT YET APPROVED
4-324
November 2010
REPORT FPROPNP
Banner University Open Purchase Orders Report
P.O. NUMBER -------TSTF9450
BUYER CODE ---C001 NAME ----------------------------------Software Service - (C. Boyce)
COMMODITY ORDERED ACCEPTED APPROVED ** ITEM CODE DESCRIPTION QUANTITY UNIT PRICE U/M QUANTITY QUANTITY UNIT PRICE EXTENDED PRICE ---- ---------- ----------------------------- ---------- -------------- --- ---------- ---------- -------------- ---------------1 Installation Guides 2.00 $5.0000 BOX .00 1.00 $5.0000 $5.00 ================ $36,183.00
Vendor Total ** MAY INCLUDE INVOICES NOT YET APPROVED
4-325
November 2010
Open Requisitions Report (FPROPNR)

Description
The Open Requisitions Report may be used to display the status of requests for goods and services that are not fully satisfied. The open requests are displayed as of a particular date and sorted by requisition number. Only procurement requisitions print on this report. The Open Stores Requisitions Report (FSROPNR) prints the open stores requisitions. The system selects and prints procurement requests when the closed indicator on the Request Detail Table (FPRREQD) equals N for that requisition. All open requisitions will be displayed unless the optional parameters are used to sort the report by requisition number or organization.
Parameters
Name
Required?
Description
Values
As of Date DD-MON-YYYY Requisition Number
Yes
No
Specific requisition number that you wish to display. If a value is entered in this parameter, only this requisition displays if it is open. Leave blank to display all open requisitions. Organization code associated with the open requisition. If a value is entered in this parameter, only open requisitions within this organization will display. Leave blank to display all open requisitions.
Organization Code
No
4-326
November 2010
Report Sample
REPORT FPROPNR FISCAL YEAR 96 ORGANIZATION: Computer Department REQUEST NUMBER NAME -------- -----------------------------R0000021 Becki Northrop
Banner University Open Requisitions Report As of 10/05/1996
REQ DATE -------07/30/1996 QUANTITY U/M REQUESTED --- ---------EA 2.00 1.00 1.00 REQ TOTAL ORDERED QUANTITY UNIT PRICE ---------- -------------2.00 1.00 1.00 $4,000 $2,000 $3,000 EXTENDED PRICE ---------------$8,000 $2,000 PO#/BID# -------BIDCU BIDCU
COMMODITY ITEM CODE DESCRIPTION ---- ---------- -----------------------------------------1 CEPC1007 Acer 386/20 Computer 2 CEMT3002 3 CEPR2002 Magnavox 7BM749 Monochrome Monitor
EA Canon LBP-8 Mark III R Printer EA
$3,000 BIDCU ---------------$13,000.00
REQOON
Becki Northrop
12/31/91 QUANTITY U/M REQUESTED ---------- ---------EA 2.00 ORDERED QUANTITY UNIT PRICE ---------- -------------2.00 $20.0000 EXTENDED PRICE ---------------$40.00 ---------------$13,040.00 PO#/BID# -------REQ2POOO
COMMODITY ITEM CODE DESCRIPTION ---- ---------- ------------------------------ --1 22000000 SUPPLIES, Cleaning
ORG TOTAL
4-327
November 2010
Purchase Order Activity Report (FPRPURA)

Description
This report enables you to print detail and summary purchase order activity information for a specified period of time, vendor, or user. This report gathers the total amount of purchase orders processed by each individual during the specified time period, as well as the total amount of purchase orders processed on each day during the specified time period. This report does the following: Obtains a listing and total amount of all purchase orders during a specified time period Obtains a listing and total amount of all purchase orders for a particular vendor during a specified time period Obtains a listing and total amount of all purchase orders processed by a specific individual during a specified time period
Parameters
Name
Required?
Description
Values
From Activity Date
Yes
Beginning of a time period for which the purchase order activity information will be printed. This field is mandatory and may not be left blank.
DD-MON-YYYYY
To Activity Date
Yes
Ending of a time period for which the purchase order DD-MON-YYYYY activity information will be printed. This field is mandatory and may not be left blank. User identification code. Filling in this parameter will limit the report to one user. Vendor identification code. Filling in this parameter will limit the report to one vendor.
User ID Vendor ID
No No
4-328
November 2010
Report Sample
FPRPURA
3.0
Development Purchase Order Activity Report 23-OCT-1996 through 25-OCT-1996
08-NOV-1996
02:06:36 PAGE: 1
ACTIVITY USER ID DATE ______________ __________ FIMSUSR 10/23/1996
VENDOR NUMBER NAME __________ _____________________________ 00010 LAB Corporation
PURCHASE ORDER NUMBER DATE REQ DATE __________ __________ __________ PO1000 P0001015 10/23/1996 10/19/1996 10/23/1996 10/19/1996
PURCHASE ORDER AMOUNT CL ______________ __
C A _ _ N N N N
R/S/C _____
$100.00 $39.00 -------------TOTAL DATE $139.00 $1,080.00 -------------TOTAL DATE $1,080.00 $600.00 -------------TOTAL DATE $600.00 TOTAL USER -------------$1,819.00 N
10/24/1996
00010
LAB Corporation
P0001022
10/24/1996 10/25/1996
Y Y
10/25/1996
00010
LAB Corporation
PO10000
10/25/1996 10/26/1996
Y Y
4-329
November 2010
Receiving & Delivery Report (FPRRCDL)

Description
The Receiving/Delivery Report may be used to determine the status of received and delivered commodities versus ordered commodities. This report may display a specific purchase order's status. If a purchase order is not specified, it displays all purchase orders sorted by vendor. If a particular vendor is indicated, then all purchase orders pertaining to that vendor display. If no purchase order is specified, then a purchase order type may be specified.
Parameters
Name
Required?
Description
Values
No
Specific purchase order number that you wish to display. If a value is entered in this parameter, the report displays information about that purchase order only. Leave blank to display all purchase orders. Vendor number that you wish to display. If a value is entered in this parameter, the report displays information about purchase orders pertaining to that vendor only. Leave blank to display all purchase orders for all vendors. Type of purchase order to be printed if a specific document is not entered. R S A Regular Standing All (default)
Vendor Number
No
Purchase Order Type
Yes
4-330
November 2010
Report Sample
REPORT FPRRCDL
Banner University Receiving/Delivery Report
RUN DATE: 10/25/1996 RUN TIME: 03:47 PM PAGE: 1
VENDOR NUMBER NAME --------- -----------------------------00007 Computer Land P.O. NUMBER DATE -------- -------CS001 10/04/1996 COMMODITY ORDERED ITEM CODE DESCRIPTION DATE QUANTITY ---- ---------- ------------------------------- -------- ---------1 AST386 AST 386 PC with Hercules card and 4mg main memory. 1.00 RECEIVED REJECTED BALANCE DATE QUANTITY QUANTITY OF QTY DUE -------- ---------- ---------- ---------.00 .00 1.00
4-331
November 2010
PO Receiving Status Report (FPRRCST)

Description
This report lists purchase orders with packing slips for purchase orders that have never been invoiced. This report sorts by Vendor Name or Vendor Code, as specified by sort sequence parameter. The Receiver Document number, displayed under the DOCUMENT column, is obtained from the Packing Slip Header Table (FPBRCDT). If no purchase order document is indicated, you may run the report for only certain purchase order types.
Note If values for the Vendor Code and Purchase Order Number parameters are not entered, the report may take considerably longer to execute.
Parameters
Name
Required?
Description
Values
Vendor Code
No
Specific vendor number that you wish to display. If this parameter is valued, the report displays information about purchase orders pertaining to that vendor only. Leave blank to display all purchase orders for all vendors. Sort sequence option. 1 2 Sort by vendor name (default value) Sort by vendor code
Sort Sequence
No
No
Specific purchase order number that you wish to display. If this parameter is valued, the report displays information about that purchase order only. Leave blank to display all purchase orders. Type of purchase order to be printed if a specific document is not entered. R S A Regular (default) Standing All
Purchase Order Type
Yes
4-332
November 2010
Report Sample
FPRRCST 3.0
Banner University PO Receiving Status Report
20-OCT-1996 04:46 PM PAGE: 1
VENDOR NUMBER NAME --------- -----------------------------00006 Computer Warehouse ------------------- P.O. ----------------------- ------- RETURN --NUMBER DATE ITEM QTY UOM CLOSED CODE QUANTITY -------- ----------- ---- --------- --- ------ -------- --------HALP0300 01-OCT-1996 1 2.00 EA -----------------------DOCUMENT PACKING SLIP -------- --------------HALP0002 HALPACK001 HALP016L HALREC16L RECEIVING --------------------------DATE RECD QTY REC QTY REJ SUSP ----------- --------- --------- --28-SEP-1996 4.00 1.00 N 13-JAN-1996 10.00 4.00 N
4-333
November 2010
Vendor Products Catalog Report (FPRVCAT)

Description
The Vendor Products Catalog Report is used to identify vendors that provide a particular commodity based on the installation's purchasing history. The report is sorted by commodity and displays vendor numbers, names, and prices. The report can be sorted by vendor type(s), and/or commodity code. Vendor types are originally defined on the Vendor Type Code Maintenance Form (FTMVTYP). Commodity codes are originally defined on the Commodity Code Validation Form (FTVCOMM). Access FTVCOMM from the Commodity field of purchasing forms.
Parameters
Name
Required?
Description
Values
Vendor Type 1 Vendor Type 2 Vendor Type 3 Vendor Type 4 Vendor Type 5 Commodity Code
No No No No No No
First vendor type code. If specified, information for each vendor with this vendor type will display. Second vendor type code. If specified, information for each vendor with this vendor type will display. Third vendor type code. If specified, information for each vendor with this vendor type will display. Fourth vendor type code. If specified, information for each vendor with this vendor type will display. Fifth vendor type code. If specified, information for each vendor with this vendor type will display. If the commodity code is specified, only the vendors related to the particular commodity will display. If this parameter is left blank, vendors will display for all commodities. Date to select data for reporting. DD-MON-YYYY Default = Current date
As of Date
Yes
4-334
November 2010
Report Sample
REPORT FPRVCAT
Banner University Vendor Products Catalog As Of 10/31/1996
COMMODITY CODE DESCRIPTION ---------- -------------------------------------------------10000000 FURNITURE VENDOR CODE NAME VENDOR REF NO VENDOR TYPES --------- ------------------------------ --------------- -------------00001 Laboratory Supplies Inc. MN 00002 LAB Discount SB 00003 Mikelson's Supplies MN 00007 Computer Land SB 00010 National Supplies, Inc. MN 000100 Garber Supplies, Inc. SB 10100000 FURNITURE, Office U/M UNIT PRICE AGREEMENT NO EFF DATE END DATE --- -------------- --------------- --------------EA $10.0000 07/18/1996 EA $121.0000 05/16/1996 EA $111.0000 05/16/1996 U/M UNIT PRICE AGREEMENT NO EFF DATE END DATE --- -------------- --------------- --------------EA $110.0000 05/01/1996 EA $101.0000 05/03/1996 EA $95.0000 09/04/1996 EA $2.0000 08/02/1996 EA $25.0000 08/09/1996 EA $.0000 09/25/1996
VENDOR CODE NAME VENDOR REF NO VENDOR TYPES --------- ------------------------------ --------------- -------------00001 Laboratory Supplies Inc. MN 00009 ABC Office Supplies SB 00010 National Supplies, Inc. MN 10110100 CHAIR, Executive Style
VENDOR CODE NAME VENDOR REF NO VENDOR TYPES U/M UNIT PRICE AGREEMENT NO EFF DATE END DATE --------- ------------------------------ --------------- -------------- --- -------------- --------------- --------------00010 National Supplies, Inc. MN EA $125.0000 03/22/1996 10110200 CHAIR, Standard Desk U/M UNIT PRICE AGREEMENT NO --- -------------- --------------EA $450.0000 EA $500.0000 EA $79.9500 A02 EFF DATE END DATE --------------04/05/1996 03/24/1996 07/01/1995
VENDOR CODE NAME VENDOR REF NO VENDOR TYPES --------- ------------------------------ --------------- -------------00003 Mikelson's Supplies MN 00009 ABC Office Supplies SB 00010 National Supplies, Inc. CHAIR-33 MN
4-335
November 2010
Vendor Volumes Report (FPRVVOL)

Description
The Vendor Volumes Report may be used to ascertain the volumes of business between the installation and its vendors. This can be done for a specific vendor or for a specific vendor type(s). This report can also be defaulted to display all vendors. The report displays the commodity purchase history including a description, unit of measure, the amount ordered and accepted, the unit price, quantity of approved amounts, and the extended price. FPRVVOL calculates and displays a total extended price for each vendor and vendor commodity activity. Vendor types are originally defined on the Vendor Type Code Maintenance Form (FTMVTYP).
Parameters
Name
Required?
Description
Values
Vendor Number
No
Specific vendor number to report on. If specified, volume information for that vendor only will display. First vendor type code. If specified, volume information for each vendor with this vendor type will display. Second vendor type code. If specified, volume information for each vendor with this vendor type will display. Third vendor type code. If specified, volume information for each vendor with this vendor type will display. Fourth vendor type code. If specified, volume information for each vendor with this vendor type will display. Fifth vendor type code. If specified, volume information for each vendor with this vendor type will display.
Vendor Type 1
No
Vendor Type 2
No
Vendor Type 3
No
Vendor Type 4
No
Vendor Type 5
No
4-336
November 2010
Parameters (cont)
Name
Required?
Description
Values
Vendor Type 6
No
Sixth vendor type code. If specified, volume information for each vendor with this vendor type will display. Seventh vendor type code. If specified, volume information for each vendor with this vendor type will display. Eighth vendor type code. If specified, volume information for each vendor with this vendor type will display. Ninth vendor type code. If specified, volume information for each vendor with this vendor type will display. Tenth vendor type code. If specified, volume information for each vendor with this vendor type will display.
Vendor Type 7
No
Vendor Type 8
No
Vendor Type 9
No
Vendor Type 10
No
Report Sample
REPORT FPRVVOL FISCAL YEAR 96
Banner University Vendor Volumes Report
VENDOR NUMBER NAME --------- -----------------------------00001 Laboratory Supplies, Inc.
VENDOR TYPES ----------------------------MN
COMMODITY QUANTITY APPROVED CODE DESCRIPTION U/M ORDERED ACCEPTED QUANTITY UNIT PRICE EXTENDED PRICE ---------- -------------------------------------------------- --- ---------- ---------- ---------- -------------- ---------------10120100 DESK, Executive (6') .00 .00 1.00 $1,200.0000 $1,200.00 SLE00003 Test Tubes .00 .00 1.00 $245.0000 $245.00 SLE00005 Specimen Slides .00 .00 1.00 $200.0000 $200.00 ---------------Vendor Total $1,645.00
4-337
November 2010
Stores Inventory Module

This section describes each report in the Stores Inventory module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their sevencharacter names.
4-338
November 2010
Stores Daily Transaction Listing Report (FSRDTLG)

Description
The Stores Daily Transaction Listing Report provides you with all activity that changed overall balances of consumable stock in the Stores Inventory System for a defined date range. The system lists all receipts of stock first. Issues list afterwards with the issued to department or organization. For receipts, all values except the Commodity Description are retrieved from the Receiving Detail Table (FPRRCDT) and Purchase Order Detail Table (FPRPODT). For issues, all values except the Commodity Description and Issued Unit of Measure are retrieved from the Stores Issue Header, Detail, and Issue Location Tables (FSBISSH, FSRISSD and FSRISSL). The Commodity Description is retrieved from the Commodity Master Table (FTVCOMM). Using an effective date, the system retrieves the issued unit of measure from the Stores Inventory Master Table (FTVINVM). This report sorts by activity date / transaction type / document code / item number. You may select a secondary sort option. The secondary sort enables you to view the report by primary location / activity date / transaction type / document code / item number. If you choose the second sort option, the primary location displays at the top of the report next to activity date. Otherwise, the primary location appears only in the body of the report. The system calculates extended cost for receipts as (quantity received - quantity rejected) multiplied by the unit price of the item on the purchase order. The system calculates extended cost for issues as the sum of all issued quantities for the item multiplied by the (unit price + any external rate amount). The total extended cost prints for transaction type by date.
Parameters
Name
Required?
Description
Values
From Date DD-M)N-YYYY To Date DD-M)N-YYYY
No
Beginning date to select data for reporting. Leave blank to default the current system date. Ending date to select data for reporting. Leave blank to default the current system date.
DD-MON-YYYY Default = current date DD-MON-YYYY Default = current date
No
4-339
November 2010
Parameters (cont)
Name
Required?
Description
Values
Transaction Type (R/I)
No
Type of transactions to print in the report. Enter R (Receipts) to print only receipt transactions. Enter I (Issues) to print only issue transactions. Leave blank to print both types of transactions.
R I
Receipts Issues
Blank Both types of receipts Yes No (default)
Sort by Location (Y/N)
No
Enter Y(Yes) to sort this report by primary location/ Y activity date/transaction type. The default is N(No), N sort the report by activity date/transaction type.
Report Sample 1
This report sorts by activity date, transaction type, transaction code, and item number.
FSRDTLG
3.0
Banner University Stores Daily Transaction Listing From 25-APR-1996 To 30-APR-1996
01-MAY-1996
14:58:21 Page 1
ACTIVITY DATE 28-APR-1996 TRANSACTION TYPE CODE DATE -- ------ ----------RC 347214 28-APR-1996 RC 347215 28-APR-1996 COMMODITY CODE ITEM U/M --------- ---- --213110000 1 BOX 213120000 1 BOX COMMODITY PRIMARY SUB EXTENDED DESCRIPTION ORG LOCATION LOCATION QUANTITY COST --------------------------- ------ ------ --------------- ---------- ---------------BALL POINT PEN DOCK1 110.00 $550.00 PENCILS 3015 10435 200.00 $500.00 ================ TOTAL $1,050.00 PENCILS BALL POINT PEN STENO PADS STENO PADS 135 135 135 135 3015 3015 3015 3015 3015 3020 10435 10434 100501 100501 100502 100502 3.00 $7.50 20.00 $100.00 <2.00> <$6.00> 2.00 $6.00 1.00 $3.00 1.00 $3.00 ================ TOTAL $113.50
IS IS IS IS
239764 239765 239766 239767
28-APR-1996 28-APR-1996 29-APR-1996 29-APR-1996
213120000 213110000 213130000 213130000
1 1 1 1
BOX BOX EA EA
4-340
November 2010
Report Sample 2
This report is a sample of the secondary sort option. This option enables you to view the report by primary location, activity date, transaction type, transaction code, and item number. If you choose this sort option, the primary location lists at the top of the report next to the activity date.
FSRDTLG
3.0
Banner University Stores Daily Transaction Listing From 25-APR-1996 To 30-APR-1996 PRIMARY LOCATION 3015 COMMODITY CODE ITEM U/M --------- ---- --213120000 1 BOX
01-MAY-1996
14:58:21 Page 1
ACTIVITY DATE 30-APR-1996
TRANSACTION TYPE CODE DATE -- ------ ----------RC 347215 28-APR-1996
COMMODITY PRIMARY SUB EXTENDED DESCRIPTION ORG LOCATION LOCATION QUANTITY COST --------------------------- ------ ------ --------------- ---------- ---------------PENCILS 3015 10435 200.00 $500.00 ================ TOTAL $500.00 PENCILS BALL POINT PEN STENO PADS STENO PADS 135 135 135 135 3015 3015 3015 3015 3015 10435 10434 100501 100501 100502 TOTAL 3.00 20.00 2.00 2.00 1.00 $7.50 $100.00 <$6.00> $6.00 $3.00 ================ $110.50
IS IS IS IS
239764 239765 239766 239767
28-APR-1996 28-APR-1996 29-APR-1996 29-APR-1996
213120000 213110000 213130000 213130000
1 1 1 1
BOX BOX EA EA
4-341
November 2010
Inventory Listing Report (FSRINVL)

Description
The Inventory Listing Report contains on-hand commodity quantities by location. Depending upon the parameter values, the report can print one of the following: All commodities for all locations sorted by commodity/location (default value) One commodity across all locations One commodity in a subset of locations All commodities for one location Redefine the location parameters based on your site policies. If only a primary location (warehouse) is entered, all sublocations (rack/shelf/bin) within the primary location are returned. If a primary location and sublocation are entered, all locations matching these parameters are reported. The system automatically performs a wildcard search using the sublocation, if entered. All report values with the exception of the commodity description are retrieved from the Commodities in Stock Locations Table (FTVSTKL). The commodity description is retrieved from the Commodity Verification Table (FTVCOMM). The total on-hand quantity by commodity is calculated and reported by adding subtotals for all locations. This report normally sorts by commodity code / primary location / sublocation. If the Sort Commodity by Description parameter is Y(Yes), the sort order is by commodity description / primary location / sublocation. Total current value prints for each stock item. To request a report for a hierarchy of commodities, enter the high level commodity within the group.
4-342
November 2010
Parameters
Name
Required?
Description
Values
Commodity
No
If a commodity code is entered, FSRINVL reports on locations only for this commodity. A high level commodity may be entered which reports on all commodities within this hierarchical structure. This parameter may be entered multiple times. If left blank, all commodities are reported. If a value for this parameter is entered, FSRINVL reports on commodities existing only in this location. If left blank, all locations are reported. If entered, a Primary Location parameter is required. All commodities within these locations are reported. Define the sublocation to the level of detail needed as a wildcard search is performed on this parameter. If left blank, all sublocations depending upon other parameter values are reported. If Y(Yes) is entered, the report is sorted by commodity description. The default is N(No), sort by commodity code. Y N Yes No (default)
Primary Location
No
Sub Location
No
Sort Commodity by Description
No
4-343
November 2010
Report Sample
FSRINVL
3.0
Banner University Inventory Listing ISSUE U/M --BOX COMMODITY DESCRIPTION ----------------------------------BALL POINT PEN INVENTORY ACCOUNT -----6094 PRIMARY LOCATION -----3015 3015 SUB LOCATION --------------100433 100434 TOTAL CURRENT VALUE ---------------$75.00 $140.00 ================ $215.00 $150.00 $150.00 ================ $300.00 $27.50 ================ $27.50
18-JUN-1996
14:58:21 Page 1
COMMODITY CODE --------213110000
ONHAND QUANTITY ------------30.00 56.00 ============= 86.00 100.00 100.00 ============= 200.00 10 00 ============= 10.00
213120000
BOX
PENCILS #2
6094 6095
3015 3016
100435 200002 TOTAL
213130000
EA
STENO PADS
6094
3015
100501 TOTAL
4-344
November 2010
Issue Ticket Report (FSRISST)

Description
When stock is issued from the stockroom, generate the Stores Issue Ticket Report to accompany the goods. The Issue Ticket Report contains a listing of the commodity code, description, quantity, quantity remaining to be issued (backordered), and location. Use this report to print return issue documents. Generally, print this report after the issue/return has been created and completed online. The report sorts by Issue Date / Issue Code / Issue Item. If stock was issued out of more than one location to satisfy the stores request, the locations and issued quantity are repeated as many times as there are issue locations for each commodity. An ON ORDER comment appears by the last location in the Comment column if the request has not been satisfied and if the on-order quantity for this commodity stock item is greater than zero. Each issue ticket prints on its own page. The capability to issue from a dock exists online using the Issues Form (FSAISSU). If the issue ticket is not associated with a stores request, the Request Quantity and Remaining Quantity fields display N/A. Additionally, the Request Code field is not displayed. Once this issue ticket has been printed, the internal Printed Date field in the Issues Header Table (FSBISSH) for the issue ticket is updated with the current date to reflect the most recent print date. If the issue ticket is being reprinted, REPRINT appears at the top of the issue ticket. See the following report sample #2. The Printed Date field is used to determine which issue tickets have been printed. If you enter a value for the Issue Code parameter, a report is generated for the specified Issue Code. If you enter an Issue Code, you are not prompted for an Issue Date. If you leave the Issue Code parameter blank, you are then prompted to provide an Issue Date. Enter a value for the Issue Date parameter to print issue tickets with the specified issue date. Leave the Issue Date parameter blank to print issue tickets with the current system date. In certain situations, you will want to print issue tickets as you complete them. To do this, you have the option to print using the sleep/wake mode. When you choose the sleep/wake mode, the process scans the Issues Collector Table (FSRISSC) using the user-entered selection criteria and sleeps for the specified sleep/wake interval. The system performs sleep/wake processing in background mode until the local operating system issues a termination command. Generally, sites using sleep/wake print a control report after the Issue Ticket Report. Enter N in the Print Control Report parameter if you are generating the Issue Ticket Report through sleep/wake. This suppresses the control report from printing after every sleep/wake cycle.
4-345
November 2010
Parameters
Name
Required?
Description
Values
Issue Code
No
When entered, reports only on this issue code. If left blank, completed issues are reported based on the entered Issue Date parameter. If entered, this date is used to restrict reporting to issue tickets with this specific issue date. If left blank, issue tickets with the current system date will be printed. This parameter is ignored if an issue code was specified. Enter Y to print only those issue tickets in the collector table. If entered, only issue tickets in the collector file with this printer will be on the report. You may enter a wildcard expression for this parameter. If you enter an N in the Use Collector Table parameter, this parameter is ignored. Enter Y to print a Control Report after the issue ticket Y report. Enter N to suppress printing a Control N Report. Enter Y to initiate the sleep/wake cycle of this process and printer. Y N Yes No (default) Yes No (default) DD-MON-YYYY
Issue Date (DD-MON-YYYY)
No
Use Collector Table (Y/N) Printer
No
Y N
Yes No (default)
No
Print Control Report (Y/N) Run in Sleep/Wake Mode (Y/N) Sleep/Wake Interval [60 sec]
No
No
No
Time in seconds to pause before resuming execution. Default = 60 seconds
4-346
November 2010
Report Sample 1
Sample of an issue ticket associated with a stores request.
FSRISST
3.0 REQUEST CODE: 93939399
Banner University Issue Ticket
18-JUN-1996
14:58:21 Page 1
REQUESTOR NAME: Jordan Cox ISSUE CODE -------12431343 SHIP CODE -----11111 ITEM ---1
COMMODITY ISSUE CODE/DESC U/M -----------213110000 BOX BALL POINT PEN 213120000 PENCILS #2 213130000 STENO PADS BOX EA
REQUEST QUANTITY ------------20.00
ISSUE/RETURN QUANTITY ------------10.00 5.00 1.00 15.00 0.00
REMAINING QUANTITY ------------10.00 5.00 4.00 0.00 100.00
PRIMARY LOCATION -----3015 3015 3016 3015 3015
SUB LOCATION --------------100433 100434 100434 100435 100501
COMMENT -------ON ORDER
2 3
15.00 100.00
ON ORDER
Report Sample 2
Sample of an issue ticket that is not associated with a stores request.
FSRISST 3.0 Banner University Issue Ticket REPRINT REQUEST QUANTITY ------------N/A ISSUE/RETURN QUANTITY ------------10.00 5.00 1.00 15.00 0.00 REMAINING QUANTITY ------------N/A N/A N/A N/A N/A PRIMARY LOCATION -----3015 3015 3016 3015 3015 SUB LOCATION --------------100433 100434 100434 100435 100501 COMMENT -------18-JUN-1996 14:58:21 Page 1
REQUESTOR NAME: Jordan Cox ISSUE CODE -------12431343 SHIP CODE -----11111 ITEM ---1 COMMODITY ISSUE CODE/DESC U/M -----------213110000 BOX BALL POINT PEN 213120000 PENCILS #2 213130000 STENO PADS BOX EA
2 3
N/A N/A
4-347
November 2010
Stores Low Stock Report (FSRLWSR)

Description
The Low Stock Report lists all stock items whose on-hand quantity plus on order quantities has fallen below the pre-defined reorder point quantity or has fallen below a range defined as a percentage of the reorder point quantity. The formula used to determine if an item needs to be reordered is: on-hand quantity + on order quantity - safety stock quantity < reorder point quantity You may increase the reorder point by entering a range percentage. For example, you may want to list all items within 10% above the reorder point quantity; the reorder point quantity in the above calculation is increased by the following formula: range reorder point = reorder point + .10 multiplied by the reorder point The Stores Commodity Master Table (FTVINVM) supplies most of the values in this report. FTVINVM is used to value all the columns except the Commodity Description and On Order Quantity. Commodity Description is retrieved from the Commodity Verification Table (FTVCOMM). The Locations Table (FTVSTKL) supplies On Hand Quantity as a sum of all locations for this commodity.
Parameters
Name
Required?
Description
Values
Reorder Point Range Percentage
No
If entered, changes the reorder point quantity by adding this percentage of the reorder point to the original reorder point. All items that now fall below this new reorder point are reported. If left blank, the default is zero (0), and the original reorder point from the inventory master is used.
Default = 0
4-348
November 2010
Report Sample
FSRLWSR
3.0
Banner University Low Stock Report ON HAND QUANTITY ------------86.00 15.00 10.00 ON 0RDER QUANTITY ------------0.00 15.00 0.00 REORDER POINT ------------100.00 125.00 50.00
18-JUN-1996 14:58:21 Page 1 REORDER RANGE ------------110.00 137.50 55.00 MINIMUM ORDER ------------100.00 75.00 125.00
COMMODITY ISSUE COMMODITY CODE U/M DESCRIPTION ---------- --- --------------------------------------213110000 BOX BALL POINT PEN 213120000 BOX PENCILS #2 213130000 EA STENO PADS
4-349
November 2010
Open Stores Requisitions Report (FSROPNR)

Description
Generate the Open Stores Requisitions Report to display the status of requests for stock items, goods, and services that are not fully satisfied. Open requests display as of a specific date and are sorted by requisition number. The system displays all open requisitions unless you use the optional parameters to selectively define the report listing. Since more than one issue could be created to satisfy a stores requests need, you may see the issue number more than once on this report. This report sorts by organization/request number/item number. A total extended cost prints for each requisition and for all requisitions within an organization.
Parameters
Name
Required?
Description
Values
No
Date to begin selecting data for reporting. Leave blank to default the current system date. The system compares this date to the delivery date on the requisition. If entered, reports on this specific requisition if it is an open requisition. Leave blank to display all open requests within the organization. If entered, only open requests within this organization are reported. Leave blank to display all open requests within the organization.
DD-MON-YYYY Default = Current date
Requisition Number
No
Organization Code
No
4-350
November 2010
Report Sample
FSROPNR
3.0
Banner University Open Stores Requisitions Report As of 18-JUN-1996 Computer Department REQ DATE ----------10-MAY-1996 QUANTITY REQUESTED ---------2.00 1.00 1.00 REQ TOTAL ISSUED QUANTITY ---------.00 .00 .00 REMAINING QUANTITY -----------2.00 1.00 1.00 REMAINING EXTENDED COST --------------$1,800.00 $300.00 $200.00 --------------$2,300.00
18-JUN-1996
14:58:21 Page 1
ORGANIZATION:
REQUEST NUMBER NAME -------- -----------------------------R91-505 Becki Northrop
COMMODITY ITEM CODE DESCRIPTION U/M ---- ---------- ------------------------------ --1 CEPC1007 Acer 386/20 Computer EA 2 CEMT3002 Magnavox 7BM749 Monochrome Monitor EA 3 CEPR2002 Canon LBP-8 Mark III R Printer EA
ISSUE# -------U000100 U000100 U000100
R91-506
Becki Northrop
30-MAY-1996 QUANTITY REQUESTED ---------5.00 ISSUED QUANTITY ---------2.00 <1.00> 3.00 REMAINING QUANTITY -----------3.00 4.00 1.00 REMAINING EXTENDED COST --------------$60.00 $80.00 $20.00 --------------$20.00 =============== $2,320.00 ISSUE# -------U000101 U000102 U000103
COMMODITY ITEM CODE DESCRIPTION U/M ---- ---------- ------------------------------ --1 22000000 SUPPLIES, Cleaning EA
REQ TOTAL ORG TOTAL
4-351
November 2010
Stores Outstanding Purchases Report (FSROUTP)

Description
The Stores Outstanding Purchases Report lists all open purchase order items for consumable stock items. You may select one commodity code on which to report, or you may accept the default to report all commodities. All the values on this report are retrieved from the Purchase Order Detail Table (FPRPODT). The Commodity Code parameter is verified on the Commodity Verification Table (FTVCOMM). This report sorts by commodity and vendor name. The purchase order number, vendor number, and delivery date print with each order. A total quantity remaining prints for each commodity. This report can select open purchase order items by a date range that the system compares to the delivery date. If the delivery date is not provided on the purchase order, the purchase order is always selected for this report regardless of the date criteria. To request a report for a hierarchy of commodities, enter the high level commodity within the group.
Note The only difference between this report and the Open Purchase Orders Report (FPROPNP) is that FPROPNP sorts by vendor and commodity. Use FSROUTP to view backordered stock commodities. Use FPROPNP to request information on specific purchase orders and to view the ordered quantity, ordered unit price, and buyer and ship-to delivery points.
In this report, extended price represents unit price multiplied by ordered quantity where the ordered quantity is quantity plus the quantity remaining.
Parameters
Name
Required?
Description
Values
Commodity Code
No
If entered, reports only those open purchase orders with this commodity. A high level commodity may be entered which reports on all commodities within this hierarchical structure. This parameter may be entered multiple times. If left blank, all commodities are reported. Beginning date to select data for reporting. Leave blank to report all open purchase orders. DD-MON-YYYY
From Date (DD-MON-YYYY)
No
4-352
November 2010
Parameters (cont)
Name
Required?
Description
Values
To Date (DD-MON-YYYY) Vendor Code
No
Ending date to select data for reporting. Leave blank to default the current system date. If entered, prints only outstanding purchase orders for this vendor code. Leave blank to select all vendors matching the above selection criteria.
DD-MON-YYYY Default = Current date
No
Report Sample
FSROUTP
3.0 ORD U/M --BOX #2 BOX #2
Banner University Stores Outstanding Purchases PO # -------3794213 3794223 VENDOR NUMBER NAME -------- -----------------------000006 Computer Warehouse 000011 Stax Stationary DELIVERY DATE ----------01-JUN-1996 01-JUL-1996
18-JUN-1996
14:58:21 Page 1
COMMODITY CODE/DESC ---------213120000 PENCILS 213120000 PENCILS
UNIT EXTENDED QUANTITY PRICE PRICE ACCEPTED ----------- ------------- ------------$1.50 $225.00 50.00 $1.50 $187.50 25.00 TOTAL
QUANTITY REMAINING ------------100.00 100.00 ============= 200.00 50.00 ============= 50.00
213130000 EA STENO PAD
4621432
000006
Computer Warehouse
01-JUL-1996
$2.50
$125.00
0.00 TOTAL
4-353
November 2010
Physical Inventory Process Report (FSRPHYR)

Description
The Physical Inventory Process Report automatically marks as reconciled all those items whose system inventory count does not vary from the physical inventory count by an amount greater than the system defined tolerance for that commodity. Before running this process, assign all stock commodities an ABC classification on the Stores Inventory Maintenance Form (FTRINVM). Assign a tolerance percentage to the ABC classifications using the System Data Maintenance Form (FTMSDAT). Use the Data field on FTMSDAT to enter the tolerance percentage. Redefine the location parameters based on your site policies. The system automatically performs a wildcard search using the sublocation, if entered. If no primary locations are specified, all commodity/locations within the system that are within tolerance limits are reconciled. If only the primary location (warehouse) is entered, all sublocations within that warehouse that are within tolerance limits are reconciled. If a primary location and sublocation are entered, all locations matching the primary location and sublocation (rack/shelf/bin) are reconciled. Print this report after the process has run to list all reconciled items. This output resembles the Physical Inventory Discrepancy Report (FSRPIDR).
Parameters
Name
Required?
Description
Values
Primary Location
No
If entered, this process reconciles commodities existing only in this location that are within tolerance limits. If left blank, all locations are reconciled that are within tolerance limits for the commodity ABC classification.
4-354
November 2010
Parameters (cont)
Name
Required?
Description
Values
Sub Location
No
If entered, a Primary Location parameter is required. All commodities within these locations are reconciled. Define the sublocation to the level of detail needed as a wildcard search is performed on this parameter. If left blank, all sublocations depending upon other entered parameters are reconciled. The process can be run in audit mode by entering A(Audit). This allows you to view the records that are automatically updated without making changes to the database. Enter U(Update) to have the process update the database and automatically reconcile those inventory records that can be reconciled. A U Audit Update
Report Mode (A/U)
Yes
Report Sample
FSRPHYR
3.0 SUB LOCATION --------------100433 100434 100435 100436 100501 COMMODITY CODE ---------213110000 213110000 213120000 213120000 213130000 ISSUE U/M --BOX BOX BOX BOX EA
Banner University Physical Inventory Process Report COMMODITY DESCRIPTION --------------------------BALL POINT PEN BALL POINT PEN PENCILS #2 PENCILS #2 STENO PAD
18-JUN-1996
14:58:21 Page 1
4-355
November 2010
Pick List Report (FSRPICK)

Description
The Pick List contains all open stores requests by a user defined commodity, location, or commodity/location combination. Use this report after creating a stores request, and print this report just before the issue. This report enables warehouse personnel to pick items to satisfy a request. The Request Detail Table (FPRREQD) is scanned for open stores requests for those commodities, directly or indirectly, by locations. Redefine the location parameters to support site requirements. The system automatically performs a wildcard search using the Sub Location parameter, if entered. If you enter a value in the Commodity Code parameter only, all valid locations for this commodity are listed for a pick selection. This report lists all store requests for stock that have not yet been fulfilled. This report sorts by location and contains each commodity, requested quantity, destination, and backorder quantity. All locations in which the commodity exists print along with the default locations defined on the Inventory Maintenance Table. The default location prints with an asterisk (*) in the default column to aid in picking locations. This report sorts by commodity code and request date. The requests listed first have priority over the other requested orders. A secondary sort option allows you to sort by request code to fulfill one request at a time. To request a report for a hierarchy of commodities, enter the high level commodity within the group. If the on-hand quantity for the location is zero and the on order quantity for the item being requested is greater than zero, ON ORDER displays in the Comments column. If the on-hand quantity for the location is zero and the on order quantity for the item being requested equals zero, N/A displays in the Comments column.
Parameters
Name
Required?
Description
Values
Commodity Code
No
If entered, reports on locations for only this commodity. A high level commodity may be entered which reports on all commodities within this hierarchical structure. This parameter may be entered multiple times. If left blank, all commodities are reported. If entered, reports on commodities existing only in this location. If left blank, all locations are reported.
Primary Location
No
4-356
November 2010
Parameters (cont)
Name
Required?
Description
Values
Sub Location
No
If entered, a Primary Location parameter is required. All commodities within these locations are reported. Define the sublocation to the level of detail needed as a wildcard search is performed on this parameter. If left blank, all sublocations, depending upon other parameter values are reported. If entered, prints all locations just for these stores request items. If entered, all items not closed with a delivery date less than or equal to the entered parameter are selected for reporting. This date is compared to the delivery date on the requisition and can be used with the other selection parameters to further qualify pick list needs. If Y(Yes) is entered, this report prints the pick list by request date / request code. DD-MON-YYYY
Request Code As of Delivery Date
No No
Sort By Request Code
No
Y N
Yes No (default)
4-357
November 2010
Report Sample
FSRPICK
3.0
Banner University Pick List COMMODITY ISSUE CODE U/M ---------- --213110000 BOX BALL POINT PEN 213110000 BOX BALL POINT PEN 213120000 BOX PENCILS #2 213130000 EA STENO PADS REQUEST QUANTITY ------------20.00 PRIMARY LOCATION -----3015 3015 3015 3015 3015 3015 3015 3015 SUB LOCATION --------------10 11 12 10 11 12 10 10 ONHAND QUANTITY ------------30.00 56.00 5.00 30.00 56.00 5.00 0.00 0.00
30-JUN-1996
14:58:21 Page 1
REQUEST REQUESTED CODE DATE DEST -------- ----------- -----12431343 10-JUN-1996 1100
D *
UNISSUED QUANTITY COMMENTS -------------- ----------10.00 ___________ ___________ ___________ 20.00 ___________ ___________ ___________ 5.00 N/A 100.00 ON ORDER
12431353 15-JUN-1996 1101
20.00
12341343 10-JUN-1996 1100 12341343 10-JUN-1996 1100
15.00 100.00
* *
4-358
November 2010
Physical Inventory Discrepancy Report (FSRPIDR)

Description
The Physical Inventory Discrepancy Report lists all items whose system inventory count does not match the physical inventory count. If an item was reconciled, values do not appear in the Count Quantity column. Redefine the location parameters based on your site policies. The system automatically performs a wildcard search using the sublocation, if entered. If only the primary location (warehouse) is entered, all discrepancies within that warehouse are reported. If a primary location and sublocation are entered, all locations matching the primary location and sublocation (rack/shelf/bin) are returned. All values with the exception of the Commodity Description and Over/Under values are retrieved from the Stock Locations Table (FTVSTKL). The commodity description is retrieved from the Commodity Verification Table (FTVCOMM). The Over/Under column is calculated as (Count Quantity minus System Quantity). You may control the printing of the discrepancy report by a tolerance. Before running this process, some or all stock commodities may be assigned an ABC classification on the Stores Inventory Maintenance Form (FTRINVM). Assign the ABC classifications to a tolerance percentage using the System Data Maintenance Form (FTMSDAT). Use the Data field on FTMSDAT to enter the tolerance percentage. The List Reconciled parameter enables you to display only R (Reconciled) items, U (Unreconciled) items, or list A(All) locations regardless of whether items have been reconciled or not. In all cases, an asterisk appears in the Not Rec column identifying those items that have not been reconciled. To request a report for a hierarchy of commodities, enter the high level commodity within the group. This report sorts by location and commodity. Enter a value in the Sort by Commodity parameter to change the sort order of the listing to commodity and location.
4-359
November 2010
Parameters
Name
Required?
Description
Values
Primary Location
No
If entered, reports on commodities with quantity discrepancies existing only in this location. If left blank, all locations are reported with quantity discrepancies. If entered, a Primary Location parameter is required. All commodities with quantity discrepancies within these locations are reported. Define the sublocation to the level of detail needed as a wildcard search is performed on this parameter. If left blank, all sublocations with quantity discrepancies, depending upon other parameter values, are reported. If entered, prints only those stock items that exceed the tolerance defined using the FTMSDAT form for the ABC classification entered. Only those commodities with this classification are checked for tolerance. If left blank, all discrepancies are reported no matter what the tolerance. Option that controls the listing of reconciled and unreconciled items. Enter U (Unreconciled) to list only unreconciled locations. Enter R (Reconciled) to list only reconciled locations. Enter an A (All) to list both reconciled and unreconciled items. Use this parameter along with the above parameters to control the printing selections. U R A Unreconciled (default) Reconciled All
Sub Location
No
ABC Classification
No
Status Selection (A/R/U)
Yes
4-360
November 2010
Parameters (cont)
Name
Required?
Description
Values
Commodity
No
If entered, reports on locations with quantity discrepancies only for this commodity. If left blank, all commodities are reported along with the above parameter values. Use commodity codes along with the location parameters to selectively list a commodity within locations. A high level commodity may be entered which reports on all commodities within this hierarchical structure. This parameter may be entered multiple times. If Y(Yes) is entered, the report is sorted by commodity / location. The default is N(No), sort by location / commodity. Y N Yes No (default)
Sort by Commodity (Y/N)
No
Report Sample
FSRPIDR NOT REC --* * * *
3.0 SUB LOCATION --------------100433 100434 100435 100436 100501
Banner University Physical Inventory Discrepancy Report
18-JUN-1996
14:58:21 Page 1
COMMODITY ISSUE COMMODITY SYSTEM COUNT OVER/ TOTAL AMOUNT CODE U/M DESCRIPTION QUANTITY QUANTITY UNDER DISCREPANCY ---------- --- --------------------------- ------------- ------------- ----------- ---------------213110000 BOX BALL POINT PEN 30.00 22.00 <8.00> <$16.00> 213110000 BOX BALL POINT PEN 56.00 55.00 <1.00> <$2.00> 213120000 BOX PENCILS #2 100.00 99.00 <1.00> <$1.50> 213120000 BOX PENCILS #2 100.00 213130000 EA STENO PAD 1.00 10.00 9.00 $22.50 ================ TOTAL $3.00
4-361
November 2010
Physical Inventory Worksheet (FSRPIWS)

Description
The Physical Inventory Worksheet lists all items that have been flagged for physical inventory count by specific location(s). The purpose of the report is to facilitate the recording of count quantities. All locations print that have not yet been counted or reconciled based upon the values you enter. Redefine the location parameters to support site requirements. The system automatically performs a wildcard search using the sublocation, if entered. If only the primary location is entered, all discrepancies within that primary location (warehouse) are reported. If a primary location and sublocation (rack/shelf/bin) are entered, all locations matching these parameters are reported. All values with the exception of the Commodity Description are retrieved from the Stock Locations Table (FTVSTKL). The commodity description is retrieved from the Commodity Verification Table (FTVCOMM). This report sorts by location and commodity. A secondary sort option allows you to sort by commodity and location.
Parameters
Name
Required?
Description
Values
Primary Location Sub Location
No No
If entered, reports on commodities existing only in this location. If left blank, all locations are reported. If entered, a Primary Location parameter is required. All commodities within these locations are reported. Define the sublocation to the level of detail needed as a wildcard search is performed on this parameter. If left blank, all sublocations depending upon other parameter values are reported.
4-362
November 2010
Parameters (cont)
Name
Required?
Description
Values
Commodity
No
If entered, reports on locations only for this commodity. Use this parameter with the location parameters to selectively list commodities within a location(s). A high level commodity may be entered which reports on all commodities within this hierarchical structure. This parameter may be entered multiple times. If left blank, all commodities are reported. If Y(Yes) is entered, the report is sorted by commodity and location. The default is N(No), sort by location and commodity. Y N Yes No (default)
Sort by Commodity (Y/N)
No
Report Sample
FSRPIWS
3.0 PRIMARY LOCATION -----3015 3015 3015 3015 SUB LOCATION --------------100433 100434 100435 100501
Banner University Physical Inventory Worksheet COMMODITY ISSUE CODE U/M ---------- --213110000 213110000 213120000 213130000 BOX BOX BOX EA
18-JUN-1996 14:58:21 Page 1 COUNT QUANTITY ------------_____________ _____________ _____________ _____________
COMMODITY DESCRIPTION -------------------------------------------------BALL POINT PEN BALL POINT PEN PENCILS #2 STENO PAD
4-363
November 2010
Put List Report (FSRPUTL)

Description
The Put List Report contains all items from a packing list and their default location to enable warehouse personnel to determine where to put the incoming store items. This report lists items that have been received on the dock but have not yet been put away. All stock locations that may contain the commodity are listed. This report sorts by commodity code/date received/locations. The oldest date received prints first in the order. You may limit the selection of data to report by entering a receiver document number, packing list identifier, or commodity code(s). The quantity in the Accepted Quantity column is displayed as a unit of measure in the ORD U/M column. The quantity in the Remaining Dock Qty column is displayed as a unit of measure in the ISSUE U/M column. The dock location is listed first and contains a D in the D column. The default put away location is identified with an asterisk (*) in the D column. If the default location is the same as the dock location, the asterisk displays. The default location for primary and sublocation is retrieved from the Stores Commodity Master Table (FTVINVM) where the commodity code is defined as a stock item. A non-zero value in the dock_remaining_quantity field on the Receiving Detail Table (FPRRCDT) causes an item to appear on the Put List. The Quantity Accepted column contains the quantity of items that have not yet been transferred (using the Stores Stock Transfer Form (FSATRAN) to a non-dock location. If the dock_remaining_quantity field on FPRRCDT is not zero, the system acknowledges that a portion of the receipt is still in the dock location.
Note When items are moved from a dock location to a warehouse location using the Stores Stock Transfer Form (FSATRAN), the system updates the dock_remaining_quantity field on FPRRCDT only if the receiving document number is entered on FSATRAN.
To ensure the system lists items on the Put List that are in a dock location, always enter the receiving document number on FSATRAN.
4-364
November 2010
Parameters
Name
Required?
Description
Values
Receiving Number
No
If entered, reports on all packing slips and commodities for this received document for items that are waiting in dock locations. If left blank, all received documents with items waiting in dock locations are reported. If entered, reports on only this packing slip's commodities that have been received waiting in dock locations. If left blank, all packing slips are reported with any item waiting in dock locations. If entered, reports on all receiver documents with this commodity sitting in dock locations. A high level commodity may be entered which reports on all commodities within this hierarchical structure. This parameter may be entered multiple times. If left blank, all receiver documents with these commodities are reported.
Packing Slip
No
Commodity Code
No
4-365
November 2010
Report Sample
This report sorts by commodity/date received/primary location /sublocation.
FSRPUTL
3.0
Banner University Put List D D *
04-JUN-1996
14:58:21 Page 1
RECEIVER PACKING DATE COMMODITY QUANTITY ORD QUANTITY ISS DOCUMENT SLIP RECEIVED CODE DESCRIPTION ACCEPTED U/M ONHAND U/M -------- --------------- ----------- ---------- ----------------------- ------------- --- ------------ --W9300022 PS98888736 01-JUN-1996 213110000 Ball Point Pen 10.00 BOX 120.00 EA 50.00 EA 20.00 EA W9300020 PSW77776 03-JUN-1996 213110000 Ball Point Pen 10.00 BOX 120.00 EA 50.00 EA 20.00 EA 240.00 EA 100.00 EA 240.00 EA 100.00 EA
PRIMARY SUB LOCATION LOCATION ------ --------------DOCK1 3015 100433 3015 100434 100433 100434 100436 100436
D DOCK1 * 3015 3015 D DOCK1 * 3015 D DOCK1 * 3015
W9300022 PS98888736 W9300020 PSW77776
01-JUN-1996 213120000 03-JUN-1996 213120000
Pencils Pencils
#2 #2
20.00 BOX 20.00 BOX
4-366
November 2010
Dock to Stock Exceptions Report (FSRSTEX)

Description
The Dock to Stock Exception Report lists all items for a specific primary Ship To location, that have been received by the central receiving process but that have not yet been introduced into the Stores Inventory System. The following receiving information prints: accepted quantity, remaining dock quantity, receipt date, receiver document number, packing slip number, purchase order number, and the order amount. The system scans the central receiving document for all stock commodities that have not been transferred over to the Stores warehouses. Dock locations that are primary locations are defined with location type code of D on the Ship To Verification Table (FTVSHIP). The quantity in the Accepted Quantity column is displayed as a unit of measure in the ORD U/M column. The quantity in the Remaining Dock Qty column is displayed as a unit of measure in the ISSUE U/M column. A non-zero value in the dock_remaining_quantity field on the Receiving Detail Table (FPRRCDT) causes an item to appear on the Put List. The Quantity Accepted column contains the quantity of items that have not yet been transferred (using the Stores Stock Transfer Form (FSATRAN) to a non-dock location. If the dock_remaining_quantity field on FPRRCDT is not zero, the system acknowledges that a portion of the receipt is still in the dock location.
Note When items are moved from a dock location to a warehouse location using the Stores Stock Transfer Form (FSATRAN), the system updates the dock_remaining_quantity field on FPRRCDT only if the receiving document number is entered on FSATRAN.
To ensure the system lists items on the Put List that are in a dock location, always enter the receiving document number on FSATRAN.
Parameters Name Required? Description Values
Primary Location
No
If entered, reports on commodities existing only in this dock location. If left blank, all dock locations are reported.
4-367
November 2010
Report Sample
FSRSTEX
3.0
Banner University Dock to Stock Exceptions Report
18-DEC-1996 14:58:21 Page 1 RECEIVER PACKING DOCUMENT SLIP -------- --------------W0000100 12343245678AS87 W0000101 838383838003033 PURCHASE ORDER -------98769876 55GGTT55
DOCK -----DOCK1 DOCK1
COMMODITY ACCEPTED ORD REMAINING ISSUE RECEIPT CODE DESCRIPTION QUANTITY U/M DOCK QTY U/M DATE ------------------------------------- ----------- --- ------------ --- ----------213110000 BALL POINT PEN 20.00 BOX 10.00 EA 12-NOV-1996 213120000 PENCILS #2 15.00 BOX 15.00 EA 12-NOV-1996
4-368
November 2010
Supply Catalog Report (FSRSUPC)

Description
The Supply Catalog Report (FSRSUPC) gives a list of all stock commodities that are currently active. It is sorted by commodity Code. Data is retrieved from the Commodity Master Table (FTVCOMM), the Stores Commodity Master Table (FTVINVM), and the Commodities in Stock Locations Table (FTVSTKL). Each commodity is checked to be sure that it is still active and has not terminated.
Parameters
Name
Required?
Description
Values
Print Cost
No
If Y (Yes) is entered, this report prints the cost. The Y cost is calculated by dividing the total value stored in N FTVCOMM by the Quantity-On-Hand stored in FTVSTKL. If N(No) is entered, the cost value is not printed. If Y (Yes) is entered, prints the primary and sub locations in which this stock item exists. If N (No) is entered, the locations are not printed. If Y (Yes) is entered, prints the text associated with this stock item stored in the FOBTEXT table. If N (No) is entered, the text is not printed. If Y (Yes) is entered, the report is sorted by commodity description. If N (No) is entered, the report is sorted by commodity code. Y N Y N Y N
Yes No (default)
Print Location
No
Yes No (default) Yes No (default) Yes No (default)
Print Text
No
Sort by Commodity Description
No
4-369
November 2010
Parameters (cont)
Name
Required?
Description
Values
Commodity Code Range Start
No
If a value is entered, FSRSUPC begins to print with this commodity. This parameter can not be used when the Sort Commodity by Description parameter is set to Y (Yes). If a value is not entered, this report begins printing with the first commodity. If a value is entered, FSRSUPC ends printing with this commodity. This parameter can not be used when the Sort Commodity by Description parameter set to Y (Yes). If a value is not entered, this report ends printing with the last commodity.
Commodity Code Range End
No
Report Sample
FSRSUPC
3.0
Banner University Supply Catalog PRIMARY LOCATION -----BLDGA BLDGA BLDGA EAST EAST EAST MNDOCK MNSTOR WCU WEST BIO BLDGA EAST MNSTOR EAST WARE1 WARE1 WARE1
26-JUL-1996
10:02:28 Page 1
COMMODITY ISSUE CODE DESCRIPTION U/M ---------- -------------------------------------------------- --B000000001 Pencils, No. 2 EA
COST -----------$0.75
SUB LOCATION TEXT --------------- --------------------RACK12 RACK13 RACK1 RACK2
RACK13 ISLAND
B000000002 Ball Point Pens, Black
EA
$0.80
B000000003 Ball Point Pens, Red
EA
$0.80
RACK1 RACK2 RACK3
4-370
November 2010
Research Accounting Module

This section describes each report in the Research Accounting module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
4-371
November 2010
Grant Rebuild Process (FGRGRBD)

Description
The Grant Rebuild Process (FGRGRBD) rebuilds the grant ledger from the Transaction Detail Table (FGBTRND). For more information, see the Reports and Processes chapter in the Banner Finance TRM Supplement.
4-372
November 2010
Grant Budget Interface Process (FRPBINF)

Description
The Grant Budget Interface Process processes budget data from the collector tables (FRCBUDD and FRCBUDH) into the Banner tables FRBBUDG and FRRBUDG, as described in Mapping Collector Tables to Grant Tables on page 2-132. Processing
1. Processes the rows in the Collector table. For details, refer to Mapping Collector Tables to Grant Tables on
page 2-132.
2. If there are no fatal errors and the process is being run in update mode, the process updates the associated
grant tables.
3. If fatal errors exist and the process is being run in update mode, the process updates occur as described in
the Mapping Collector Tables section in Chapter 2, Processing.

4. The Collector table and interface process support recurring entries for FRBBUDG and FRRBUDG. 5. If the Calculate Indirect Cost and Cost Share Parameter = Y, the process calculates those costs based on the
codes on FRABUDG and inserts the calculated value for Indirect Cost as the 1st sequence in FRRBUDG and the value for Cost Share as the second Sequence. If the Calculate Indirect Cost and Cost Share Parameter = Y, and there are no Indirect or Cost Share Codes on FRABUDG, then an appropriate warning message is issued. If there are Indirect Codes, but not Cost Share Codes, an appropriate warning message is issued. If there are Cost Share Codes, but not Indirect Codes, an appropriate warning message is issued.
6. If Submit Budget for Processing is Y, the system maps the elements from FRBBUDG and FRRBUDG into
FGBTRNI. System ID is identified in FTMSDAT prior to feeding documents. Generic format is YYYYMMDDHHMMSS. Document number is the next available Journal Entry document number. These numbers are sequential and are increased for additional records. If FRBBUDG_REVERSAL_IND is Y, then all rows will have a "-" (minus); otherwise, all rows will have a "+" (plus).
4-373
November 2010
7. If the parameter for Create distribution entries for indirect cost and cost share is Y and Submit Budget for
posting is Y and Calculate Indirect and Cost Share is Y and cost share codes have been set up, then this process will calculate cost share and insert a row into FRBTRNI for the cost share credit distribution FOAPAL defined for FRBBUDG_CSTA_CODE_CHARGE; and insert rows into FGBTRNI for the cost share debit distribution FOAPAL defined for FRBBUDG_CSTA_CODE_DISTR. If no share cost codes have been set up, a warning message displays.
8. When the process has finished in update mode, all values from the collector table are deleted.
Parameters
Name
Required?
Description
Values
Audit or Update Mode Submit Budget for Posting Calc Indirect Cost and Cost Share
Yes Yes
Indicates whether process is to be run in audit or update mode Indicates whether the system should create transactions in FGBTRNI Indicates whether the system should calculate indirect cost and cost share budget item. This is the same as the Calculate Now function in the FRABUDG form. Indicates whether the system should create indirect cost credit budget items; and whether the system should create cost share credit (revenue) and debit (expense) budget items. Indicates whether error report is to be generated during this process
A (default) or U Y N Y N Yes No (default) Yes No (default)
Yes
Create Distr Entries
Yes
Y N
Yes No (default)
Generate Error Report
Yes
Y N
Yes (default) No
4-374
November 2010
Grant Interface Process (FRPGINF)

Description
This program processes information loaded from collector tables (FRCBFIX, FRCEVNG, FRCGLOC, FRCGRNT, FRCGRPI, and FRCGUSN) into the following Banner tables: FRRBFIX, FRBEVNG, FRRGLOC, FRBGRNT, FRRGRPI, and FRRGUSN. Processing
1. Processes the rows in the Collector table. For details, refer to Mapping Collector Tables to Grant Tables on
page 2-132.
2. If there are no fatal errors and the process is being run in Update mode, the process updates the associated
grant tables.
1. If fatal errors exist and the process is being run in update mode, the updates occur as described in Mapping
Collector Tables to Grant Tables on page 2-132.

2. The collector table and interface process supports recurring entries for FRRBFIX, FRREVNG, FRRGLOC,
FRRGRPI, FRRGUSN, and FRRPRXG.

3. If an Agency Code is entered for the Grant Header, the corresponding values from FTVAGCY are defaulted
into FRBGRNT.
4. If a Status Code and Status Date are entered for the Grant Header, the corresponding values are defaulted into
FRRGRST. If the system detects that an entry has been made to either the Project Start Date or the Project End Date existing values, you are notified that similar changes may need to be incorporated into the Research Accounting Fund Maintenance form (FRMFUND). The following warning message displays: Research Accounting Fund budget dates may need similar changes to support multi-year encumbrances.
5. If Event Header Information is entered, the process calculates the due date based on the number of days and
the indicator or the frequency. It uses that information to create the appropriate number of entries in the FRRENVG and FRRPRXG.
6. When the process has finished in update mode, all values from the Collector table are deleted.
4-375
November 2010
Parameters
Name
Required?
Description
Values
Audit or Update Mode Required Generate Error Report
Yes Yes
Indicates whether process is to be run in audit or update mode Indicates whether error report is to be generated during this process
A (default) or U Y N Yes (default) No
4-376
November 2010
Research Accounting Billing Process (FRRBILL)

Description
The Research Accounting Billing Process enables you to generate billing amounts and post transactions to the ledgers. You must specify whether to process information by grant or by PMS code. Banner will identify all grants that belong to the specified bill format and produce output that shows the bill amounts for the parameters that you entered. Processing
1. (Optional) Run the Billing Preview Report (FRRINVS) for a specific date to determine which grants will be
selected by the Research Accounting Billing Process when you run it for that date.
2. Run the Research Accounting Billing Process (FRRBILL) in Audit mode for a specific Billing Format Code
and Billing Period To Date.

3. Run the Billing Exception Report (FRRBEXC) to identify exceptions associated with the specified grant or
PMS code.
4. Correct any exceptions found in Step 3. 5. Run the Research Accounting Billing Process (FRRBILL) in Update mode for a specific Billing Format
Code and Billing Period To Date.You must run the Research Accounting Billing Process for PMS codes to create billed charges and obtain a letter of credit drawdown to reduce the receivables.
6. Use the following forms to view the billed amounts and print the bills. You can also use these forms to change
the billed amounts; however, your changes will not affect the ledgers. Standard Billing 1034 Form (FRA134B) Standard Billing 270 Form (FRA270B) Standard Billing 272 Form (FRA272B) Generic Bill Form (FRAGENB) If you would like to print more than one bill at a time, use the Run Standard Bills and Reports Form (FRABRUN).
4-377
November 2010
Creating Generic Bills Generic bills are user-defined and include information specific to amounts budgeted, billed or retained, based on a group sequence number. When there are no expenses for a billing period, the FRRBILL process produces the bill and updates the Generic Bill Table (FRRGENB) using a group sequence number of 999. If you plan to produce fixed, generic bills with no expenses, use the Grant Billing Format Form (FTMBFRM) to add sequence number 999 to your generic formats. If you do not do this, you will receive the following message on the FRAGENB form: Invalid group sequence number Running FRRBILL in Update Mode When you run FRRBILL in Update mode, Banner does the following: Update the amount in the Cumulative field on the Grant Billing Information window of the Grant Maintenance Form (FRAGRNT). Update the values in the Last Invoice Number and the Sequence Number fields on the Grant Maintenance Form (FRAGRNT). If you billed by PMS code, then Banner will also update the value in the Last Invoice Number field on the Payment Management System Code Maintenance Form (FRVPMSC). Send a document to posting. The starting character of this document is G, the document type is GBL, and the document type sequence number is 75. The transaction date of this document is the date entered in the Posting Date parameter. Change the Status field to S on the Grant Events Assignment Form (FRAEVGA). Insert a row in the Account Charge/Payment Detail Table (TRRACCD) that summarizes billed amounts by grant fund. Use the Research Accounting Payments Entry Form (FRAAREV) to view the summarized amounts. Insert rows into the bill format table that corresponds to the format code entered by the user. For example, if you run the Research Accounting Billing Process for bills with the 272 format, Banner will insert rows in the 272 Bill Format Table (FRR272B) for each of the selected grants. Change the status of the transaction to Billed in the Billing Detail Table (FRRBDET). See Chapter 2, Processing, for more information.
4-378
November 2010
Parameters
Name
Required?
Description
Values
Bill by PMS Code/ Grant Code PMS Code Option
Yes
Indicates whether to generate bills by grant code or PMS code. Way you want to enter PMS code(s). Enter only if Bill by PMS Code/Grant Code = P.
P G A R W S
Bill by PMS code. Bill by grant code. Automatically enter all PMS codes. Enter a range of PMS codes. Search for a specific PMS code using a wildcard. Enter a specific PMS code.
No
From PMS Code To PMS Code PMS Code
No No No
First PMS code in a series. Enter only if PMS Code Option = R. Last PMS code in a series. Enter only if PMS Code Option = R. User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. Enter only if PMS Code Option = W or S. You may use a wildcard (* or %) if PMS Code Option = W. Way you want to enter grant code(s). Enter only if Bill by PMS Code/Grant Code = G. A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant Code Option
No
From Grant Code
No
First grant code in a series. Enter only if Grant Code Option = R.
4-379
November 2010
Parameters (cont)
Name
Required?
Description
Values
To Grant Code Grant Code
No No
Last grant code in a series. Enter only if Grant Code Option = R. User-defined code identifying a grant. Enter only if Grant Code Option = W or S. You may use a wildcard (* or %) if Grant Code Option = W. Code defining the format of a bill. Specifies which transactions to include in the FRRBILL process. Banner will select transactions with dates less than or equal to the Billing Period To Date. Indicates whether this is the last bill for the grant or PMS code. Indicates whether you want to bill for advance or reimbursement payments. Enter only if Billing Format Code = 270B. Indicates whether you want the system to generate a bill and post transactions to the ledger, or generate a bill only. Type of output you want to generate. Default = system date
Billing Format Code Billing Period To Date
Yes Yes
Final or Partial Payment
No
F P A R U A S D
Final bill Not a final bill. Bill for advance payment. Bill for reimbursement payment. Update mode (generate a bill and post transactions). Audit mode (generate a bill only). Generate output that summarizes information by grant. Generate output that shows detailed information by fund.
Advance/ Reimbursement Payment Execution Mode
No
No
Report Type
No
Bill Date Posting Date
No No
Date on which the bill will be generated. Date the transactions in the bill will be posted to the ledgers.
4-380
November 2010
Parameters (cont)
Name
Required?
Description
Values
Bill Retainage
No
Indicates whether you want to generate a bill that includes retainage amounts (amounts withheld from previous bills by your institution). Indicates whether you want to generate a bill that includes payments withheld by the sponsoring agency.
Y N Y N
Bill retainage amounts. Do not bill retainage amounts. Bill withheld payments. Do not bill withheld payments.
Bill Payment Withholding
No
Report Sample
FRRBILL 4.0
Banner University (sctmhp5) Research Accounting Billing Process Audit Mode
07/12/1999 09:50:07 PAGE 1
Bill Format Code: 270B Grant Code ---------------G00000004 G00000005 G00000005 G00000007 G00000008 Fund Code Inv. No. Adj. No. ---------- -------- -------FUND4 1 0 F5 1 0 F5-1 1 0 F7 1 0 F8 1 0 From Date ----------01-MAY-99 01-MAY-99 01-MAY-99 14-FEB-99 21-NOV-98 To Date Bill Amount Act. Cost Amt Retainage Amt ----------- -------------- -------------- -------------31-MAY-99 420.00 420.00 0.00 31-MAY-99 1260.00 1260.00 0.00 31-MAY-99 1260.00 1260.00 0.00 13-MAY-99 1890.00 1890.00 0.00 20-MAY-99 2420.00 2420.00 100.00
4-381
November 2010
* * * REPORT CONTROL INFORMATION (FRRBILL RELEASE 4.0) * * * Parameters have been entered from Host Prompt.
Parameter Name _____________________________ Parameter Seq No: Bill By: Grant Code Billing Format Code: Final/Partial Indicator: Advance/Reimbursement Payment: Execution Mode: Report Type: Bill Date: Post Date: As of Date: Bill Retainage: Bill Payment Withholding: Line Count:
Value ________________ 14382 G A 270B P R A D 19990712095007 19990712095007 31-MAY-1999 N N 55
Message ____________________________________________________________ Grant Code ALL Partial Reimbursement Audit Detail
Chosen number of lines per page
Number of Transactions Processed: 16 Number of TRRACCD Inserted: 0 Number of Exception Inserted: 3
4-382
November 2010
Research Accounting Billing Reversal Process (FRRBREV)

Description
The Research Accounting Billing Reversal Process enables you to reverse, or undo, bills and transactions that you ran in Update mode (Execution Mode = U) in the Research Accounting Billing Process (FRRBILL).
Note You cannot reverse a bill for which payments have been applied on the Research Accounting Payments Entry Form (FRAAREV).
When you run the Research Accounting Billing Reversal Process, Banner will do the following: Create a negative amount. Send a document to posting. The starting character of this document is G. Change the Status field to P on the Grant Events Assignment Form (FRAEVGA). Add 1 to the current adjustment number (Adj#). Insert a negative summary amount in the Account Charge/Payment Detail Table (TRRACCD). Use the Research Accounting Payments Entry Form (FRAAREV) to view this amount. Change the status of the transaction to Unbilled in the Billing Detail Table (FRRBDET). Adds detailed information about the original bill to the Billing Detail History Table (FRRBDTH) if you selected the Maintain History for Reversal? check box on the Research Accounting System Control Form (FRASYSC).
Parameters
Name
Required?
Description
Values
PMS Code Grant Code Billing Invoice Number Invoice Adjustment Number Billing Date
No No Yes Yes No
PMS code on the bill you want to reverse. Grant code on the bill you want to reverse. Invoice number of the bill you want to reverse. Adjustment number of the bill you want to reverse. Date of the bill you want to reverse.
4-383
November 2010
Report Sample
* * * REPORT CONTROL INFORMATION (FRRBREV RELEASE 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Parameter Seq No: PMS Code: Grant Code: Invoice seq no: Invoice adj no: Line Count: Value ________________ 66400 G00000022 1 0 55 Message ____________________________________________________________
Chosen number of lines per page
Number of Transactions Processed: 1
4-384
November 2010
Deferred Grant Process (FRRGRNT)

Description
The Deferred Grant Process enables you to define when you want Banner to perform indirect cost (F & A), cost share, and revenue recognition calculations. It also enables you to post these grant calculations to the ledgers in summary format. This process: Examines the Defer Calculations of Indirect Cost and Cost Share checkbox on the Grant System Control Maintenance Form (FRASYSC). Scans the Transaction Detail Table (FGBTRND) for entries against grant funds where indirect cost (F & A), cost share, and revenue recognition should be performed. Creates entries that move to the Transaction Interface Table (FGBTRNI) for execution of the Transaction Interface Process (FGRTRNI). Once edited and cleared, these entries will move to the Approved Document Table (FOBAPPD). Posting will then process the transactions. Performs a recalculation of indirect cost (F & A) for retroactive rate charges.
Parameters
Name
Required?
Description
Values
Recalculation
No
Indicates whether indirect costs (F & A) have been calculated already and need to be recalculated due to a change in indirect cost rates.
Indirect costs have been calculated previously. Recalculate them now. Indirect costs have not been calculated previously.
N Date From No All grant transactions from this date are selected from the FGBTRND table for recalculation of indirect cost (F & A). Enter only if Recalculation = Y. All grant transactions up to this date are selected from the FGBTRND table for grant calculations or recalculation of indirect cost (F & A).
DD-MON-YYYY
Date To
No
DD-MON-YYYY
4-385
November 2010
Parameters (cont)
Name
Required?
Description
Values
Chart of Accounts Fund Option
Yes No
User-defined code representing an accounting or reporting entity. Way you want to enter fund code(s). A R W S Automatically enter all fund codes. Enter a range of fund codes. Search for a specific fund code using a wildcard. Enter a specific fund code.
No No No
First fund code in a series. Enter only if Fund Option = R. Last fund code in a series. Enter only if Fund Option = R. User-defined code from which grant expenses are paid. Enter only if Fund Option = W or S. You may use a wildcard (* or %) if Fund Option = W. Posting date should be greater than or equal to the entry in the Date To parameter. If this parameter is left blank, the posting date is the greater of the Date To and the system date. Indirect cost (F & A), etc. cannot be posted earlier than the year-to-date activity. DD-MON-YYYY
Posting Date
No
4-386
November 2010
Parameters (cont)
Name
Required?
Description
Values
Execution Mode
No
Indicates whether you want the system to print a report and update the FGBTRNI table, or print a report only.
A U S D
Audit mode. (Print a report, but do not update the FGBTRNI table.) Update mode. (Print a report and update the FGBTRNI table.) Generate output that summarizes information by grant. Generate output that shows detailed information by fund.
Report Type
No
Level of detail you want to include in the report.
4-387
November 2010
Report Sample
FRRGRNT 4.0
Banner University (sctmhp5) Deferred Grant Process *** Update/Detail Mode *** Actv Locn Amount 2,000.00 Amount 120.00 120.00 10.60 10.60 11.54 9.66 2,098.80 2,098.80 Fund GRNT5A TEST GRNT5A GRNT5A TEST TEST GRNT5A GRNT5A Orgn 142071 142071 142071 142071 142071 142071 142071 142071 Acct 7750 7750 5900 5940 7150 7160 5510 1310 Prog 20 10 20 20 10 10 20 20 120.00 21.20 2,098.80 Actv Locn I/C Rate 6% C/S Rate 1% Revenue Y
06-JAN-2001 10:26:53 PAGE: 1
COA: B Grant: GRNTFD05 Fund Orgn Acct Prog GRNT5A 142071 7220 20 Orig. Doc Trans Date I0000815 06-JAN-2001 Def. Doc G0000025 G0000025 G0000025 G0000025 G0000025 G0000025 G0000025 G0000025 Trans Date 06-JAN-2001 06-JAN-2001 06-JAN-2001 06-JAN-2001 06-JAN-2001 06-JAN-2001 06-JAN-2001 06-JAN-2001 Rule INNI Rule GRIC GRIR GRCG GRCG GRCC GRCC GRRV GRAR
Total Indirect Cost for Fund GRNT5A Total Cost Share for Fund GRNT5A Total Revenue Recognition for Fund GRNT5A * * * REPORT CONTROL INFORMATION * * * Run Sequence Number: 44938 Recalculate: N Date To: 06-JAN-2001 Chart of Accounts: B Fund Range: All Funds Posting Date: 06-JAN-2001 Report Execution Mode: Update Report Type: Detail No. Lines per Page: 55 Number of Transactions Processed: 16 Start Time: 10:27:20 End Time : 10:27:49
4-388
November 2010
Deferred Grant Purge Process (FRRGRNP)

Description
The Deferred Grant Purge Process allows you to specify the information that you want to remove from the Grant History Table. You can purge the information by date range. The date range corresponds to the date of the entries in the Deferred Grant History Table (FRRGRNH). This process may be run in audit mode or update mode. In audit mode, the process gives you the number of potential records that would be deleted. In update mode, the process gives you the number of records deleted.
Parameters
Name
Required?
Description
Values
Run Mode
Yes
Determines whether the process is in Audit mode or Update mode. Audit mode will produce a report detailing potential records removed from the database. However, no database changes will occur. Update mode will produce the report and update the database. All transactions from this date are selected from the FRRGRNH table for purge. All transactions up to this date are selected from the FRRGRNH table for purge.
A or a U or u
Audit Update
Date From Date To
Yes Yes
DD-MON-YYYY Default system date DD-MON-YYYY Default system date
4-389
November 2010
Research Accounting Report Process (FRRGRPT)

Description
The Research Accounting Report Process enables you to generate data for Grant Billing reports. When you run this process, Banner will change the Status field to S on the Grant Events Assignment Form (FRAEVGA). The system will also identify all the transactions that were billed on the specified date and will populate the appropriate reporting table. This process does not create entries in the ledger; it simply reports what has been billed so far. This process also populates the Federal Financial Report Table and produces the Federal Financial Report (FRRFFRR). You can run this process for grant codes or PMS codes. Then, you can view the report online using the corresponding form. For example, you can view a standard 269 report using the Standard 269 Report Form (FRR269R). You can also print the report using the Standard Bill and Reports Form (FRABRUN).
Parameters
Name
Required?
Description
Values
Bill by PMS Code/ Grant Code PMS Code Option
Yes
Indicates whether to generate reports by grant code or PMS code. Way you want to enter PMS code(s). Enter only if Bill by PMS Code/Grant Code = P.
P G A R W S
Generate reports by PMS code. Generate reports by grant code. Automatically enter all PMS codes. Enter a range of PMS codes. Search for a specific PMS code using a wildcard. Enter a specific PMS code.
No
From PMS Code To PMS Code
No No
First PMS code in a series. Enter only if PMS Code Option = R. Last PMS code in a series. Enter only if PMS Code Option = R.
4-390
November 2010
Parameters (cont)
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. Enter only if PMS Code Option = W or S. You may use a wildcard (* or %) if PMS Code Option = W. Way you want to enter grant code(s). Enter only if Bill by PMS Code/Grant Code = G. A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant Code Option
No
From Grant Code To Grant Code Grant Code
No No No
First grant code in a series. Enter only if Grant Code Option = R. Last grant code in a series. Enter only if Grant Code Option = R. User-defined code identifying a grant. Enter only if Grant Code Option = W or S. You may use a wildcard (* or %) if Grant Code Option = W. Code defining the format of a report. Last date of the reporting period you want to include in the output. Reporting periods are defined on the Grant Events Assignment Form (FRAEVGA). Indicates whether this is the last report for the grant or PMS code. Y N Final report Not a final report (default)
Report Format Code Reporting Period To Date Final Report
Yes No
No
4-391
November 2010
Report Sample
FRRGRPT 4.0 Report Format Code: 269R PMS Code ---------------HHS1 HHS1 Grant Code ---------G00000016 G00000017 From Date ----------01-FEB-00 01-FEB-00
Banner University (sctmhp5) Research Accounting Report Process
06/06/2000 12:31:29 PAGE 1
To Date Report Amount ----------- -------------29-FEB-00 12000.00 29-FEB-00 12000.00
* * * REPORT CONTROL INFORMATION (FRRGRPT RELEASE 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Parameter Seq No: Bill By: PMS Code Report Format Code: Reporting Period To Date: Final/Partial Indicator: Line Count: Value ________________ 27853 P HHS1 269R 29-FEB-2000 N 55 Message ____________________________________________________________ PMS Code
Partial Chosen number of lines per page
Number of Transactions Processed: 12
4-392
November 2010
Application of Payment Process (TRRAPPL)

Description
The Application of Payment Process enables you to apply payments to charges by grant. By default, Banner will apply payments based on the date of each charge; the oldest charge will be paid first. You can use the Grant Payments Entry Form (FRAAREV) to manually apply a payment to a specific charge by populating the Tpay Number and the Invoice Paid Number fields. See Chapter 2, Processing, for more information.
Note The Application of Payments Process does not have any parameters or printed output.
4-393
November 2010
Unapplication of Payments Process (TRRUNAP)

Description
The Unapplication of Payments Process enables you to reverse, or undo, payments that you applied to charges using the Application of Payment Process (TRRAPPL). You cannot reverse payments that were applied manually on the Research Accounting Payments Entry Form (FRAAREV).
Parameters
Name
Required?
Description
Values
Enter Grant Option
No
Way you want to enter grant code(s).
A R W S
Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From Grant To Grant Wildcards Specific Grants Unapply Date (DD-MON-YYYY)
No No No No No
First grant code in a series. Enter only if Enter Grant Option = R. Last grant code in a series. Enter only if Enter Grant Option = R. Partial grant code that contains a wildcard (* or %). Enter only if Enter Grant Option = W. User-defined code identifying a grant. Banner selects all payments that were applied to charges on or after this date. For example, if you enter 15-AUG-1999, Banner reverses all payments that were applied on 15-AUG-1999 or after 15AUG-1999. DD-MON-YYYY
4-394
November 2010
Report Sample
TRRUNAP 4.0 PAGE 1
Banner University
08-SEP-1998 15:13:17
* * * REPORT CONTROL INFORMATION (TRRUNAP RELEASE 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Parameter Seq No: Grant option : NUMBER OF RECORDS PRINTED : 0 Value ________________ 71031 Specific Grants Message _______________________________________________________________________ The following invalid grant codes were entered: 07-SEP-98
4-395
November 2010
Grant Ledger Exception Report (FGRGLEX)

Description
The Grant Ledger Exception Report prints a list of all transactions that exist in the Transaction Detail Table (FGBTRND), but not the Grant Ledger (FRRGRNL). In the report, transactions are sorted by grant; within each grant, they are sorted by FOAPAL. You can run the Grant Rebuild Process (FGRGRBD) to rebuild the grant ledger from the Transaction Detail Table (FGBTRND).
Parameters
Name
Required?
Description
Values
Yes No
User-defined code representing an accounting or reporting entity. Way you want to enter grant code(s). A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant
No
User-defined code identifying a grant. Enter only if Grant Option = W or S. You may use a wildcard (* or %) if Grant Option = W. First grant code in a series. Enter only if Grant Option = R. Last grant code in a series. Enter only if Grant Option = R.
From Grant To Grant
No No
4-396
November 2010
Report Sample
FGRGLEX 4.0
Banner University (sctmhp5) Grant Ledger Exception Report As of 10-DEC-1999
10-DEC-1999 09:32:14 PAGE 1
Chart of Accounts: S Grant Code: G00000010 Fund Cd F10 F10 F10 Orgn Cd 11004 11004 11004 Acct Cd 5510 6111 7523
Chart for Development Research on Rheumatoid Arthritis Prog Cd 10 10 10 Actv Cd Locn Cd Fld Cd 03 03 03 Field Cd Desc YTD activity YTD activity YTD activity Grnt Yr 1998 1998 1998 Trans Amount 4060 2900 1160 Grant Ledger Amt 2800 2000 800
Chart of Accounts: S Grant Code: G00000011 Fund Cd F11 F11 F11 Orgn Cd 11004 11004 11004 Acct Cd 5510 6111 7523
Chart for Development Research on Arthritis Prog Cd 10 10 10 Actv Cd Locn Cd Fld Cd 03 03 03 Field Cd Desc YTD activity YTD activity YTD activity Grnt Yr 1998 1998 1998 Trans Amount 11340 8100 3240 Grant Ledger Amt 8400 6000 2400
* * * REPORT CONTROL INFORMATION (fgrglex release 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Seq No: Chart of Accounts: Grant Option: Grant: Line Count: Value ________________ S A 55 Message ____________________________________________________________ All grants Number of lines per page
4-397
November 2010
Standard 1034 Billing Form (FRR134B)

Description
The Standard 1034 Billing Form prints a bill in the standard 1034 format. It is an Oracle report. After you run the Research Accounting Billing Process (FRRBILL), you can run this bill from the Standard 1034 Billing Form (FRA134B). You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this bill for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a bill that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a bill that summarizes all grants with that PMS code or producing separate bills for each grant. If you want to print a 1034 continuation form, which contains detailed information about the bill, select the Details button. Banner will print a separate page that you will need to collate with the appropriate bill. See Chapter 2, Processing, for more information.
Note To run this bill, Oracle Reports must be installed on your computer. This bill will not run from a web-enabled form.
Parameters
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. User-defined code identifying a grant. Indicates whether to print one bill summarizing all grants with the specified PMS code or to print one bill for each grant. Enter only if you entered a value in the PMS Code parameter. Invoice number generated by the Research Accounting Billing Process (FRRBILL). Number of times the bill has been adjusted. M = Print one bill for each grant. S = Print one bill summarizing all grants.
Grant Code Single/Multiple Bills
No No
Invoice Sequence Number Adjusted Number
Yes Yes
4-398
November 2010
Parameters (cont)
Name
Required?
Description
Values
Period To Date
Yes
Last date of the billing period you want to include in the output. Billing periods are defined on the Grant Events Assignment Form (FRAEVGA). Format for the report output. The default value is PDF.
DD-MON-YYYY
Destination Format
Yes
DELIMITED DELIMITED DATA HTML HTMLCSS PDF POSTSCRIPT (This format is not currently supported.) PRINTER DEFINITION (This format is not currently supported.) RTF XML
Destination Type
Yes
Indicates where the report output will be directed. The default value is Cache. Values of File, Mail, or Printer are available only when Communication Mode is set to Asynchronous.
Cache File Printer Mail
Display report on screen. (default value) Save report to a file. Print report. Send report via email.
4-399
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Name
No
Printer or file where report output will be directed. The destination name can be up to 30 characters in length.
If destination type is File, use a valid drive, folder, and file name. If destination type is E-mail, use a valid e-mail address. Enter multiple addresses with commas as separators. If destination type is Printer, use a valid printer name. If blank, report goes to the Report Servers default printer.
Execution Mode
Yes
Way you want this report to run.
Batch Runtime
Run from job submission. Run from a form. Wait on the Banner form for report results.
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default) No Do not display Report Parameters form. Yes Show Report Value Window No Do not display Report Value window.
4-400
November 2010
4-401
Voucher No.
Standard Form 1034 Revised January 1980 Department of the Treasury 1 TFRM 4-2000
PUBLIC VOUCHER FOR PURCHASES AND SERVICES OTHER THAN PERSONAL

10 Schedule No. Paid By Date Voucher prepared 09/09/98 Contract Number and Date AIDS3049-56 Requisition Number and Date

Grant billing agency without LOC 4567 Market street Main building 2nd floor Philadelphia PA 19355
Date Invoice recieved
Discount Terms
Payee's Account Number
Payee's Name and Address
Diane Mathews 3601 Market street Main building 3rd floor Phialdelphia PA 19104
To Weight
G00000032
Government B/L Number
Shipped From
Unit Price
Quantity
Amount COST PER (1) $618.00
Number And Date Of Order
Date Of Delivery Or Service
Articles Or Services (Enter Description, item number of contract or Federal supply schedule, and other information deemed necessary)
09/09/98 Research on cure for aids
09/09/98
Details.....
(Use continuation sheets if necessary) PAYMENT: =$ BY APPROVED FOR
(Payee must NOT use the space below) Exchange Rate =$
TOTAL
Differences
$618.00
Provisional Complete Partial Final Progress Advance TITLE
Amount Verified: Correct (signature or initials)
Pursuant to authority vested in me, I certify that this voucher is correct and proper for payment
Date
(Authorized Certifying Official)
(Title)
ACCOUNTING CLASSIFICATION
CHECK NUMBER
On Account Of U.S. Treasury
CHECK NUMBER
ON (Name of Bank)
CASH $
DATE
PAYEE
PER
When stated in foreign currency, insert name of currency. If the ability to certify and authority to prove are combined in one person, one signature only is necessary. Otherwise the approving officer will sign in the space provided, over his official title. When a voucher is reciepted in the name of company or corporation, the name of the person writing the company or corporate name, as well as the capacity in which he signs, must appear. For example: "John Doe Company, per John Smith, Secretary", or Treasurer" as the case may be. Previous edition usable 1034-119
TITLE
NSN 7540-00-900-2234 PRIVACY STATEMENT The information requested on this form is required under the provisions of 31 U.S.C. 82b and 82c, for the purpose of disbursing Federal money. The information requested is to identify the particular creditor and the amounts to be paid. Failure to furnish this information will hinder discharge of the payment.
PAYMENT WITHHOLDING
November 2010
Standard 269 Report Form (FRR269R)

Description
The Standard 269 Report Form prints grant billing information in the standard 269 format. It is an Oracle report. After you run the Research Accounting Report Process (FRRGRPT), you can run this report from the Standard 269 Report Form (FRA269R).You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this report for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a report that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a report that summarizes all grants with that PMS code or producing a separate report for each grant.
Note To run this report, Oracle Reports must be installed on your computer. This report will not run from a web-enabled form.
Parameters
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. User-defined code identifying a grant. Indicates whether to print one report summarizing M all grants with the specified PMS code or to print one S report for each grant. Enter only if you entered a value in the PMS Code parameter. Last date of the reporting period you want to include in the output. Reporting periods are defined on the Grant Events Assignment Form (FRAEVGA). Print one report for each grant. Print one report summarizing all grants.
Grant Code Single/Multiple Reports
No No
Period To Date
Yes
DD-MON-YYYY
4-402
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Format
Yes
Format for the report output.
DELIMITED DELIMITED DATA HTML HTMLCSS PDF (default) RTF XML
Destination Type
Yes
Where the report output will be directed. Values of File, Mail, or Printer are available only when Communication Mode is set to Asynchronous.
Display report on screen. (default) Save report to a file. Print report. Send report via email.
Destination Name
No
Execution Mode
Yes
Batch Runtime
Run from Job Submission. Run from a form.
4-403
November 2010
Parameters (cont)
Name
Required?
Description
Values
Communication Mode
Yes
Communication mode.
Synchronous
Wait on the Banner form for report results.
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default) No Do not display Report Parameters form. Yes Show Report Value Window. No Do not display Report Value window.
4-404
November 2010
4-405
FINANCIAL STATUS REPORT
(Short Form)
(Follow the instructions on the back) 1. Federal Agency and Organizational Element to which Report is Submitted Grant billing agency without LOC 3. Recipient Organization (Name and complete address, including ZIP code) Diane Mathews 3601 Market street Main building 3rd floor Phialdelphia PA 19104 4. Employer Identification Number E1-5051 GRTB-1 8. Funding/Grant Period (See Instructions) From : ( Month, Day, Year ) To : ( Month, Day, Year ) March , 01, 1998 10. Transactions : February , 29, 2000 5. Recipient Account Number or Identifying Number 6. Final Report Yes
9. Period Covered by this Report From : ( Month, Day, Year )
Page 1
Of 1 Pages

2. Federal Grant or Other Identifying Number Assigned OMB Approval by Federal Agency No. 0348-0039 AIDS3049-56 7. Basis X No CASH
To : ( Month, Day, Year )
Report Sample
X ACCRUAL
March , 01, 1998 I Previously Reported $.00 $.00 II This Period
March , 31, 1998 III Cumulative $3,300.00 $300.00 $3,300.00 $300.00 $3,000.00 $.00 $.00 $.00 $3,000.00 $.00
a. Total Outlays b. Recipient Share of Outlays c. Federal Share of Outlays d. Total unliquidated obligations e. Recipient share of unliquidated obligations f. Federal share of unliquidated obligations g. Total Federal share (Sum of lines c and f) h. Total Federal funds authorized for this funding period i. Unobligated balance of Federal funds (Line h minus line g) a. Type of Rate (Place "x" in the appropriate box) Provisional Predetermined 11. Indirect Expense b. Rate $.00 b. Base $.00
-$3,000.00
Final b. Total Amount $.00
Fixed b. Federal Share $.00 12. Remarks: Attach any explanations deemed necessary or information required by Federal sponsoring agency in compliance with governing legislation.
This is the text that will be printed on 269 repor
13. Certification : I certify to the best of my knowledge and belief that this report is correct and complete and that all outlays and unliquidated obligations are for the purposes set forth in the award documents. Typed or Printed Name and Title Telephone (Area code, number and extension)
Signature of the Authorized Certifying Official
Date Report Submitted 08/11/98
NSN 7540-01-218-4387
269-201
Standard Form 269A (REV 4-88) Prescribed by OMB Circulars A-102 and A -110
November 2010

Description
The Standard 270 Billing Form prints a bill in the standard 270 format. It is an Oracle report. After you run the Research Accounting Billing Process (FRRBILL), you can run this bill from the Standard 270 Billing Form (FRA270B). You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this bill for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a bill that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a bill that summarizes all grants with that PMS code or producing separate bills for each grant.
Note To run this bill, Oracle Reports must be installed on your computer. This bill will not run from a Web-enabled form.
Parameters
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. User-defined code identifying a grant. Indicates whether to print one bill summarizing all grants with the specified PMS code or to print one bill for each grant. Enter only if you entered a value in the PMS Code parameter. Invoice number generated by the Research Accounting Billing Process (FRRBILL). Number of times the bill has been adjusted. Last date of the billing period you want to include in the output. Billing periods are defined on the Grant Events Assignment Form (FRAEVGA). DD-MON-YYYY M S Print one bill for each grant. Print one bill summarizing all grants.
No No
Invoice Sequence Number Adjusted Number Period To Date
Yes Yes Yes
4-406
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Format
Yes
DELIMITED DELIMITED DATA HTML HTMLCSS PDF (default) POSTSCRIPT (This format is not currently supported.) PRINTER DEFINITION (This format is not currently supported.) RTF XML
Destination Type
Yes
Destination Name
No
4-407
November 2010
Parameters (cont)
Name
Required?
Description
Values
Execution Mode
Yes
Batch Runtime
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default) No Do not display Report Parameters form. Yes Show Report Value Window No Do not display Report Value window
4-408
November 2010
4-409
Approved by Office of Management and Budget, No. 80-R0183
Page of
REQUEST FOR ADVANCE OR REIMBURSEMENT

b. "x" the applicable box FINAL X PARTIAL 3. FEDERAL SPONSORING AGENCY & ORGANIZATIONAL 4. FEDERAL GRANT OR OTHER IDENTIFYING ELEMENT TO WHICH THIS REPORT IS SUBMITTED NUMBER ASSIGNED BY FEDERAL AGENCY a. "x" one, or both boxes ADVANCE X REIMBURSEMENT 1. TYPE OF PAYMENT REQUESTED
1
CASH
2. BASIS OF REQUESTS
ACCRUAL

5. PARTIAL PAYMENT REQUEST NUMBER FOR THIS REQUEST
Grant billing agency without LOC LYME3049-56

8. FROM (month, day, year) 6. EMPLOYER ID NUMBER 7. RECIPIENT'S ACCOUNT NUMBER OR ID NUMBER
PERIOD COVERED BY THIS REPORT TO (month, day, year)
Report Sample
E1-5051 GRTB-2 May , 01, 1998

9. RECIPIENT ORGANIZATION Name : Diane Mathews Number and Street : 3601 Market street
May
, 31, 1998
10. PAYEE (Where check is to be sent if different than item 9) Name : Diane Mathews Number and Street : 3601 Market street
Main building 3rd floor City, State, Zip Code : Phialdelphia PA 19104
11. (a)
City, State, Zip Code : Phialdelphia PA 19104
Main building 3rd floor
COMPUTATION OF AMOUNT REIMBURSEMENT/ADVANCES REQUESTED (b) (c)
PROGRAMS/FUNCTIONS/ACTIVITIES >
a. Total program outlays todate b. Less: Cumulative program income (As of date)
TOTAL $10,350.00 $.00 $10,350.00
c. Net program outlays (Line a minus line b)
$.00
d. Estimated net cash outlays for advance period
$10,350.00
e. Total (Sum of lines c & d)
$1,360.00
f. Non-Federal share of amount on line e
$8,990.00
g. Federal share of amount on line e
$4,590.00
h. Federal Payments previously requested
$4,400.00
i. Federal share now requested (Line g minus line h)
$.00
1 st month
$.00
2 nd month
j. Advances required by month, when requested by Federal grantor agency for use in makiing prescheduled advances 12.
$.00
3 rd month ALTERNATE COMPUTATION FOR ADVANCES ONLY
$.00
a. Estimated Federal cash outlays that will be made during period covered by the advance
$.00
b. Less: Estimated balance of Federal cash on hand as of beginning of advance period
$.00
c. Amount requested (Line a minus line b) 13. DATE REQUEST SUBMITTED
CERTIFICATION SIGNATURE OF AUTHORIZED CERTIFYING OFFICIAL I certify that to the best of my knowledge and belief the data above are correct and that all outlays are made in accordance with the grant conditions or other agreement and that payment is due and has not TYPED OR PRINTED NAME AND TITLE been previously requested. Noll, Mark
06/25/98
TELEPHONE (AREA CODE, NUMBER, EXTENSION
Professor
This space for agency use
270-102
STANDARD FORM 270 Prescribed by Office of Management and Budget Cir. No. A-110
November 2010

Description
The Standard 272 Billing Form prints a bill in the standard 272 format. It is an Oracle report. After you run the Research Accounting Billing Process (FRRBILL), you can run this bill from the Standard 272 Billing Form (FRA272B). You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this bill for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a bill that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a bill that summarizes all grants with that PMS code or producing separate bills for each grant.
Note To run this bill, Oracle Reports must be installed on your computer. This bill will not run from a Web-enabled form.
Parameters
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. User-defined code identifying a grant. Indicates whether to print one bill summarizing all grants with the specified PMS code or to print one bill for each grant. Enter only if you entered a value in the PMS Code parameter. Invoice number generated by the Research Accounting Billing Process (FRRBILL). Number of times the bill has been adjusted. Last date of the billing period you want to include in the output. Billing periods are defined on the Grant Events Assignment Form (FRAEVGA). DD-MON-YYYY M S Print one bill for each grant. Print one bill summarizing all grants.
No No
Invoice Sequence Number Adjusted Number Period To Date
Yes Yes Yes
4-410
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Format
Yes
Format for the report output. The default value is PDF.
DELIMITED DELIMITED DATA HTML HTMLCSS PDF RTF XML
Destination Type
Yes
Indicates where the report output will be directed. Values of File, Mail, and Printer are available only when Communication Mode is set to Asynchronous.
Destination Name
No
Execution Mode
Yes
Batch Runtime
Run from job submission. Run from a form.
4-411
November 2010
Parameters (cont)
Name
Required?
Description
Values
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default value) No Do not display Report Parameters form. Yes Show Report Value Window No Do not display Report Value window
4-412
November 2010
4-413
FEDERAL CASH TRANSACTIONS REPORT
(See instructions on the back. If report is for more than one grant or assistance agreement, attach completed Standard Form 272-A.) 1. Federal sponsoring agency and organizational element to which this report is submitted
Approved by Office of Management and Budget No. 80-R0182
Grant billing agency with LOC

2. RECIPIENT ORGANIZATION Name :
Diane Mathews NASA7890-123

6. Letter of credit number
4. Federal Grant or other identification number
5. Recipient's account number or identifying number
GRTB-P
7. Last payment voucher number

Number and Street :
3601 Market street Main building 3rd floor 11111111111111

8. Payment vouchers certified to your account
2
9. Treasury checks recieved (whether or not deposited)
Give total number for this period
Report Sample
City, State and ZipCode : Phialdelphia PA 19104
10.
3. FEDERAL EMPLOYER IDENTIFICATION NO.
PERIOD COVERED BY THIS REPORT

TO (month, day, year)
E1-5051 a. Cash on hand beginning of report period
FROM (month, day, year)
April , 01, 1998
April , 30, 1998 -$6,550.00 $6,550.00 $.00 $6,550.00 $.00 $2,580.00 $.00 $2,580.00 -$600.00 -$3,180.00
11. STATUS OF c. Treasury check payments FEDERAL d. Total reciepts ( Sum of lines b and c ) CASH f. Gross disbursements g. Federal share of program income h. Net disbursements ( line f minus line g ) i. Adjustments of prior periods j. Cash on hand end of period
( See specific instructions on the back )
b. Letter of credit withdrawls
e. Total cash available ( Sum of lines a and d )
OTHER INFORMATION $.00
12. THE AMOUNT SHOWN 13. ON LINE 11, ABOVE REPRESENTS CASH a. Interest Income REQUIREMENTS FOR ENSUING 2
b. Advances to subgrantees or subcontractors Days
$.00
14. REMARKS ( Attach additional sheets of plain paper where space is required )
This text will print on the bill/report
15.
SIGNATURE
CERTIFICATION
DATE REPORT SUBMITTED
AUTHORIZED CERTIFYING OFFICIAL

TYPED OR PRINTED NAME AND TITLE
05/10/98
TELEPHONE ( Area Code, Number, Extension )
I certify to the best of my knowledge and belief that this report is true in all respects and that all disbursements have been made for the purpose and conditions of the grant on agreement.
THIS SPACE FOR AGENCY USE ONLY
H. Donald, Thibault Professor
272-22
STANDARD FORM 272- (7-76) Prescribed by the Office of Management and Budget Cir. No. A-110
November 2010
Standard 272 Report Form (FRR272R)

Description
The Standard 272 Report Form prints grant billing information in the standard 272 format. It is an Oracle report. After you run the Research Accounting Report Process (FRRGRPT), you can run this report from the Standard 272 Report Form (FRA272R). You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this report for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a report that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a report that summarizes all grants with that PMS code or producing a separate report for each grant.
Note To run this report, Oracle Reports must be installed on your computer. This report will not run from a Web-enabled form.
Parameters
Name
Required?
Description
Values
PMS Code
No
Grant Code Single/Multiple Reports
No No
Report as of Date
Yes
DD-MON-YYYY
4-414
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Format
Yes
DELIMITED DELIMITED DATA HTML HTMLCSS PDF (default) POSTSCRIPT (This format is not currently supported.) PRINTER DEFINITION (This format is not currently supported.) RTF XML
Destination Type
Yes
Destination Name
No
4-415
November 2010
Parameters (cont)
Name
Required?
Description
Values
Execution Mode
Yes
Batch Runtime
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default value) No Do not display Report Parameters form. Yes Show Report Value Window No Do not display Report Value window.
4-416
November 2010
4-417
FEDERAL CASH TRANSACTIONS REPORT
(See instructions on the back. If report is for more than one grant or assistance agreement, attach completed Standard Form 272-A.) 1. Federal sponsoring agency and organizational element to which this report is submitted
Approved by Office of Management and Budget No. 80-R0182
Grant billing agency with LOC

2. RECIPIENT ORGANIZATION Name :
Diane Mathews NASA7890-123

6. Letter of credit number
4. Federal Grant or other identification number
5. Recipient's account number or identifying number
GRTB-P1
7. Last payment voucher number

Number and Street :
3601 Market street Main building 3rd floor

8. Payment vouchers certified to your account
11111111111111 Give total number for this period

9. Treasury checks recieved (whether or not deposited)
Report Sample
City, State and ZipCode : Phialdelphia PA 19104
10.
3. FEDERAL EMPLOYER IDENTIFICATION NO.
PERIOD COVERED BY THIS REPORT

TO (month, day, year)
E1-5051 a. Cash on hand beginning of report period
FROM (month, day, year)
March , 01, 1998
May
, 31, 1998 $.00 $.00 $.00 $.00 $.00 $4,000.00 $.00 $4,000.00 $.00 -$4,000.00
11. STATUS OF c. Treasury check payments FEDERAL d. Total reciepts ( Sum of lines b and c ) CASH f. Gross disbursements g. Federal share of program income h. Net disbursements ( line f minus line g ) i. Adjustments of prior periods j. Cash on hand end of period
( See specific instructions on the back )
b. Letter of credit withdrawls
e. Total cash available ( Sum of lines a and d )
OTHER INFORMATION $.00
12. THE AMOUNT SHOWN 13. ON LINE 11, ABOVE REPRESENTS CASH a. Interest Income REQUIREMENTS FOR ENSUING 5
b. Advances to subgrantees or subcontractors Days
$.00
14. REMARKS ( Attach additional sheets of plain paper where space is required )
15.
SIGNATURE
CERTIFICATION
DATE REPORT SUBMITTED
AUTHORIZED CERTIFYING OFFICIAL

08/11/98
I certify to the best of my knowledge and belief that this report is true in all respects and that all disbursements have been made for the purpose and conditions of the grant on agreement.
THIS SPACE FOR AGENCY USE ONLY
TELEPHONE ( Area Code, Number, Extension )
272-22
STANDARD FORM 272- (7-76) Prescribed by the Office of Management and Budget Cir. No. A-110
November 2010
Agency Budget Report (FRRABUD)

Description
The Agency Budget Report prints a list of budget activity for grants received from the specified sponsoring agency.
Parameters
Name
Required?
Description
Values
Agency Code Proposal Code Budget Code Personnel Indicator Display Cost Share Percent
Yes No No Yes No
User-defined code representing a sponsoring agency. User-defined code representing a proposal. User-defined code identifying a budget. Personnel ID of the person whose name you want to include on the report. Indicates whether to include cost share percentage information in the report. Default = All proposals Default = All Default = 001 (Principal Investigator) Yes Include cost share percentage information. No Do not include cost share percentage information.
Execution Mode
No
Indicates whether you want the system to print a report and post transactions to the ledger, or print a report only. Indicates whether to include waived indirect costs (F & A) in the report.
U A Y
Update mode (Print a report and post transactions.) Audit mode (Print a report only.) Include waived indirect costs. (default value)
Print Waived Indirect Amount
No
No Do not include waived indirect costs.
4-418
November 2010
Report Sample
FRRABUD CONTACT: Bob Gibson AGENCY : Inside Repairs ADDRESS: 88 Cardinal Corner St. Louis MO 47834 PROPOSAL: PROPFD04 Athletic event planning Primary Investigator TOTAL REQUESTED AMOUNT: BUDGET: FISCAL
Banner University (sctmhp5) Agency Budget Report
01/04/01 14:09:15 PAGE 1
FDPROP6 Schmidt, Michael J $100,000.00 PERIOD COST SHARE 13,500 900 1,500 10,000 5,000 1,500 3,500 2,500 0 0 38,400 01-JUL-1999 TO 30-JUN-2000 PROJECT VALUE 30,000 2,000 3,000 20,000 10,000 3,000 7,000 5,000 720 11,200 91,920
Fiscal Budget for Proposal BUDGET AMOUNT 16,500 1,100 1,500 10,000 5,000 1,500 3,500 2,500 720 11,200 53,520
TITLE Salaries-Faculty Health Ins Premiums Office Supplies Office Equipment Mobile Phone Pagers Legal Accounting Indirect Cost Fringe Amount TOTAL R
COST SHARE PERCENT 0.8182 0.8182 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 0.0000 0.0000 0.7175
* * * REPORT CONTROL INFORMATION (FRRABUD RELEASE 3.1) * * * Parameters have been entered from Host Prompt.
Parameter Name _____________________________ Parameter Seq No: Agency Code: Proposal Code: Budget Code: Personnel Ind: Cost Share Percent: Execution Mode: Line Count:
Value ________________ 43289 KITCHEN 001 Y A 55
Message ____________________________________________________________ All Proposal Code All Budget Code Primary Investigator Print cost share percentage Audit Mode Chosen number of lines per page
4-419
November 2010
Billing Detail Exception Report (FRRBDEX)

Description
The Billing Detail Exception Report prints a list of all documents that are stored in the Transaction Detail Table (FGBTRND), but not the Billing Detail Table (FRRBDET). Documents are sorted by grant within a FOAPAL string. If you selected the Defer Calculations of Indirect Cost and Cost Share check box on the Grant System Control Maintenance Form (FOASYSC), you must run the Deferred Grant Process (FRRGRNT) before you run this report.
Parameters
Name
Required?
Description
Values
Yes No
User-defined code representing an accounting or reporting entity. Way you want to enter grant code(s). A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant
No
User-defined code identifying a grant. Enter only if Grant Option = W or S. You may use a wildcard (* or %) if Grant Option = W. First grant code in a series. Enter only if Grant Option = R. Last grant code in a series. Enter only if Grant Option = R. First date you want to include in the report. Last date you want to include in the report. DD-MON-YYYY DD-MON-YYYY
From Grant To Grant From Date To Date
No No Yes Yes
4-420
November 2010
Report Sample
FRRBDEX 4.0
Banner University Billing Detail Exception Report 01-OCT-1988 To 31-JAN-2000 Chart for Development Research on Arthritis Prog Cd 10 Sub Num Item Num 0 0 0 Actv Cd Locn Cd Seq Num 0 0 0 Trans Amount 1 1 1 3000 -2000 200 Actv Cd Locn Cd
08-JAN-2000 11:02:21 PAGE 1
Chart of Accounts: S Grant Code: G00000002 Fund Cd FUND2 Code Orgn Cd 11004 Doc Type JV JV JV Acct Cd 7523
Acct Cd 6111 Trans Date
J0000129 J0000130 J0000131 Cd
10-OCT-98 11-OCT-98 10-JUN-99 Prog Cd 10
Orgn Cd
FUND2 Doc Code J0000129 J0000130 J0000131
11004 Doc Type JV JV JV
Trans Date 10-OCT-98 11-OCT-98 10-JUN-99
Sub Num 0 0 0
Item Num 0 0 0
Seq Num 1 1 1
Trans Amount 1200 -800 80
* * * REPORT CONTROL INFORMATION (frrbdex release 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Seq No: Chart of Accounts: Grant Option: Grant: Begin Date: To Date: Line Count: Value ________________ S A 01-OCT-1988 31-JAN-2000 55 Message ____________________________________________________________ All grants
Number of lines per page
4-421
November 2010
Billing Exception Report (FRRBEXC)

Description
The Billing Exception Report prints a list of all grants that have exceptions associated with them. You must run the Research Accounting Billing Process (FRRBILL) in Audit mode before you run this report. You can run this report by grant or by PMS code for a specific billing period end date (To Date parameter). If you enter S as a value for the Exception Option parameter, Banner produces a report that lists only grants with the specified Exception Code. See Chapter 2, Processing, for more information.
Parameters
Name
Required?
Description
Values
PMS
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. You may enter a partial PMS code with a wildcard (* or %). User-defined code identifying a grant. Billing period end date. Last date you want to include in the report. DD-MON-YYYY
Grant Code To Date
No Yes
4-422
November 2010
Parameters (cont)
Name
Required?
Description
Values
Exception Option
No
Indicates whether you want to include all exceptions or only a specific type of exception in the report.
A S 01 02 03 04 05 06 07 08 09
Include all exceptions. Include only a specific type of exception. No billing address. Trail in activity. Trail out activity. Billing minimum not reached. Budget exceeded in total. Line item budget exceeded. Expenses not included in format. Billing items on hold. Billing Process cannot determine which event record to select or what type of bill to produce.
Exception Code
No
Number representing the exception you want to include in the report. This parameter is required if Exception Option = S.
4-423
November 2010
Report Sample
FRRBEXC 4.0
Banner University (sctmhp5) Billing Exception Report As of 31-MAR-2000 Trail In Activity FROM DATE 01-JUN-99 01-JUN-99 TO DATE 30-JUN-99 30-JUN-99 DOC CODE J0000127 J0000127 FUND CODE FUND4 FUND4 ORG CODE 11004 11004 ACCT CODE 6111 7523 PROG CODE 10 10
04-DEC-2000 14:18:45 PAGE 1
Exception: 2 GRANT CODE G00000004 G00000004 Exception: 4 GRANT CODE G00000004 FROM DATE 01-JUN-99
BILL AMOUNT 2000 800
Budget Line Exceeded TO DATE 30-JUN-99 FUND CODE FUND4 ORG CODE 11004 ACCT CODE 6111 PROG CODE 10 BUDG AMOUNT 2000 BILL AMOUNT 6300
* * * REPORT CONTROL INFORMATION (frrbexc release 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Seq No: PMS : Grant Code: To Date: Exception Option: Exception Code: Exception Code: Exception Code: Exception Code: Exception Code: Exception Code: Exception Code: Exception Code: Line Count: Value ________________ All 31-MAR-2000 A 1 2 3 4 5 6 7 8 55 Message ____________________________________________________________
All Exceptions Bill without billing address Trail In Activity Billing Item on Hold Budget Line Exceeded Budget Exceeded in total Billing Minimum not reached Expenses not included in format Trail Out Activity Number of lines per page
4-424
November 2010
Grant Budget Report (FRRBUDG)

Description
The Grant Budget Report displays a specific budget, or a series of budget iterations that have been created on the Grant Budget Form (FRABUDG) for a specific grant. This report displays a breakdown of grant budget information by fund, organization, program, activity, and location for each account code in the budget. The report will also display indirect cost (F & A) and cost share amounts.
Parameters
Name
Required?
Description
Values
Grant Grant Budget Option
Yes No
User-defined code representing a grant. Way you want to enter grant budget code(s). A R W S Automatically enter all grant budget codes. Enter a range of grant budget codes. Search for a specific grant budget code using a wildcard. Enter a specific grant budget code.
Grant Budget Code
No
User-defined code identifying the budget for a specific grant. Enter only if Grant Budget Code Option = S. Partial grant budget code that contains a wildcard (* or %). Enter only if Grant Budget Code Option = W. First grant budget code in a series. Enter only if Grant Budget Option = R. Last grant budget code in a series. Enter only if Grant Budget Option = R.
Grant Budget Wildcard
No
Grant Budget Code From Grant Budget Code To
No No
4-425
November 2010
Report Sample
19-JAN-2001 14:14:29 GRANT: GRNTFD01 BUDGET CODE: FISCAL COAS: FUND: ORGN: PROG: ACTV: LOCN: B GRNT1 142071 10 Dimpled golf balls Budget for golf balls
Banner University (sctmhp5) GRANT BUDGET REPORT PROPOSAL: PROPOSAL BUDGET CODE: PROPFD01 FISCAL
PAGE 1 FRRBUDG
Banner University Fund for Grant 1 Office of Athletic Director Instruction
ACCOUNT 6111 6121 6200CA 6220 7210 7720 7730 7750
TITLE Salaries-Faculty Wages-Full Time Fringe Benefits - Clearing Account Health Ins Premiums Office Supplies Legal Accounting Other
BUDGET AMOUNT 16,500 5,500 12,000 7,975 2,500 6,000 3,850 591 54,916 54,916 54,916 54,916
COST SHARING 13,500 4,500 0 6,525 2,500 6,000 3,850 591 37,466 37,466 37,466 37,466
PROJECT VALUE 30,000 10,000 12,000 14,500 5,000 12,000 7,700 1,182 92,382 92,382 92,382 92,382
ORGN TOTAL: FUND TOTAL: BUDGET TOTAL: GRANT TOTAL:
* * * Report Control Information (frrgitd release 3.1) * * * Parameter Name ----------------------------Parameter Seq No Grant Budget Option Line Count Value -------------------GRNTFD01 A 55 Message ----------------------------All Budgets Chosen number of lines per page
4-426
November 2010
Canadian Standard Report Form (FRRCNSF)

Description
The Canadian Standard Report Form prints grant billing information in a format customized for Canadian institutions. It is an Oracle report. After you run the Research Accounting Report Process (FRRGRPT), you can run this report from the Standard Bill and Reports Form (FRABRUN). You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this report for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a report that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a report that summarizes all grants with that PMS code or producing a separate report for each grant. The printed size of this bill is 8.5 by 14 inches.
Parameters
Name
Required?
Description
Values
PMS Code
No
Grant Code Single/Multiple Bill(s)
No No
Period To Date
Yes
DD-MON-YYYY
4-427
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Format
Yes
Destination Type
Yes
Destination Name
No
Execution Mode
Yes
Batch Runtime
4-428
November 2010
Parameters (cont)
Name
Required?
Description
Values
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default) No Do not display Report Parameters form.
Yes Show Report Value Window No Do not display Report Value window.
4-429
November 2010
Research Accounting Conversion Report (FRRCONV)

Description
The Research Accounting Conversion Report prints indirect cost (F & A) and cost share data.
Parameters
Name
Required?
Description
Values
Indirect Cost/Cost Share/ Yes Both
Type of data you want to include in the report.
I C B
Include indirect cost data. Include cost share data. Include both indirect cost and cost share data.
4-430
November 2010
Report Sample
FRRCONV
Banner University Research Accounting Conversion Report
06/18/1996 14:21:49 PAGE 1
Chart of Accounts: A Active Status: A Indirect Cost Code: FEDGRT Title: Indirect Costs-Federal Grants Dates --> Last Activity: 29-MAR-1996 Effective: 01-JUL-1994 Termination: Next Change: Indirect Account : 6180 Include Account Range: I Basis: S Rate: 35.000 Memo: N --------------------- Account Ranges --------------------From Account 5000 To Account 5300 Override Percent
------------------- Distribute Results To ------------------Percent 100.000 Index Fund 1000 Orgn 210 Acct 4330 Prog 610 Actv Locn
Chart of Accounts: A Active Status: A Indirect Cost Code: MBRS1 Title: Bio-Research (MBRS) Indirect Cost Dates --> Last Activity: 04-APR-1995 Effective: 01-JUL-1994 Termination: Next Change: Indirect Account : 6180 Include Account Range: I Basis: S Rate: 80.000 Memo: N --------------------- Account Ranges --------------------From Account 5000 5300 5500 5600 6000 To Account 5299 5399 5500 5600 9999 Override Percent 0.000 0.000 0.000 0.000
------------------- Distribute Results To ------------------Percent 100.000 Index Fund 1012 Orgn 291 Acct 4330 Prog 620 Actv Locn
4-431
November 2010
Grant Events Report (FRREVNG)

Description
The Grant Events Report prints a list of events associated with a grant. You can view events for a specific personnel indicator, a specific time period, a range of grants, a specific grant, or a selection of grants. You can also view events that are pending, satisfied, or both. This report displays both the status description and the alternate description, when available. The alternate description is appended to the default description and the text displays under the DESCRIPTION heading on the report. The format of the display may be selected by choosing a Report Option. One option displays the responsible organization, the grant, and the due dates for each event. With this option, you can also specify an organization code or a range of organizations. A second option displays events by grant code.
Parameters
Name
Required?
Description
Values
Report Option
Yes
Way in which you want to sort events.
1 2 3
Sort by responsible organization. Sort by grant. Sort by PMS code.
Begin Date End Date Personnel Indicator Event Code Value Indicator
No No Yes No Yes
First date you want to include in the report. Last date you want to include in the report. Personnel ID of the person for whom you want to view events. User-defined code representing an event. You may enter a partial event code with a wildcard (* or %). Type of events you want to include in the report.
DD-MON-YYYY DD-MON-YYYY Default = 001 (Principal Investigator) Default = All events A P C S Include all events. Include only pending events. Include only cancelled events. Include only satisfied events.
4-432
November 2010
Parameters (cont)
Name
Required?
Description
Values
Grant Chart of Accounts Responsible Orgn Option
No Yes No
User-defined code representing a grant. You may enter a partial grant code with a wildcard (* or %). User-defined code representing an accounting or reporting entity. Way you want to enter organization code(s).
Default = All grants
A R W S
Automatically enter all organization codes. Enter a range of organization codes. Search for a specific organization code using a wildcard. Enter a specific organization code.
From Responsible Orgn To Responsible Orgn Responsible Orgn
No No No
First organization code in a series. Enter only if Responsible Orgn Option = R. Last organization code in a series. Enter only if Responsible Orgn Option = R. User-defined code representing an administrative office responsible for a grant. Enter only if Responsible Orgn Option = W or S. You may use a wildcard (* or %) if Responsible Orgn Option = W.
4-433
November 2010
Report Sample
PAGE 6 REPORT : FRREVNG
Development Grant Events Report Reporting Period: 01-MAY-2002 To: 31-MAY-2002 10 Biomedical Engineering PROPOSAL: CWP203
COA: B
RESPONSIBLE ORGN:
GRANT: CWG7272
Innovative MRI Research Technology JNS Smith, Joseph N DUE DATE 01-MAY-2002 08-MAY-2002 15-MAY-2002 22-MAY-2002 STATUS P Pending P Pending P Pending P Pending
Innovative MRI Research Technology
PRIMARY INVESTIGATOR : EVENT CERT CERT EVAL FINR DESCRIPTION
RESPONSIBLE USER ASMITH ASMITH ASMITH ASMITH
APPROVED BY ASMITH ASMITH ASMITH ASMITH
Certification Required on animal use studies Certification Required on human use studies Evaluation of costs based on NSF conditions Financial Report due at month end
4-434
November 2010
Report Sample (Summary Page)
PAGE 17 REPORT : FRREVNG
Development Grant Events Report Reporting Period: 01-MAY-2002 To: 31-MAY-2002 * * * REPORT CONTROL INFORMATION (frrevng release 5.4) * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Parameter Sort Option: Period Begin Date: Period End Date: Indicator Option: Event Option: Grant Option: Events Satisfaction Indicator: Chart of Accounts: Organization Option: Line Count:
Value ________________ 803568 1 01-MAY-2002 31-MAY-2002 001 A A A B A 55
Message ____________________________________________________________ Sort by Responsible Orgn/Grant/Due Date Primary Investigator All Events All Grants All events(satisfied and unsatisfied) All Organizations Chosen number of lines per page
4-435
November 2010
Proposal Events Report (FRREVNP)

Description
The Proposal Events Report prints a list of events associated with a proposal. You can view events for a specific personnel indicator, a specific time period, a range of proposals, a specific proposal, or a selection of proposals. You can also view events that are pending, satisfied, or both. This report displays both the event description and the alternate description, when both are available. The alternate description is appended to the default description and the text displays under the DESCRIPTION heading on the report. The format of the display may be selected by choosing a Report Option. One option displays the responsible organization, the proposal, and the due dates for each event. With this option, you can also specify an organization code or a range of organizations. A second option displays events by proposal code.
Parameters
Name
Required?
Description
Values
Report Option
Yes
Way in which you want to sort events.
1 2
Sort by responsible organization. Sort by proposal.
Begin Date DD-MON-YYYY End Date DD-MON-YYYY Personnel Indicator Event Code
No
First date you want to include in the report.
DD-MON-YYYY
No
Last date you want to include in the report.
DD-MON-YYYY
Yes No
Personnel ID of the person for whom you want to view events. User-defined code representing an event. You may enter a partial event code with a wildcard (* or %).
Default = 001 (Principal Investigator) Default = All events
4-436
November 2010
Parameters (cont)
Name
Required?
Description
Values
Value Indicator
Yes
Type of events you want to include in the report.
A P C S
Include all events. Include only pending events. Include only cancelled events. Include only satisfied events.
Proposal
No
User-defined code representing a proposal. You may enter a partial proposal code with a wildcard (* or %). User-defined code representing an accounting or reporting entity. Way you want to enter organization code(s).
Default = All grants
Chart of Accounts Responsible Orgn Option
Yes No
A R W S
Automatically enter all organization codes. Enter a range of organization codes. Search for a specific organization code using a wildcard. Enter a specific organization code.
From Responsible Orgn To Responsible Orgn Responsible Orgn
No No No
First organization code in a series. Enter only if Responsible Orgn Option = R. Last organization code in a series. Enter only if Responsible Orgn Option = R. User-defined code representing an administrative office responsible for a grant. Enter only if Responsible Orgn Option = W or S. You may use a wildcard (* or %) if Responsible Orgn Option = W.
4-437
November 2010
Report Sample
PAGE 1 REPORT : FRREVNP
Development Proposal Events Report Reporting Period: 01-FEB-2002 To: 31-MAY-2002 10 Biomedical Engineering TOTAL REQUESTED:
COA: B
RESPONSIBLE ORGN: CWP203
PROPOSAL: GRANT:
Innovative MRI Research Technology
300,000.00
PRIMARY INVESTIGATOR : EVENT BUDG CTRV REV SUB DESCRIPTION
JNS Smith, Joseph N DUE DATE 01-FEB-2002 10-FEB-2002 15-MAR-2002 30-APR-2002 STATUS P Pending P Pending P Pending P Pending RESPONSIBLE USER ASMITH ASMITH ASMITH ASMITH APPROVED BY ASMITH ASMITH ASMITH ASMITH
Budget due for approval Certification requirements require review by PI Review proposal & budget prior to submission Submit proposal upon approval
4-438
November 2010
Report Sample (Summary Page)
PAGE 3 REPORT : FRREVNP
Development Proposal Events Report Reporting Period: 01-FEB-2002 To: 31-MAY-2002 * * * REPORT CONTROL INFORMATION (frrevnp release 5.4) * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Parameter Sort Option: Period Begin Date: Period End Date: Indicator Option: Event Option: Proposal Option: Events Satisfaction Indicator: Chart of Accounts: Organization Option: Line Count:
Value ________________ 803543 1 01-FEB-2002 31-MAY-2002 001 A A A B A 55
Message ____________________________________________________________ Sort by Responsible Orgn/Proposal/Due Date Primary Investigator All Events All Proposals All events All Organizations Chosen number of lines per page
4-439
November 2010
Fund Exception Report (FRRFEXC)

Description
The Fund Exception Report prints a list of all grant funds that do not have information stored in the Accrual Acct and Revenue Acct fields on the Fund Code Maintenance Form (FTMFUND). When you run the Research Accounting Billing Process (FRRBILL), Banner uses data from the Billing Detail Table (FRRBDET) to process bills. Grant funds that do not have the Accrual Acct and Revenue Acct fields populated on the Fund Code Maintenance Form (FTMFUND) will not have rows in the Billing Detail Table (FRRBDET). Therefore, you must ensure that all grant funds have information stored in these fields before you run the Research Accounting Billing Process.
Parameters
Name
Required?
Description
Values
Charts of Accounts Fund Range
Yes No
User-defined code representing an accounting or reporting entity. Funds to include on the report. R A S W Range of funds All funds Specific fund Wildcard characters
From Fund To Fund Fund Code
No No No
Fund code to begin with. Fund code to end with User-defined code representing a fund from which expenses are paid. A wildcard (* or %) is allowed. Leave this parameter blank to include all fund codes in the report. Last date you want to include in the report.
Any valid fund code. Any valid fund code.
As of Date
No
DD-MON-YYYY
4-440
November 2010
Report Sample
FRRFEXC 4.0
Banner University Fund Exception Report As of 28-AUG-1998
28-AUG-1998 14:07:27 PAGE 1
Chart of Accounts: 2 GRANT CODE G00000273 G00000273 G00000004 G00000273 FUND CODE ABAL60 CAPFND F4 FXSRC1
Banner University TITLE Research Research Research Research on on on on Arthritis Lyme Disease cure for Aids Lung Cancer
* * * REPORT CONTROL INFORMATION (frrfexc release 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Seq No: Chart of Accounts: Fund Code: Number of lines per page Value ________________ 69523 2 A As of Date: Line Count: Message ____________________________________________________________ ALL 28-AUG-1998 55
4-441
November 2010
Federal Financial Report (FRRFFRR)

Description
The Federal Financial Report (FFR) is a reporting format announced by the Office of Management and Budget (OMB) for the financial status of grants and cooperative agreements. This reporting format streamlines and simplifies the reporting of each grant, or multiple grants, to their respective Federal agencies. The FFR format is intended to replace both the Federal Cash Transactions Report (SF272) and the Financial Status Report (SF269) by October 2009. The Banner Federal Financial Report mimics the Federal Financial Report format. After you run the Research Accounting Report Process (FRRGRPT), you can run the Federal Financial Report from the Federal Financial Report Form (FRAFFRR) or from the Run Standard Bills and Reports Form (FRABRUN). You can also run the Federal Financial Report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this report for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a report that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a report that summarizes all grants with that PMS code or producing a separate report for each grant.
Note To run this report, Oracle Reports must be installed on your computer. This report will not run from a web-enabled form.
Federal Financial Report (FRRFFRR) Chart The following chart identifies the information that can be collected and included on the Federal Financial Report. The numbers listed in the first column correlate to the numbers on the report.
4-442
Banner Finance 8.5 User Guide Federal Financial Report - Functional
November 2010
FFR Number Field
Description
1 2
Federal Agency and Organizational Element to Which Report is Submitted Federal Grant or Other identifying Number Assigned by Federal Agency Recipient Organization
The name of the federal agency is displayed as retrieved from the Grants table. For a single award or grant, the Sponsor ID is displayed from the Grant Maintenance Form (FRAGRNT). For multiple awards or PMS, this field is blank. The organization name as taken from the Payee name on the Research Accounting System Control Form (FRASYSC). The address is displayed from the Principal Investigators default address type and sequence number as defined on the Personnel window of the Grant Maintenance Form (FRAGRNT). If these values are null, the address comes from FRASYSC.
4a 4b 5 6 7 8a 8b
DUNS Number EIN Recipient Account Number or Identifying Number Report Type Basis of Accounting Project/Grant Period, From: (Month, Day, Year) Project/Grant Period, To: (Month, Day, Year)
The Data Universal Numbering System (DUNS) number as valued on the Research Accounting System Control Form (FRASYSC). The Employer Identification Number (EIN) as defined on the 1099-MISC Type Magnetic Type Transmitter Data Form (FOA1099). For a single grant, this is the Grant Code established on the Grant Maintenance Form (FRAGRNT). For multiple grants or PMS, this field is blank. Options for this check box include Quarterly, Semi-Annual, Annual, or Final. Your method of accounting will be is pulled from the chart record (Chart of Accounts Code Maintenance Form, FTMCOAS). The grant project start date as defined on the Grant Maintenance Form (FRAGRNT). The grant project end date as defined on the Grant Maintenance Form (FRAGRNT).
4-443
November 2010
FFR Number Field
Description
9 10a 10b
Reporting Grant Period End Date: (Month, Day, Year) Cash Receipts Cash Disbursements
The reporting period-to-date from the Research Accounting Report Process (FRRGRPT). The cumulative amount of payments and transfers received to date from the Research Accounting Account Detail Table (TRRACCD). The cumulative amount of expenditures (direct and indirect) from the Research Accounting Transaction Detail Table (FRRBDET) as of the reporting period to date. Calculated field: 10a - 10b. For a single grant, this value is derived from the Cumulative amount as defined on the header window of the Grant Maintenance Form (FRAGRNT). For PMS codes, this field is blank.
10c 10d
Cash on hand Total Federal Funds Authorized
10e
Federal Share of Expenditures
This amount equals the total charges or expenditures from the Research Accounting Transaction Detail Table (FRRBDET), both direct and indirect, as of the reporting period to date. Total commitments, both reservations and encumbrances, from the Grant Ledger Table (FRRGRNL) for the Grant Code as of the reporting period to date. Calculated field: 10e + 10f. Calculated field: 10d - 10g. This value comes from the Total Recipient Share field on the Grant Maintenance Form (FRAGRNT). If Banner cost sharing is being calculated, this field holds any cost share expense from the Research Accounting Transaction Detail Table (FRRBDET). Calculated field: 10i - 10j.
10f
Federal share of unliquidated obligations
10g 10h 10i 10j 10k
Total Federal share Unobligated balance of Federal funds Total recipient share required Recipient share of expenditures Remaining Recipient Share to be Provided
4-444
November 2010
FFR Number Field
Description
10l 10m 10n 10o 11a 11b 11c 11d 11e 12 13a
Total Federal Program Income Earned Program Income Expended in Accordance with the Deduction Alternative Program Income Expended in Accordance with the Addition Alternative Unexpended program income Type of Rate Rate Base Total Amount Federal Share Remarks Typed or Printed Name and Title of Authorized Certifying Official Signature of Authorized Certifying Official Telephone
This field always displays a value of zero. It can be updated on FRAFFRR. This field always displays a value of zero. It can be updated on FRAFFRR. This field always displays a value of zero. It can be updated on FRAFFRR. Calculated: 10l - 10m or 10n. The Indirect Cost Rate type comes from the Research Accounting System Control Form (FRASYSC). For single grants, the rate comes from the Indirect Cost Rate as defined on the grant record. Total direct costs as of the reporting period to date. The total amount of indirect costs as taken from the Research Accounting Transaction Detail Table (FRRBDET). The total federal share of indirect costs. Text from the Entity Text Entry Form (FOAETXT). This field extracts this information from the Personnel window of the Grant Maintenance Form (FRAGRNT) when the Billing or Report Format field contains a value of FFR. This field is left blank. This information comes from the Personnel window of the Grant Maintenance Form (FRAGRNT) when the Billing or Report Format field contains a value of FFR. This information comes from the Personnel window of the Grant Maintenance Form (FRAGRNT) when the bill or report format code is defined as FFR.
13b 13c
13d
E-mail address
4-445
November 2010
FFR Number Field
Description
13e 14
Date Report Submitted Agency Use Online
Date the report was executed. This field is reserved for agency use.
The following chart contains the parameters used to generate this report.
Parameters
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. User-defined code identifying a grant. Last date of the reporting period you want to include in the output. Reporting periods are defined on the Grant Events Assignment Form (FRAEVGA). Format for the report output. The default value is PDF. DD-MON-YYYY
Grant Code Period To Date
No Yes
Destination Format
Yes
4-446
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Type
Yes
Destination Name
No
Execution Mode
Yes
Batch Runtime
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes.
4-447
November 2010
Parameters (cont)
Name
Required?
Description
Values
Parameter Form Designator
Yes
Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache.
Yes Display Report Parameters form. (default value) No Do not display Report Parameters form. Yes Show Report Value Window No Do not display Report Value Window
Show Report Value Window
Yes
Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL.
4-448
November 2010
Report Sample Executed by Grant Code
4-449
November 2010
Report Sample Executed by PMS Code
4-450
November 2010
Attachment Used When Reporting Multiple Grants
4-451
November 2010
Grant Budget Status Report (FRRGBFY)

Description
The Grant Budget Status Report displays operating account information for a grant for the specified fiscal year. This report displays budget information, year-to-date activity, commitments, and a calculated available balance. The report retrieves information from the Operating Ledger. The report may be run by chart of accounts for all grants, by a range of grants, or by a selection of grants. You can also include accrual period activity on the report.
Parameters
Name
Required?
Description
Values
Fiscal Yr Chart of Accounts As of Date Grant Option
Yes Yes No No
Two-digit code representing the year of a grant budget. User-defined code representing an accounting or reporting entity. Last date you want to include in the report. Way you want to enter grant code(s).
YY
DD-MON-YYYY A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From Grant To Grant Wildcard
No No No
First grant code in a series. Enter only if Grant Option = R. Last grant code in a series. Enter only if Grant Option = R. Partial grant code that contains a wildcard (* or %). Enter only if Grant Option = W.
4-452
November 2010
Parameters (cont)
Name
Required?
Description
Values
Specific Grant Accrual Period
No No
User-defined code identifying a grant. Indicates whether to include detailed information about accrual periods in the report. Y N Include accrual period information. Do not include accrual period information.
4-453
November 2010
Report Sample
14:02:24 FISCAL YEAR 00 CHART: FUND: PRED ORG: ORGN: PI/MANAGER: AGENCY: ACCOUNT 5520 TOTAL 6112 TOTAL B 2157 110 11001 Banner University Early Childhood Diseases School of Arts and Sciences Dean Sch of Arts and Sciences
Banner University (sctmhp5) Grant Budget Status Report AS OF 04-JAN-2001 GRANT: 215601 PROJECT PERIOD:
PAGE 1 FRRGBFY Early childhood Diseases 01-MAY-1995 - 30-APR-1996
Cynthia A. Pavlicek Department of Health and Human Services ACCOUNT TITLE ADJUSTED BUDGET .00 .00 .00 .00 CURRENT PERIOD ACTIVITY .00 .00 .00 .00 ACTIVITY 5,419.95 5,419.95 5,419.95 5,419.95 COMMITMENTS .00 .00 .00 .00 AVAILABLE BALANCE -5,419.95 -5,419.95 -5,419.95 -5,419.95
Direct Income Grants and Contracts Salaries-Professional Staff Salaries and Wages
ORGANIZATION TOTAL 11001 Dean Sch of Arts and Sciences 50 Revenues 60 Labor NET
.00 .00 .00
.00 .00 .00
5,419.95 5,419.95 .00
.00 .00 .00
-5,419.95 -5,419.95 .00
* * * REPORT CONTROL INFORMATION (frrgbfy release 4.0) * * * Parameter Name _____________________________ Parameter Seq No: Fiscal Year: Chart of Accounts: As of Date: Grant Option: Accrual Period: Value ________________ 00 B 04-JAN-2001 A Y Message ____________________________________________________________
All Grants
4-454
November 2010
Generic Bill Form (FRRGENB)

Description
The Generic Bill Form prints bills in a format customized by your institution on the Billing/Report Format Maintenance Form (FTMBFRM). It is an Oracle report. After you run the Research Accounting Billing Process (FRRBILL), you can use the Generic Billing Form (FRAGENB) to print one bill, or you can use the Standard Bill and Reports Form (FRABRUN) to print multiple bills.You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this bill for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a bill that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a bill that summarizes all grants with that PMS code or producing separate bills for each grant. If you enter Y in the Details parameter, Banner will print a two-page bill. The first page will contain details for each expenditure group defined on the Bill/Report Format Maintenance Form (FTMBFRM). The second page will contain details for each account code in each expenditure group.
Note To run this bill, Oracle Reports must be installed on your computer. This bill will not run from a web-enabled form.
Parameters
Name
Required?
Description
Values
PMS Code
No
User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. User-defined code identifying a grant. Indicates whether to print one bill summarizing all grants with the specified PMS code or to print one bill for each grant. Enter only if you entered a value in the PMS Code parameter. Invoice number generated by the Research Accounting Billing Process (FRRBILL). M S Print one bill for each grant. Print one bill summarizing all grants.
No No
Invoice Sequence Number
Yes
4-455
November 2010
Parameters (cont)
Name
Required?
Description
Values
Adjustment Number Period To Date
Yes Yes
Number of times the bill has been adjusted. Last date of the billing period you want to include in the output. Billing periods are defined on the Grant Events Assignment Form (FRAEVGA). Amount of detail you want to include in the bill. DD-MON-YYYY
Details
Yes
Generate a bill that contains details for each expenditure group defined on the Bill/Report Format Maintenance Form (FTMBFRM) and details for each account code in each expenditure group. Generate a bill that contains details for each expenditure group defined on the Bill/Report Format Maintenance Form (FTMBFRM).
Destination Format
Yes
Destination Type
Yes
4-456
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Name
No
Execution Mode
Yes
Batch Runtime
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default) No - Do not display Report Parameters form. Yes Show Report Value Window. No Do not display Report Value window.
4-457
November 2010
4-458
Page 1 of 1 Grant Code: GRTB-1 Bill Invoice: 3 Payee Name: Diane Mathews Agency Name: Grant billing agency without LOC Sponsor Id: AIDS3049-56 Period From Date: 29-SEP-98 Period To Date: 29-SEP-98 Group
Salaries Subtotal: Salaries $.00 $1,500.00 $.00 $1,500.00
Budget Amount
Previous Bill Amount
Current Bill Amount

$.00 $.00
Cumulative Bill Amount

$1,500.00 $1,500.00
Report Sample

Other expenses Supplies Subtotal: Other expenses $.00 $.00 $.00 $1,900.00 $1,000.00 $2,900.00 $.00 $.00 $.00 Cost share Subtotal: Cost share $.00 $.00 -$450.00 -$450.00 $.00 $.00 withholding Subtotal: Withholding $.00 $.00 $.00 $.00 $20.00 $20.00 Grant Total $.00 $3,950.00 $20.00
$1,900.00 $1,000.00 $2,900.00
-$450.00 -$450.00
$20.00 $20.00
$3,970.00
29-SEP-98 SIGNATURE TYPED OR PRINTED NAME AND TITLE DATE SUBMITTED PHONE NUMBER
AUDIT ONLY
November 2010
Generic Report Form (FRRGENR)

Description
The Generic Report Form prints grant billing information in a format customized by your institution on the Billing/ Report Format Maintenance Form (FTMBFRM). It is an Oracle report. After you run the Research Accounting Report Process (FRRGRPT), you can use the Generic Report Form (FRAGENR) to print one report, or you can use the Standard Bill and Reports Form (FRABRUN) to print multiple reports. You can also run this report from the Process Submission Controls Form (GJAPCTL). For additional information, refer to the Banner General User Guide. You can run this report for only one PMS code at a time. If you leave the PMS Code and Grant Code parameters blank, Banner will print a report that lists all grants for the specified date. If you enter a value in the PMS Code parameter, you have the option of producing a report that summarizes all grants with that PMS code or producing a separate report for each grant.
Parameters
Name
Required?
Description
Values
PMS Code
No
Grant Code Single/Multiple Bills?
No No
Period To Date
Yes
DD-MON-YYYY
4-459
November 2010
Parameters (cont)
Name
Required?
Description
Values
Destination Format
Yes
Format for the report output. The default value is PDF.
Destination Type
Yes
Destination Name
No
Execution Mode
Yes
How you want this report to run.
Batch Runtime
4-460
November 2010
Parameters (cont)
Name
Required?
Description
Values
Communication Mode
Yes
Communication mode.
Synchronous
Asynchronous Run report behind the scenes. Parameter Form Designator Yes Indicates if you want to display the form that contains all report parameter selections made for the report parameters. For this field to be set to Yes, Destination Type must be set to Cache. Show Report Value Window Yes Indicates if you want to display this window when initiating the report from a link in a form other than GJAPCTL. Yes Display Report Parameters form. (default) No Do not display Report Parameters form. Yes Show Report Value Window No Do not display Report Value window.
4-461
November 2010
4-462
Page 1 of 1 Grant Code: GRTB-2 Payee Name: Diane Mathews Period To Date: Sponsor Id: Previous Report Amount
$.00 $.00
Period From Date: 01-MAR-1998 31-MAR-1998 LYME3049-56
Agency Name: Grant billing agency without LOC Group

Salaries Subtotal: Salaries $270,000.00 $270,000.00
Budget Amount
Current Report Amount

$1,000.00 $1,000.00
Cumulative Report Amount

$1,000.00 $1,000.00
Report Sample

Supplies Other expenses Subtotal: Supplies $.00 $.00 $.00 $.00 $.00 $.00 $1,000.00 $1,300.00 $2,300.00 Cost share Subtotal: Cost share $.00 $.00 $.00 $.00 -$300.00 -$300.00 Grant Total $270,000.00 $.00 $3,000.00
$1,000.00 $1,300.00 $2,300.00
-$300.00 -$300.00
$3,000.00
17-AUG-1998 SIGNATURE Date Report Submitted
Telephone (Area Code, Number, Extension)
November 2010
Grant Inception to Date Report (FRRGITD)

Description
The Grant Inception to Date Report displays operating account information from the inception of a grant to the specified As of Date. This report displays budget information, actual activity, commitments, and a calculated available balance. The report retrieves information from the Grant Ledger. This report may be run by chart of accounts for all grants, by a range of grants, or by a selection of grants. You can also see the breakout of grants information by fund code(s) associated with the grant.
Note Grant transactions that occur after the project end date are not posted in period 14. Instead, the system posts these transactions to the actual grant year and period.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date Enter Grant Option
Yes No No
User-defined code representing an accounting or reporting entity. Last date you want to include in the report. Way you want to enter grant code(s). DD-MON-YYYY A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From Grant To Grant Wildcards
No No No
First grant code in a series. Enter only if Enter Grant Option = R. Last grant code in a series. Enter only if Enter Grant Option = R. Partial grant code that contains a wildcard (* or %). Enter only if Enter Grant Option = W.
4-463
November 2010
Parameters (cont)
Name
Required?
Description
Values
Specific Grants Fund Information
No No
User-defined code identifying a grant. Enter only if Enter Grant Option = S. Type of output you want to generate. Y N Generate output that shows detailed information by fund. Generate output that summarizes information by grant. (default)
4-464
November 2010
Report Sample
04-JAN-2001 14:03:26
Banner University (sctmhp5) Grant Inception to Date Report AS OF 04-JAN-2001 GRANT: 215601 PROJECT PERIOD: Early childhood Diseases 01-MAY-1995 - 30-APR-1996
PAGE 2 FRRGITD
CHART: PI/MANAGER: AGENCY: FUND:
Banner University
Cynthia A. Pavlicek Department of Health and Human Services 2157 Early Childhood Diseases ADJUSTED BALANCE CURRENT PERIOD INCEPTION COMMITMENTS AVAILABLE
TO DATE ACTV. GRANT TOTAL 215601
Early childhood Diseases Revenues Labor
.00 .00 .00
54,495.91 54,495.91 .00
54,495.91 54,495.91 .00
.00 79,317.23 -79,317.23
-54,495.91 -133,813.14 79,317.23
NET
* * * Report Control Information (frrgitd release 4.0) * * * Parameter Name ----------------------------Parameter Seq No Chart of Accounts As of Date Grant Option Fund Info Y or [N] Line Count Value -------------------B 04-JAN-2001 A Y 55 Message -----------------------------
All Grants Include Fund Information Chosen number of lines per page
4-465
November 2010
Grant Expenditures Report (FRRINDC)

Description
The Grant Expenditure Report displays operating account activity by fund, organization, account type, account, and program for a grant, a range of grants, or a selection of grants. This report displays the account title, the account type to which the account code is linked, the total expenditure amount for the specified As of Date, the amount of indirect costs (F & A), and the sum of direct and indirect costs. Totals are also displayed for each fund, organization, account type, and program, with a grand total by grant.
Parameters
Name
Required?
Description
Values
Chart of Accounts As of Date Enter Grant Option
Yes No No
User-defined code representing an accounting or reporting entity. Last date you want to include in the report. Way you want to enter grant code(s). DD-MON-YYYY A R W S Automatically enter all grant codes. Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From Grant To Grant Wildcards Specific Grants
No No No No
First grant code in a series. Enter only if Enter Grant Option = R. Last grant code in a series. Enter only if Enter Grant Option = R. Partial grant code that contains a wildcard (* or %). Enter only if Enter Grant Option = W. User-defined code identifying a grant. Enter only if Enter Grant Option = S.
4-466
November 2010
Report Sample (Page 1 of 2
04-JAN-2001 14:01:19
Banner University (sctmhp5) Grant Expenditures Report AS OF 04-JAN-2001
PAGE 1 FRRINDC
GRANT: 215601 FUND 2157
Early childhood Diseases ORGN 11001 PROG 10 ATYP 61 ATYP TITLE Salaries and Wages TOTAL DIRECT EXPENDITURES OVERHEAD TOTAL EXPENDITURES AMOUNT 6,380.00 6,380.00 .00 6,380.00 154.02 154.02 .00 154.02 14,204.06 14,204.06 .00 14,204.06 29,353.43 -8.00 29,345.43 .00 29,345.43
2157
11002
10
61
Salaries and Wages TOTAL DIRECT EXPENDITURES OVERHEAD TOTAL EXPENDITURES
2157
11003
10
61
2157 2157
11004 11004
10 10
61 62
Salaries and Wages Fringe Benefits TOTAL DIRECT EXPENDITURES OVERHEAD TOTAL EXPENDITURES
4-467
November 2010
04-JAN-2001 14:01:19
Banner University (sctmhp5) Grant Expenditures Report AS OF 04-JAN-2001
PAGE 2 FRRINDC
GRANT: 215601 FUND 2157
Early childhood Diseases ORGN 11008 PROG 10 ATYP 61 ATYP TITLE Salaries and Wages TOTAL DIRECT EXPENDITURES OVERHEAD TOTAL EXPENDITURES AMOUNT 4,104.36 4,104.36 .00 4,104.36 308.04 308.04 .00 308.04
2157
11009
10
61
GRANT TOTAL: 215601
GRANT TOTAL DIRECT EXPENDITURES GRANT TOTAL OVERHEAD GRANT TOTAL EXPENDITURES * * * Report Control Information (frrindc release 4.0) * * *
54,495.91 .00 54,495.91
Parameter Name ----------------------------Parameter Seq No Chart of Accounts As of Date Grant Option Line Count
Value -------------------B 04-JAN-2001 A 55
Message -----------------------------
All Grants Chosen number of lines per page
4-468
November 2010
Grant Billing Preview Report (FRRINVS)

Description
The Grant Billing Preview Report prints a list of all grants that will be selected by the Research Accounting Billing Process (FRRBILL) when its run on the specified date (As of Date parameter). The report includes a list of grants sorted by agency and format code. It also provides the following types of billing information for each grant. Billing end date Retainage amount Payment withholding amount Cumulative amount billed to sponsoring agency Maximum bill amount This report enables you to enter the appropriate parameters in the Research Accounting Billing Process (FRRBILL); therefore, it is recommended that you print this report before you run that process.
Parameters
Name
Required?
Description
Values
As of Date
No
Last date you want to include in the report.
DD-MON-YYYY
4-469
November 2010
Report Sample
FRRINVS 4.0
Banner University (sctmhp5) Research Accounting Billing Preview Report
01/09/2000 11:03:59 PAGE 1
Agency: NIH National Institute of Health Billing Format Code: 270B Request for Advance/Reimbursement Grant Code ---------G00000004 G00000005 G00000006 G00000007 G00000008 SRGR1 Grant Title --------------------------Research on Rheumatoid Arthritis Research on Rheumatoid Arthritis Research on Rheumatoid Arthritis Research on Rheumatoid Arthritis Research on Rheumatoid Arthritis Research on Rheumatoid Arthritis Billing End Date ---------------31-DEC-2000 31-DEC-2000 31-DEC-2000 31-DEC-2000 31-DEC-2000 31-DEC-2000 Retainage Amt ------------0.00 0.00 0.00 0.00 100.00 0.00 Payment W/H ------------0.00 0.00 0.00 0.00 0.00 0.00 Cumulative Billed ----------------420.00 1500.00 0.00 1890.00 2420.00 119320.00 Bill Max Amt ------------1500000.00 1500000.00 1500000.00 1500000.00 1500000.00 1500000.00
* * * REPORT CONTROL INFORMATION (FRRINVS RELEASE 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Parameter Seq No: As of Date: Line Count: Value ________________ 23471 29-FEB-2000 55 Message ____________________________________________________________ Chosen number of lines per page
4-470
November 2010
Grant/Budget Error Printing (FRRTRNR)

Description
The Grant Interface enhancement produces an error report based on the contents of the FRCTRNR collector table. For information about the Grant Interface, refer to the Grant Budget Interface Process (FRPBINF) and the Grant Interface Process (FRPGINF) described in this chapter, or to Chapter 2, Processing.
Parameters
Name
Required?
Description
Values
Grant, Budget or All Errors
Yes
Prints an error report based on the contents of the FRCTRNR collector table.
G B A
Grant interface errors Budget interface errors All
4-471
November 2010
Grants Aging Analysis Report (TRRAGES)

Description
The Grant Aging Analysis Report prints information about the aging of billed receivables. You can run this report for unbilled charges to see the aging of charges that have been incurred but not billed. You can also run this report for billed charges that have not been paid. The Report Type parameter enables you to specify whether to include invoice detail in the report.
Parameters
Name
Required?
Description
Values
Report Option
No
Type of charges to include in the report.
1 2 3
Include unbilled charges. Include billed charges. (default value) Include both billed and unbilled charges. Enter PMS code(s). Enter grant code(s).
Selection Option
No
Indicates whether you want to enter PMS code(s) or grant code(s). User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. Enter only if Selection Option = P. Way you want to enter grant code(s). Enter only if Selection Option = G.
P G
PMS Code
No
Grant Option
No
A R W S
Automatically enter all grant codes. (default value) Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From
No
First grant code in a series. Enter only if Grant Option = R.
4-472
November 2010
Parameters (cont)
Name
Required?
Description
Values
Grant To Wild Card Specific Grant Code As of Date
No No No No
Last grant code in a series. Enter only if Grant Option = R. Partial grant code that contains a wildcard (* or %). Enter only if Grant Option = W. User-defined code identifying a grant. Enter only if Grant Option = S. Last date you want to include in the report. DD-MON-YYYY Default = system date
Date Range 1 Date Range 2 Date Range 3 Date Range 4 Date Range 5 Report Type
No No No No No No
Number of days before the As of Date to include in the first aging period. Number of days before the As of Date to include in the second aging period. Number of days before the As of Date to include in the third aging period. Number of days before the As of Date to include in the fourth aging period. Number of days before the As of Date to include in the fifth aging period. Specifies whether you want to display aging information for grants or invoices.
Default = 30 Default = 60 Default = 90 Default = 120 Default = 150 S D Display aging information for grants. Display aging information for invoices.
4-473
November 2010
Report Sample
TRRAGES 4.0
Banner University (sctmhp5) Billed Aging Analysis Report Detail mode AS OF 04-JAN-2001
04-JAN-2001 08:56:52 PAGE 1
AGENCY: NIH TITLE: National Institute of Health GRANT CODE --------G00000019 G00000019 TOTAL FOR AGENCY: INV NUM -------1 2 0 To 60 --Days------------1,040.00 3,000.00 4,040.00 61 To 90 --Days-------------.00 .00 .00 91 To 120 --Days-------------.00 .00 .00 121 To 150 --Days-------------.00 .00 .00 151 To 180 --Days-------------.00 .00 .00 Future Balance ------------.00 .00 .00
* * * REPORT CONTROL INFORMATION (TRRAGES RELEASE 4.0) * * * Parameters have been entered from Host Prompt. Report Option: Billed Charges Selection Option: Grant Code AS OF DATE: 04-JAN-2001 REPORT TYPE Detail Mode RANGE DATE 1: 60 RANGE DATE 2: 90 RANGE DATE 3: 120 RANGE DATE 4: 150 RANGE DATE 5: 180 ERROR MESSAGE: NUMBER OF RECORDS PRINTED : 2
4-474
November 2010
Collections Report (TRRCOLL)

Description
The Collections Report prints information about collection efforts that have been entered on the Grant Billing Collections Form (FRACOLL). You can run this report by agency, by grant, by bill invoice number, by User ID, or by bill status. This report sorts collection efforts by grant within a sponsoring agency.
Parameters
Name
Required?
Description
Values
Report Option
Yes
Indicates whether to generate reports by agency code, by grant code, or both.
A G L
Generate reports by agency code. Generate reports by grant code. Generate reports by agency and grant codes. (default value) Automatically enter all agency codes. (default) Enter a specific agency code.
Agency Option
No
Way you want to enter agency code(s).
A S
Agency Codes Grant Option
No No
User-defined code representing a sponsoring agency. Enter only if Agency Option = S. Way you want to enter grant code(s). A R W S Automatically enter all grant codes. (default) Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant_from Grant_to
No No
First grant code in a series. Enter only if Grant Option = R. Last grant code in a series. Enter only if Grant Option = R.
4-475
November 2010
Parameters (cont)
Name
Required?
Description
Values
Grants Wild Grants Specific Bill Invoice Number Bill Status
No No No No
Partial grant code that contains a wildcard (* or %). Enter only if Grant Option = W. User-defined code identifying a grant. Enter only if Grant Option = S. Number that uniquely identifies a bill. Generated by the FRRBILL process. Type of bills you want to include in the report. O C B Include paid bills (Status = Open). Include unpaid bills (Status = Closed). Include both paid and unpaid bills (default).
User ID
No
Identification code of the person running the report.
4-476
November 2010
Report Sample
TRRCOLL 4.0
Banner University (sctmhp5) Collections Report AS OF 08-JAN-2000
08-JAN-2000 16:32:45 PAGE 1
AGENCY: NIH National Institute of Health USER ID: FIMSUSR Grant Code G00000013 G00000014 G00000015 Invoice No 2 2 3 Code FIRST FIRST FIRST Code Description This is the first call This is the first call This is the first call Amount 300.00 500.00 400.00 Status Open Open Open Contact Date 08-JAN-2000 08-JAN-2000 08-JAN-2000
USER ID: SYSTEST2
Grant Code G00000002
Invoice No 1 -
Code FIRST
Code Description This is the first call
Amount 300.00
Status Open
Contact Date 05-JUL-1999
* * * REPORT CONTROL INFORMATION (TRRCOLL RELEASE 4.0) * * * Parameter name _____________________________ Parameter Seq no: Report options: Agency option: Bill Invoice number: User Id: Bill Status: NUMBER RECORDS PRINTED : 4 Parameters have been entered from Host Prompt. Value Message ________________ ____________________________________________________________ 23111 By Agency All Agencies
4-477
November 2010
TRRCOLL 4.0
Banner University (sctmhp5) Collections Report AS OF 08-JAN-2000
08-JAN-2000 16:32:45 PAGE 1
AGENCY: NIH National Institute of Health USER ID: FIMSUSR Grant Code G00000013 G00000014 G00000015 Invoice No 2 2 3 Code FIRST FIRST FIRST Code Description This is the first call This is the first call This is the first call Amount 300.00 500.00 400.00 Status Open Open Open Contact Date 08-JAN-2000 08-JAN-2000 08-JAN-2000
USER ID: SYSTEST2
Grant Code G00000002
Invoice No 1 -
Code FIRST
Code Description This is the first call
Amount 300.00
Status Open
Contact Date 05-JUL-1999
* * * REPORT CONTROL INFORMATION (TRRCOLL RELEASE 4.0) * * * Parameter name _____________________________ Parameter Seq no: Report options: Agency option: Bill Invoice number: User Id: Bill Status: NUMBER RECORDS PRINTED : 4 Parameters have been entered from Host Prompt. Value Message ________________ ____________________________________________________________ 23111 By Agency All Agencies
4-478
November 2010
Grant Reconciliation Report (TRRRCON)

Description
The Grant Reconciliation Report reconciles data between the Accounts Receivable module and the Banner Finance System for Grant Billing transactions only. You can reconcile data by chart of accounts, by grant code, or by PMS code.
Parameters
Name
Required?
Description
Values
Selection Option
Yes
Type of data you want to reconcile.
Reconcile the summary of billed charges in the TRRACCD table with the details of billed charges in the FRRBDET table. Banner will not reconcile grants that have a fixed billing schedule. Reconcile billed charges in the TRRACCD table with the billed receivables account in the General Ledger. Reconcile payments in the TRRACCD table with payments that were posted to the General Ledger. List all payments that have been entered in the Accounts Receivable module that have not been fed to the Banner Finance System.
As of Date
No
Last date of the billing period you want to reconcile. DD-MON-YYYY Default = system date
4-479
November 2010
Parameters (cont)
Name
Required?
Description
Values
Report Option
Yes
Indicates whether to reconcile data by chart of accounts code, grant code, grants out of balance, PMS code, or PMS out of balance.
1 2 3 4 5
Reconcile data by chart of accounts code only. Reconcile data by grant code only. Reconcile data by grants out of balance. Reconcile data by PMS code only. Reconcile data by PMS out of balance.
No No
User-defined code representing an accounting or reporting entity. Enter only if Report Option = 1. Way you want to enter grant code(s). Enter only if Report Option = 2. A R W S Automatically enter all grant codes (default) Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From Grant To Grants Wild Grants Specific
No No No No
First grant code in a series. Enter only if Grant Option = R. Last grant code in a series. Enter only if Grant Option = R. Partial grant code that contains a wildcard (* or %). Enter only if Grant Option = W. User-defined code identifying a grant. Enter only if Grant Option = S.
4-480
November 2010
Parameters (cont)
Name
Required?
Description
Values
PMS Option
No
Way you want to enter PMS code(s). Enter only if Report Option = 4.
A R W S
Automatically enter all PMS codes. Enter a range of PMS codes. Search for a specific PMS code using a wildcard. Enter a specific PMS code.
PMS From PMS To PMS Wildcard PMS Specific
No No No No
First PMS code in a series. Enter only if PMS Option = R. Last PMS code in a series. Enter only if PMS Option = R. Partial PMS code that contains a wildcard (* or %). Enter only if PMS Option = W. User-defined code representing one or more grants from the same sponsoring agency with the same reimbursement requirements. Enter only if PMS Option = S.
4-481
November 2010
Report Sample
TRRRCON 4.0
Banner University (sctmhp5) Reconciliation Report AS OF 04-JAN-2001
04-JAN-2001 08:53:50 PAGE 1
Charge/General Ledger reconciliation Grant code G00000004 G00000005 G00000005 G00000006 G00000007 G00000013 G00000013 G00000019 SRGR1 Fund code FUND4 F5 F5-1 F6 F7 F13 F13-1 F19 SRF1 Account code 1321 1321 1321 1321 1321 1321 1321 1321 1321 G/L Balance 120.00 1,000.00 2,500.00 5,950.00 2,690.00 1,620.00 1,260.00 4,040.00 5,620.00 AR balance 120.00 1,000.00 2,500.00 5,950.00 2,690.00 1,620.00 1,260.00 4,040.00 5,620.00 Message
* * * REPORT CONTROL INFORMATION (TRRRCON RELEASE 4.0) * * * Parameters have been entered from Host Prompt. AS OF DATE: 04-JAN-2001 REPORT SELECTION: Charge/General Ledger reconciliation REPORT TYPE: Grants only ERROR MESSAGE: NUMBER RECORDS PRINTED : 9
4-482
November 2010
Unapplied Payments Listing (TRRUNPL)

Description
The Unapplied Payments Listing prints a list of all payments that have not been applied to charges. You can run this process for a specific grant code or for a range of grant codes. The fund code on this report represents the fund to which a payment was posted.
Parameters
Name
Required?
Description
Values
Grants Option
Yes
Way you want to enter grant code(s).
A R W S
Automatically enter all grant codes. (default value) Enter a range of grant codes. Search for a specific grant code using a wildcard. Enter a specific grant code.
Grant From Grant To Grant
No No No
First grant code in a series. Enter only if Grants Option = R. Last grant code in a series. Enter only if Grants Option = R. User-defined code identifying a grant. Enter only if Grant s Option = W or S. You may use a wildcard (* or %) if Grants Option = W.
4-483
November 2010
Report Sample
TRRUNPL 4.0
Banner University (sctmhp5) Unapplied Payments Listing Report As of 08-JAN-2000 Research on Arthritis Tran Num 4 Balance -1000
08-JAN-2000 16:24:36 PAGE 1
Grant Code: G00000002 COAS S Grant Cd G00000002 Fund Cd FUND2
Grant Code: G00000007
Research on Rheumatoid Arthritis Tran Num 2 Balance -110
COAS S
Grant Cd G00000007
Fund Cd F7
Grant Code: G00000012 COAS S Grant Cd G00000012 Fund Cd 1112
Research on Arthritis Tran Num 4 Balance -558.8
* * * REPORT CONTROL INFORMATION (trrunpl release 4.0) * * * Parameters have been entered from Host Prompt. Parameter Name _____________________________ Seq No: Grant Option: Grant: Line Count: Value ________________ A 55 Message ____________________________________________________________ All grants Number of lines per page
4-484
November 2010
Utilities Module
This section describes each report in the Utilities module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
4-485
November 2010
Finance Upload to GURFEED Process (FUPLOAD)

Description
The Finance Upload to GURFEED Process is run via job submissions. This process evaluates input data based on parameters entered to load internal vendor data to GURFEED. Input files contain one or more individual documents. Documents include the four record types identified in the following table. For detailed information, refer to Vendor Input File Layout on page 4-489. Renaming the input data file You can use operating system-appropriate commands to rename the input data file: For UNIX, use the mv command. For Windows NT, use the move command For VMS, use the rename command. If you prefer to use a different file renaming command, then make an entry to the system data table through the System Data Maintenance Form (FTMSDAT). Use the following values: ENTITY=FUPLOAD ATTRIBUTE=OS_FILE_RENAME_COMMAND DATA= the actual operating system command for renaming a file
Note Because some operating systems have problems with spaces in file names, we recommend that you create file names that do not contain spaces.
Record Types Header Record (Type 1) Detail Record (Type 2)
Descriptions
Indicates the beginning of a new document. Provides specific transactional data.
4-486
November 2010
Record Types Trailer Record (Type 3) Text Record (Type 4)
Descriptions
Contains the Detail record count and hash total used for file integrity checking. Contains document-related text. Optional. Although Text records are not required, the Finance Upload to GURFEED Process produces a warning message when a document does not include a Text record.
Processing Modes FUPLOAD reads a fixed format input file that has been created from data in a subsystem, such as a Microsoft Excel spreadsheet or a Microsoft Access data base. This file can contain data for multiple documents to be fed to Banner Finance. This process can be executed in one of two modes: (A) Audit or (U) Update. In either mode, the entire input file is read for errors and a report containing each error or warning is noted in the associated report (fupload.lis). Documents that pass all FUPLOAD edits are committed to GURFEED/GURTEXT. Those documents that do not pass all FUPLOAD edits are not committed to the database. When FUPLOAD is executed in Update mode, it is possible for any individual document in an input file to fail the edits and not be loaded, while other documents in the same file that contain no errors are loaded to GURFEED/ GURTEXT. General Encumbrances from External Feeds The posting process (FGRACTG) creates non-labor encumbrances from external feeds. The encumbrance type should be E to indicate a general encumbrance. The rule class used should have a process code to create an original encumbrance. For example, the rule class can contain a process code of E117. In addition to the other required values, the external feed process that populates the GURFEED table must populate the encumbrance-related columns in the following table:
4-487
November 2010
.
GURFEED_ENCD_NUM GURFEED_ENCD_ITEM_NUM GURFEED_ENCD_SEQ_NUM GURFEED_ENCB_TYPE VARCHAR2(8) NUMBER(4) NUMBER(4) VARCHAR2(1)
Edits
FUPLOAD edits are performed in two separate input file passes. The first pass attempts to validate file format (that is, record types 1, 2, and 3 are present and in sequence). Additionally, if the optional Text Record (type 4) is present, FUPLOAD verifies that it follows, in sequence, record types 1, 2, and 3. If Document Code is supplied, the file is checked to ensure the document code is the same for all sequential record types (1, 2, 3, and 4). When the next Type 1 (Header Record) is found, it is assumed that a new document is being transmitted in the same file. If an input file is found to have file format errors in the first pass, the entire file is read and the format errors are listed in the resulting report (fupload.lis). However, the second pass is not performed and the file cannot be loaded to GURFEED. If the file format is found to be valid, FUPLOAD does a second pass to edit for valid data within the file with the following edits: FUPLOAD validates that Account Index, Fund, Organization, Account, Program, Activity, and Location Codes are valid within the designated Chart of Accounts as of the transaction date. Additionally, FUPLOAD will allow for Grant Funds that have an expenditure end date that is beyond the actual termination date of the fund. Transaction date for the document is within an open Fiscal Period for that Chart. of Accounts A transaction description exists. Rule Class and Bank Code, if present, are valid as of the Transaction Date. If an encumbrance document is referenced, then the encumbrance number, encumbrance item, and encumbrance sequence are valid for an open encumbrance. Encumbrance action indicators are also verified to be P (Partial), T (Total), or A (Adjustment). Documents with an encumbrance type of L (Labor) are not edited for encumbrance validity.
4-488
November 2010
If Type 4 records (Text) are not found for any document, a warning is generated. If all other edits are passed, the document is loaded to GURFEED.
Note FUPLOAD files do not contain a User ID. Therefore, FUPLOAD does not check fund/org security or any override indicators/tolerances defined at the user level.
Parameters
Name
Required?
Description
Values
01 02 03 04
System ID Location File name Run Mode
Yes Yes Yes Yes
Must match System ID specified in the input file. Directory path to stored input file. Input file name. When this process runs, the system performs edits and writes any errors to the fupload.lis file. With the audit option (A), data are not committed to GURFEED/GURTEXT. With the update option (U), documents that pass edits are loaded to GURFEED/GURTEXT. A U Audit Update
Vendor Input File Layout Data files from the internal vendors must contain the following elements to populate GURFEED Document Header Records and Document Detail Records. GURFEED records are posted in Banner Finance as Journal Voucher transactions. Associated document text records may also be needed to populate the GURTEXT table where additional information for an upload document is needed. GURTEXT records are loaded to FOBTEXT by FGRTRNI and are viewed as Document Level Text in the Journal Voucher.
Header Record
SYSTEM_ID DOC_CODE REC_TYPE
Start
Length Description
Required
Value/Source
1 9 17
8 8 1
System ID identifies vendor Code identifying document Defines as header record
Yes No Yes
Internal Vendor Internal Vendor/Process 1
4-489
November 2010
Header Record
TRANS_DATE FILLER
Start
Length Description
Required
Value/Source
18 26
8 123
Transaction date YYYYMMDD FILLER
Yes
Internal Vendor Spaces
Detail Record
SYSTEM_ID DOC_CODE REC_TYPE RUCL_CODE DOC_REF_NUM TRANS_AMT TRANS_DESC DR_CR_IND BANK_CODE COAS_CODE ACCI_CODE FUND_CODE ORGN_CODE ACCT_CODE PROG_CODE ACTV_CODE LOCN_CODE ENCD_NUM ENCD_ITEM_NUM ENCD_SEQ_NUM ENCD_ACTION_IND PRJD_CODE ENCB_TYPE
Start
Length Description
Required
Value/Source
1 9 17 18 22 30 42 77 78 80 81 87 93 99 105 111 117 123 131 135 139 140 148
8 8 1 4 8 12 35 1 2 1 6 6 6 6 6 6 6 8 4 4 1 8 1
System ID identifies vendor Code identifying document Defines as detail record Rule Code Reference Number Transaction Amount Transaction Description Debit/Credit (D/C or +/-) Bank Code Chart of Accts code Account Index Code Fund Orgn Acct Prog Activity Location Encumbrance Number Encumbrance Commodity Item Number Encumbrance SEQUENCE NUMBER T = Total, P = Partial, A = Adjustment Project R = Requisition, P = PO, E = Enc, L = Labor, M = Memo.
Yes No Yes Yes No Yes Yes Yes No Yes No Yes No Yes No No No No No No No No No
Internal Vendor Internal Vendor/Process 2 Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor Internal Vendor
4-490
November 2010
Trailer Record
SYSTEM_ID DOC_CODE
Start
Length Description
Required
Value/Source
1 8 System ID identifies vendor 9 8 Code identifying document REC_TYPE 17 1 Defines as trailer record REC_COUNT 18 8 Number of detail records TRANS_TOT 26 12 * Trans Amt total from detail recs FILLER 38 111 FILLER * Total of all transaction amounts in document, regardless of debit or credit.
Yes No Yes Yes Yes
Internal Vendor Internal Vendor/Process 3 Internal Vendor Internal Vendor
Text Record
SYSTEM_ID DOC_CODE REC_TYPE TEXT FILLER
Start
Length Description
Required
Value/Source
1 9 17 18 68
8 8 1 50 81
System ID identifies vendor Code identifying document Defines as text record Alphanumeric text FILLER
Yes No Yes Yes Yes
Internal Vendor Internal Vendor/Process 4 Internal Vendor Space
Note: Text records are not required for any given document; however, if Type 4 (text) records exist, they must follow the format above. In update mode, any document without Type 4 (text) records that passes all other edits is loaded to GURFEED. A warning message is generated in the fupload.lis file (in either Audit or Update mode) for documents that have no Type 4 (text) records.
12-APR-2002
Development Gurfeed Upload Process System ID - BOOKUP
Page: 1 FUPLOAD
FILE:/u/designer/jsmith/GH2.prn Doc Code: BK000003 1 6 3 Type 1 Record written to GURFEED Type 2 Records written to GURFEED Type 4 Records written to GURTEXT 6000.00
DOCUMENT TRANS_TOT
4-491
November 2010
12-APR-2002
Development Gurfeed Upload Process System ID - BOOKUP
Page: 2 FUPLOAD
FILE:/u/designer/jsmith/GH2.prn
* * * REPORT CONTROL INFORMATION - FUPLOAD Release 5.3.1.1 * * *
Detail File Name: /u/designer/jsmith/GH2.prn Run Mode: U System ID: BOOKUP Total Total Total Total Total Records Read: 11 Records inserted into GURFEED: 7 Records inserted into GURTEXT: 0 Errors: 0 Warnings: 0
4-492
November 2010
Student Refund Interface Process (FURAPAY)

Description
The Student Refund Interface Process takes Banner Student/Finance refund check transactions from the Accounting Feed Accounts Payable Table (GURAPAY) and creates FINANCE System Invoices which are ready to be posted unless an error occurs with the transaction. This process provides output to the following tables: Invoice Header Table (FABINVH) Invoice Commodity Table (FARINVC) Invoice Accounting Table (FARINVA) Batch Transaction Error Report Table (FGRTRNR) Approved Document Table (FOBAPPD) Approval History Table (FOBAPPH) Vendor Validation Table (FTVVEND) A possible side effect of this process is that a vendor is created because a vendor must exist before an invoice can be created. If tax processing is in effect, a non-taxable tax group will be placed in the invoice records.
Note The Student Refund Interface Process is most useful when you have the Banner Student System installed.
Parameters
Name
Required?
Description
Values
Bank Code
No
Bank code for those funds without a default bank code.
4-493
November 2010
Finance Feed Sweep Process (FURFEED)

Description
This process produces hard copy output of the Finance Feed Sweep Process. FURFEED gathers financial transaction information from the General System's Finance Transaction Input Table (GURFEED) and inserts it into the Banner Finance System's Transaction Input Table (FGBTRNI).
Parameters
Name
Required?
Description
Values
Report Mode
Yes
Report can be run in either V (View) or S (Select) mode. View runs the audit mode and Select runs the update mode. System to be run through the Finance Feed Sweep. To run the Finance Feed Sweep for all systems enter ALL for SYSTEMID.
V S
View Select
System ID/Time Stamp
Yes
SYSTEMID DD-MON-YY [HH24MISS] ALL = SYSTEMID
Report Sample
05-09-1996 13:08:47 SYSTEM ID --------ACTRECV ACTRECV PAYROLL PAYROLL PAYROLL PAYROLL TIMESTAMP -----------------19910509125500 19910509125951 19910426163418 19910429164329 19910429165825 19910502135325 DOCUMENT -------F0000059 F0000060 F0000028 F0000032 F0000034 F0000036
Banner University Finance Feed Sweep Process DESCRIPTION ----------------------------------AMOUNT -------------6.00 2598000666.04 Banner HR / Position Batch Header Banner HR / Position Batch Header Banner HR / Position Batch Header Banner HR / Position Batch Header REPORT TOTALS: 52132.12 327867.76 52132.16 93998.68 -------------2598526802.76 40 14 41 45 -----164 COUNT -----3 21
PAGE: 1 REPORT: FURFEED STATUS -----------
-------------0 TRANSFERS
4-494
November 2010
Position Control Module

This section describes each report in the Position Control module. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their sevencharacter names.
4-495
November 2010
Budget Roll Process Report (NBPBROL)

Description
This report executes budget roll (including fringe benefits) from one fiscal year to another. Results are posted to the Position Totals Block of the Position Form (NBAPOSN).
Parameters
Name
Description/Values
Required?
Default
Validation
New Fiscal Year
Fiscal year to which the budget is being rolled or approved. Budget ID. The ID you enter here must be valid for all COA codes entered.
Yes
None
Format must be YYYY or YY NBAFISC
Budget ID
Yes, if Banner Finance exists No, if Banner Finance does not exist
None
FTVOBUD
Budget Phase
Budget Phase. The budget phase Yes, if Banner Finance you enter here must be valid for all exists COA codes entered. No, if Banner Finance does not exist Fiscal year from which the budget is being rolled Chart of Account Code or Codes. You can enter multiple COA codes if they are all rolling to the same New Fiscal Year and have the same Current Fiscal Year. Yes
None
FTVOBPH
Current Fiscal Year
None
Format must be YYYY or YY NBAFISC
Chart of Accounts Code
Yes, if Banner Finance exists No, if Banner Finance does not exist Yes
None
FTVCOAS
Salary Group Code
Salary group
None
NTRSGRP
4-496
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Report Choice
Choice of actions: R Roll budget. The contents of NTRBROL and NTRFRNG are printed in the output below the parameters on the control page. Approve budget Delete working budget
Yes
None
None
A D
If you select D, you may select a specific Budget Phase and Budget ID to delete only one working budget. If no phase or ID is specified and D is selected as the Report Choice, then all working budgets will be deleted.
Note: When running NBPBROL to Approve Budgets, every position in Banner for the fiscal year must have a 'Working' budget record for the specified Budget ID and Phase defined in the parameters.
4-497
November 2010
Report Sample
REPORT : NBPBROL
Banner University Budget Roll Process * * * REPORT CONTROL INFORMATION * * *
PAGE 1 RUN DATE 06/07/1991 RUN TIME 04:49 PM
Parameter Name _________________ Parameter Seq No: Report Choice COAS Code New Fiscal Year Current Fiscal Year Budget Id: Budget Phase: Salary Group: Record Count:
Value ______________________________ 5449 A A 1992 1991 9192 GUID92 1992
Source _______ Entered Entered Entered Entered Entered Entered Entered
Message ____________________________________________________________
4-498
November 2010
Budget Maintenance Process (NBPBUDM)

Description
Spreads budget amounts to position labor distributions. Calculates salary and fringe benefit encumbrance amounts for both installation and external funding sources, assigns encumbrance document and sequence numbers, and assigns labor distribution overrides where appropriate.
Parameters
Name
Description/Values
Required?
Default
Validation
Process Mode
Mode of operation R Report mode. If you select this option, the system generates a report of pending transactions but does not change the database in any way. Select this option if you want to preview any updates before actually applying them. Process mode. If you select this option, the system generates a report of pending transactions, then applies the updates to the database. The database update includes the writing of history records for tracking purposes.
Yes
None
None
Budget Processing
Budget transaction processing indicator: Y N Perform budget transaction processing. Do not perform budget transaction processing. If you select this option, the system bypasses the next five parameters and goes directly to Encumbrance (below).
Yes
None
None
This option is not available unless the Banner Finance System is installed at your site.
4-499
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Encumbrances Processing
Encumbrance transaction processing: Y N Perform encumbrance transaction processing. Do not perform encumbrance transaction processing.
Yes
None
None
Active or Working Budgets
Active or working budgets indicator. This parameter appears only if you entered Y at Budget Processing. A Calculate amounts for budgets designated as active in Status in the NBAPOSN Position Salaries Total Block. Calculate amounts for budgets designated as working in Status in the NBAPOSN Position Salaries Total Block.
Yes
None
None
Chart(s) of Accounts to be used in budget selection. This parameter appears only if you entered Y at Budget Processing. (This is a repeating parameter.) Fiscal year to be used in budget selection. This parameter appears only if you entered Y at Budget Processing. Budget ID to be used (in conjunction with budget phase, below) in selection of working budgets. This parameter appears only if you entered Y at Budget Processing and W at Active or Working.
Yes (on first appearance only) Yes
None
FTVCOAS
Fiscal Year
None
NBBFISC
Budget ID
Yes
None
FTVOBUD
4-500
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Budget Phase
Budget phase to be used (in conjunction with budget ID, above) in selection of working budgets. This parameter appears only if you entered Y at Budget Processing and W at Active or Working. COA codes for recasting. Date to be used for computing encumbrances. The Recast Date must fall within the active fiscal year and may be a pay period end date, a specific day within a month, a future date, or a past date. Pay IDs to compute encumbrance recasting. Y N Recast all Pay IDs. Do not recast all Pay IDs.
Yes
None
FTVOBPH
Recast Chart of Accounts Code Recast Date
No
None
FTVCOAS DD-MON-YYYY
Yes, if None Recast Chart of Accounts Code is entered Yes, if Y Recast Chart of Accounts Code is entered Yes, only if Process all Pay IDs? is set to N None
Process all Pay IDs?
Y or N
Recast Pay ID
Pay ID to be used when computing encumbrance recasting.
PTRPICT
4-501
November 2010
Report Sample Encumbrance Option (Page 1 of 3)
REPORT : NBPBUDM
Banner University Budget Maintenance Process Report of Encumbrance Transactions *Transactions Shown Have Been Applied To The Database* Fiscal Year: 1994 Chart of Accounts: A Begin Date: 01-JUL-1993 End Date: 30-JUN-1994 POSITION GLPOSA ORGN 125 ACCT 5210 PROG 100 ACTV SUFFIX 00 JOB BEGIN DATE 03-MAR-1994 SALARY SALARY LOCN PERCENT AMOUNT TO POST 100.00 34343.40 34343.40 ---------- ---------JOB TOTALS 34343.40 34343.40 JOB BEGIN DATE 01-JUL-1993 SALARY SALARY LOCN PERCENT AMOUNT TO POST 100.00 13600.00 13600.00 ---------- ---------JOB TOTALS 13600.00 13600.00
PAGE 1 RUN DATE 03/03/1994 RUN TIME 11:26 AM
ID EMPLOYEE NAME 198234221 Smith, John Paul TYPE EFFECTIVE DT FUND TABLE 03-MAR-1994 1000
ENCUMBRANCE DOCUMENT SEQ PR940001 2
ID EMPLOYEE NAME 999010011 Tait, Eugene K TYPE EFFECTIVE DT FUND TABLE 01-JUL-1993 1000 ORGN 210 ACCT 5120
POSITION 000001 PROG 100 ACTV
SUFFIX 42
ENCUMBRANCE DOCUMENT SEQ PR940001 3
Report Sample - Encumbrance Option (Page 2 of 3)
REPORT : NBPBUDM
Banner University Budget Maintenance Process Report of Encumbrance Transactions *Transactions Shown Have Been Applied To The Database* Fiscal Year: 1994 Chart of Accounts: A Begin Date: 01-JUL-1993 End Date: 30-JUN-1994 GRAND TOTALS FOR THIS YEAR AND CHART
JOB COUNT --------2
SALARY AMOUNT ------------47943.40
SALARY TO POST -------------47943.40
4-502
November 2010
Report Sample - Encumbrance Option (Page 3 of 3)
REPORT : NBPBUDM
Banner University Budget Maintenance Process * * * REPORT CONTROL INFORMATION * * *
Parameter Name ----------------Parameter Seq No: Process Mode: Budget Flag: Encumbrance Flag: Print Lines/Page:
Value -----------------------------18697 P N Y 55
Source Message ----------- -----------------------------------------------------------Default Entered Entered Entered Default
4-503
November 2010
Mass Salary Table Update Report (NBPMASS)

Description
This report calculates the contract value for the fiscal year entered; it also calculates automatic step increases. NBPMASS also updates groups of Table/Grade combinations by amount or percentage and updates job records with a new table/grade combination. If applicable, the system prints messages indicating Electronic Approval activities for employees. See the Electronic Approval Messages section immediately preceding the report samples for further details.
Parameters
Name
Description/Values
Required?
Default
Validation
Report Mode
Choice of actions: R Report - Calculate and print out the changes that take place. Do not do any database updates. Process - Perform database updates.
Yes
None
None
P Process
Choice of actions: D E J U Roll contract dates Roll jobs encumbrance hours Update job records Update NTRSALA tables/grades/steps
Yes
None
None
Job Change Reason Code
Job change reason code. Enter this parameter if you set the Report Mode parameter to P and the Process parameter to either E or J. Salary group to roll from. Enter this parameter if the Process parameter is set to either J or U.
No
None
PTVJCRE
Salary Group (FROM)
No
None
NTRSGRP
4-504
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Salary Group (TO)
Salary group to roll to. Enter this parameter if Process parameter is set to U.
No
None
NTRSGRP
Rule Set
Rule set that the process should use to update salary records.
Yes, if the Process parameter is set to J. No
None
Mass Job Salary Increase Rule Form (NTRJINC)
Personnel Change Date
Personnel change date for use when a future change jobs record is inserted. This parameter updates the Personnel Change Date field on the jobs record being inserted. Enter this parameter if Report Mode parameter is set to P and the Process parameter is set to either E or J.
None
Format must be DD-MMM-YYYY or DD-MMM-YY
Use Population Selection Population selection indicator: Y N Population selection will be used to specify the salaries to be rolled. Population selection will not be used.
No
None
None
Enter this parameter if the Process parameter is set to E or J. Selection ID Selection ID for population selection. Specify this parameter only if you set the Use Population Selection parameter to Y. No None None
4-505
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Creator ID
Creator ID for population selection. Enter this parameter only if you set the Use Population Selection parameter to Y.
No
None
None
Application ID
Application ID for population selection. Enter this parameter only if you set the Use Population Selection parameter to Y.
No
None
None
Electronic Approval Messages When the Process parameter is set to J (Update Job Records) or E (Roll Encumbrance Hours), the system prints messages on the NBPMASS report indicating current Electronic Approval activities for employees. A message is produced when an attempt has been made to update a jobs record through the Electronic Approval process and a future date exists on the associated employee jobs record on NBAJOBS. Messages are also produced when pending Electronic Approval transactions exist. The message produced when an attempt has been made to insert a jobs record for an employee prior to future dated records for that employee depends on the setting of the Allow the Insertion of Job Detail Information Effective Dated Prior to Existing Job Detail Records indicator on the Position Control Installation Rule Form (NTRINST). If the indicator is set to Not Allowed and future record exists for an employee, a message similar to the following is printed in the record for that employee: Future changes after 12-DEC-1994 (record not updated) If the indicator is set to Allowed, a message similar to the following is printed: Future changes after 12-DEC-1994 (record updated) When a pending Electronic Approval transaction exists for an employee, the following message is printed in the record for that employee: Pending changes (record updated); category (s): LTRANE
4-506
November 2010
Report Sample Option D (Page 1 of 2)
REPORT : NBPMASS Mass Salary Table Update REPORT - Roll Contract Dates ___________________________________________________________________ Contract Begin Date From Contract End Date From Contract Begin Date To 01-SEP-1995 30-JUN-1996 01-SEP-1996 ID Name Position SP0000013 Cathie Duncan SP0002 - 00 SP2 Barbara Taylor SP0002 - 00
Contract End Date To 30-JUN-1997
Report Sample Option D (Page 2 of 2)
2 PAGE REPORT : NBPMASS Mass Salary Table Update REPORT - Roll Contract Dates * * * REPORT CONTROL INFORMATION * * * Parameter Name ________________________ Parameter Seq No: Report Mode: Process Type: Line Count: Record Count: Value ___________________ 17774 R Roll Contract Dates 55 2
Source Message _______ ____________________________________________________________ Entered Default Default
4-507
November 2010
Report Sample Option E (Page 1 of 2)
REPORT : NBPMASS
Banner University Mass Salary Table Update PROCESS - Roll Jobs Encumbrance Hours First Name Eugene Eugene Lisa Leigh Thomas Paul Rose Theresa Theresa Michael Michael
ID 999010011 999010011 777010005 555010002 777010007 710922561 777010013 777010010 777010010 555010001 555010001
Last Name Adams Adams Brown Crawford Dean Dunne Griffin Harris Harris Johnson Johnson
MI Position Suff ECLS Roll Ind Encumbrance_Hours Tot_Enc_Hrs Tot_Contract_Hrs K K R A R R T H H F00001 000001 222222 345678 000001 ADM010 222222 000001 222222 345678 678901 00 00 00 00 00 00 00 00 00 00 00 FA FT FA FA FT AD FA FT FA FA FA <-------------------- CURRENT/NEW ---------------------> Z 0.00 111.00 1011.00 0.00 Effective: 15-DEC-1993 <-------------------- CURRENT/NEW ---------------------> C 0.00 0.00 Effective: 01-JAN-1994 <-------------------- CURRENT/NEW ---------------------> Z 400.00 0.00 Effective: 15-DEC-1993 <-------------------- CURRENT/NEW ---------------------> Z 0.00 633.00 1533.00 0.00 Effective: 15-DEC-1993 <-------------------- CURRENT/NEW ---------------------> C 0.00 0.00 Effective: 01-JAN-1994 <-------------------- CURRENT/NEW ---------------------> C 145.00 145.00 1045.00 145.00 Effective: 01-JAN-1994 <-------------------- CURRENT/NEW ---------------------> Z 120.00 0.00 Effective: 15-DEC-1993 <-------------------- CURRENT/NEW ---------------------> C 0.00 110.00 1010.00 110.00 Effective: 01-JAN-1994 Future Change found After/= 15-DEC-1993 <-------------------- CURRENT/NEW ---------------------> Z 0.00 600.00 1500.00 0.00 Effective: 15-DEC-1993 <-------------------- CURRENT/NEW ---------------------> Z 0.00 0.00 Effective: 15-DEC-1993
4-508
November 2010
Report Sample Option E (Page 2 of 2)
REPORT : NBPMASS
Banner University Mass Salary Table Update PROCESS - Roll Jobs Encumbrance Hours * * * REPORT CONTROL INFORMATION * * *
Parameter Name ________________________ Parameter Seq No: Report Mode: Process: Job Change Reason: Personnel Change Date: Use Population Selection: Line Count: Record Count:
Value ___________________ 11605 P Roll Jobs Encumbrance Hours rench 01-JAN-1994 n 55 61
Source Message _______ ____________________________________________________________ Entered Entered Entered Entered Entered Default
4-509
November 2010
Report Sample Option J (Page 1 of 4)
REPORT : NBPMASS Mass Salary Table Update REPORT - Update Job Tables - Salary Increases ID 882100001 100000806 100000806 555020014 555020016 SP0000003 777010012 777010012 SP0000013 929001127 929001127 SP0000005 882100029 SP0000009 SP0000009 Last Name Campbell Canuck Canuck Costello Cowden Cox Davis Davis Duncan Employee Employee Fiege Girard Goddard Goddard First Name Patricia Nanook Nanook Jose Ronald Sidney Mary Mary Cathie Anne Anne Eric Germain Gregory Gregory S S F D D E A A A MI Position Suff MM/DD A 400001 G00022 G00022 500021 500023 SP0001 400001 KFRNGR SP0002 400000 400016 SP0004 400029 SP0007 SP0007 03 00 02 00 00 00 91 00 00 00 00 00 00 00 00 PA / / / / / / / / / / / / / / SGRP Tab Grade Step Hourly_Rate
PAGE 5 RUN DATE 10/24/95 RUN TIME 09:54 AM Annual_Salary
1994 CF 05 0 6.000000 12480.00 1995A CF 05 6.600000 13728.00 1994 FT 10 0 Future Change found After 01-JAN-1996 1994 FT 10 0 Future Change found After 01-JAN-1996 <-------------------- CURRENT/NEW ---------------------> 1994 MF 02 0 6.250000 13000.00 1995A MF 02 6.875000 14300.00 <-------------------- CURRENT/NEW ---------------------> 1994 MF 04 0 8.000000 23640.00 1995A MF 04 8.800298 26004.00 <-------------------- CURRENT/NEW ---------------------> 1995 FF 04 0 31.250601 65000.00 1995A FF 04 34.375661 71500.00 <-------------------- CURRENT/NEW ---------------------> 1994 CF 05 0 12.000000 11520.00 1995A CF 05 13.200000 12672.00 <-------------------- CURRENT/NEW ---------------------> 1994 FT AD 0 12.523595 26050.00 1995A FT AD 13.775912 28655.00 <-------------------- CURRENT/NEW ---------------------> 1995 FF 03 0 24.231235 42000.00 1995A FF 03 26.654359 46200.00 <-------------------- CURRENT/NEW ---------------------> 1994 CF 05 0 11.250000 23400.00 1995A CF 05 12.375000 25740.00 <-------------------- CURRENT/NEW ---------------------> 1994 FF 02 0 16.025667 25000.00 1995A FF 02 17.628205 27500.00 <-------------------- CURRENT/NEW ---------------------> 1995 EX EX 0 16.827266 35000.00 1995A EX EX 18.509971 38500.00 <-------------------- CURRENT/NEW ---------------------> 1994 MF 02 0 8.000000 16640.00 1995A MF 02 8.800000 18304.00 Pending changes (record updated); category(s): LLDIST <-------------------- CURRENT/NEW ---------------------> 1995 CF 01 0 8.750000 9100.00 1995A CF 01 9.625000 10010.00 <-------------------- CURRENT/NEW --------------------->
4-510
November 2010
PAGE 11 REPORT : NBPMASS Mass Salary Table Update REPORT - Update Job Tables - Salary Increases UPDATING JOB TABLES USING SALARY GROUP 1995A Process Only MM/DD: N Process Step Zero: Y Table CF EX FF FT MF TF Incr Step By 0 0 0 0 0 0 Year: 1996 Effective Date: 01-JAN-1996 Percent 10.00 10.00 10.00 10.00 10.00 10.00 Amount Rounding Ind U U U U U U Rounding Amount 1.00 1.00 1.00 1.00 1.00 1.00
REPORT : NBPMASS Mass Salary Table Update REPORT - Update Job Tables - Salary Increases * * * REPORT CONTROL INFORMATION * * * Parameter Name ________________________ Parameter Seq No: Report Mode: Process Type: Salary Group Used: Use Population Selection: Line Count: Record Count: Value ___________________ 18070 R Update Job Tables 1995A N 55 114
Source Message _______ ____________________________________________________________ Entered Default Default Default Default
4-511
November 2010
PAGE 10 REPORT : NBPMASS Mass Salary Table Update PROCESS - Table/Grade Changes * * * REPORT CONTROL INFORMATION * * * Parameter Name ________________________ Parameter Seq No: Report Mode: Process Type: Salary Group: New Salary Group: Line Count: Record Count: Value ___________________ 17772 P Update Salary Tables 1995 1995A 55 80
Source Message _______ ____________________________________________________________ Entered Default Default Default Default
4-512
November 2010
Report Sample Option U (Page 1 of 3)
REPORT : NBPMASS Mass Salary Table Update PROCESS - Table/Grade Changes CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW CURRENT NEW Sal Group 1995 1995A Sal Group 1995 1995A 1995 1995A 1995 1995A 1995 1995A 1995 1995A 1995 1995A Sal Group 1995 1995A Sal Group 1995 1995A 1995 1995A 1995 1995A 1995 1995A 1995 1995A Table CF CF Table CF CF CF CF CF CF CF CF CF CF CF CF Table CF CF Table CF CF CF CF CF CF CF CF CF CF Grade 01 01 Grade 01 01 01 01 01 01 01 01 01 01 01 01 Grade 02 02 Grade 02 02 02 02 02 02 02 02 02 02 Rate/Salary Low 6.89 8.00 Step 0 0 1 1 2 2 3 3 4 4 5 5 Rate/Salary Low 7.14 8.00 Step 0 0 1 1 2 2 3 3 4 4 Rate/Salary Mid 8.67 10.00 Rate/Salary High 10.46 11.00 Type H H
Rate/Salary 6.89 8.00 7.60 8.00 8.31 9.00 9.03 10.00 9.74 11.00 10.46 11.00 Rate/Salary Mid 8.93 10.00 Rate/Salary High 10.71 12.00 Type H H
Rate/Salary 7.14 8.00 7.85 9.00 8.57 9.00 9.28 10.00 10.00 11.00
4-513
November 2010
Report Sample Option U (Page 2 of 3)
REPORT : NBPMASS
Banner University Mass Salary Table Update PROCESS - Table/Grade Changes UPDATING SALARY TABLES - ROLL FROM 1994 TO 1995
Table AD FA FT
Percent 5.00 10.00 10.00
Amount 1000.00 100.00
Rounding Ind U U U
Rounding Amount 1.00 1.00 100.00
Report Sample Option U (Page 3 of 3
REPORT : NBPMASS
Banner University Mass Salary Table Update PROCESS - Table/Grade Changes * * * REPORT CONTROL INFORMATION * * *
Parameter Name ________________________ Parameter Seq No: Report Mode: Process Type: Salary Group: New Salary Group: Line Count: Record Count:
Value ___________________ 11983 P Update Salary Tables 1994 1995 55 42
Source Message _______ ____________________________________________________________ Entered Entered Entered Entered Default
4-514
November 2010
Budget Worksheet Report (NBRBWRK)

Description
This report displays budget phases with current year and prior year budget amounts from the budget file. This report is sorted by organization, fund, program, activity, location, and account.
Parameters
Name
Required?
Description
Values
Previous Fiscal Year Proposed Fiscal Year Budget ID Budget Phase Average Percent Raise Chart of Accounts Code
Yes Yes No No Yes Yes
Previous fiscal year for which detailed budget information will be printed. Fiscal year for which budget is being proposed. ID of specific budget for which information will be printed. Budget phase for which information will be printed. Average salary increase by percentage from the previous to the proposed fiscal year.
Validated against NBAFISC Validated against NBAFISC Validated against FTVOBUD Validated against FTVOBPH
Code for the chart of accounts whose budget is being Validated against FTVCOAS rolled.
4-515
November 2010
REPORT : NBRBWRK A 001 Office of The President Posn Title Ecls EXEC01 Secretary CL Budget Item --------------REG Regular Fiscal Year -----1994 1995
Banner University Budget Work Sheet Report Proposed Budget Id: CHRIS2 Budget Phase: C2-1 Status A Active Type S Single Begin Date 01-JUL-1990 End Date Roll Indicator S Sum Annual Sal. ORGN -----220 220 ACCT -----5210 5210
PAGE 1 RUN DATE 09/22/1995 RUN TIME 01:21 PM 1994 Midpoint 9.18 PROG -----100 100 ACTV -----1995 Midpoint 9.18 LOCN -----PERCENT ------100.00 100.00
Budgeted Percent Budget Amount Diff FTE COAS FUND -------------- -------- ------- --------105,000.00 1.000 A 1000 105,000.00 .00 1.000 A 1000 -------------- -------Total Salaries 1994 105,000.00 1995 105,000.00 .00 ************************************************************ FIM Fica Med 1995 6,510.00 A 1000 FIO Fica Old 1995 1,522.50 A 1000 -------------- -------Total Fringes 1994 .00 1995 8,032.50 ************************************************************ APPROXIMATE BREAKDOWN OF BUDGET AMOUNTS BY LABOR 1994 Budget 1995 Budget Pct Diff COAS FUND --------------- --------------- -------- --------105,000.00 105,000.00 .00 A 1000 .00 8,032.50 A 1000 --------------- --------------- -------Total Compensation 105,000.00 113,032.50 7.65
220 220
5300 5300
100 100
100.00 100.00
DISTRIBUTION ORGN ACCT ------ -----220 5210 220 5300
PROG -----100 100
ACTV ------
LOCN ------
INCUMBENTS ____________________________________________________________________________________________________________________________________ Employee Name Id Suff Stat Begin Date End Date Salary Encumb Job FTE 1994 Ann Sal 1995 Ann Sal Lake, Jay B 7001VLC01 00 A 16-APR-1992 105,000.00 1.000 105,000.00 105,000.00 Default Earn Codes: REG -------------- -------- -------------- -------------Incumbent Totals 105,000.00 1.000 105,000.00 105,000.00 ORGANIZATION TOTALS FOR: 001 Office of The President 1994 Budget 1995 Budget Pct Diff ------------------ ------------------ -------Salaries 105,000.00 105,000.00 .00 Premium Earnings .00 .00 Fringes .00 8,032.50 Fringe Chrg Back .00 .00 Total Compensation 105,000.00 113,032.50 7.65 Budgeted FTE 1.00 1.00 .00 Annual Salaries 105,000.00 105,000.00 .00
4-516
November 2010
REPORT : NBRBWRK
Banner University Budget Work Sheet Report Proposed Budget Id: CHRIS2 Budget Phase: C2-1 Ecls AN Id 888219999 Status A Active Suff 00 Type P Pooled Stat A Begin Date 01-JAN-1991 End Date Roll Indicator S Sum Annual Sal. Salary Encumb 21,402.82 32,083.35 Job FTE 1.000 1.000
A 120 Biology Department Posn Title 000001 Secretary I Employee Name Miller, Steve Senne, Martin F
1994 Midpoint 18,500.00 1994 Ann Sal 26,625.00 65,000.00
1995 Midpoint 18,500.00 1995 Ann Sal 26,625.00 65,000.00
Begin Date 01-JAN-1992
End Date
@00000790 00 A 01-JAN-1994 Default Earn Codes: REG Deduction Codes: DEN 782546777 00 A 01-JUL-1993 Default Earn Codes: REG
Smith, Sally VACANT Incumbent Totals
5,000.00
1.000 1.000 -------7.000
5,000.00
5,000.00 18,500.00 -------------202,025.08
-------------115,198.75
-------------183,525.08
ORGANIZATION TOTALS FOR: 120 Biology Department 1994 Budget -----------------Salaries 71,337.00 Premium Earnings 100.00 Fringes 123.00 Fringe Chrg Back .00 Total Compensation 71,560.00 Budgeted FTE 1.00 Annual Salaries 183,525.08 1995 Budget -----------------207,000.00 .00 .00 .00 207,000.00 7.00 202,025.08 Pct Diff -------190.17
189.27 600.00 10.08
4-517
November 2010
REPORT : NBRBWRK
Banner University Budget Work Sheet Report Proposed Budget Id: CHRIS2 Budget Phase: C2-1 Ecls CL Status A Active Type S Single Begin Date 01-JAN-1992 End Date Roll Indicator S Sum Annual Sal. Salary Encumb 20,259.20 Job FTE 1.000
A 125 Math Department Posn Title 500000 Clerk I/Math (Ind Te Employee Name Mann, Elizabeth
1994 Midpoint 8.67 1994 Ann Sal 20,259.20
1995 Midpoint 8.67 1995 Ann Sal 20,259.20
Id Suff Stat Begin Date End Date 555020017 00 A 01-JUL-1992 Default Earn Codes: REG Deduction Codes: DEN FIM FIO HBC LVR
VACANT Incumbent Totals ORGANIZATION TOTALS FOR: 125 Math Department 1994 Budget -----------------Salaries 50,527.68 Premium Earnings 1,790.25 Fringes 10,365.37 Fringe Chrg Back .00 Total Compensation 62,683.30 Budgeted FTE 2.50 Annual Salaries 40,259.20 1995 Budget -----------------49,598.40 1,790.25 10,294.28 .00 61,682.93 2.50 49,276.00 Pct Diff --------1.84 .00 -.69 -1.60 .00 22.40 -------------40,259.20
.500 -------2.500
-------------40,259.20
9,016.80 -------------49,276.00
CHART OF ACCOUNTS TOTALS FOR: Institute of Technology 1994 Budget -----------------Salaries 226,864.68 Premium Earnings 1,890.25 Fringes 10,488.37 Fringe Chrg Back .00 Total Compensation 239,243.30 Budgeted FTE 4.50 Annual Salaries 328,784.28 1995 Budget -----------------361,598.40 1,790.25 18,326.78 .00 381,715.43 10.50 356,301.08 Pct Diff -------59.39 -5.29 74.73 59.55 133.33 8.37
4-518
November 2010
REPORT : NBRBWRK
Banner University Budget Work Sheet Report Proposed Budget Id: CHRIS2 Budget Phase: C2-1
GRAND TOTALS: 1994 Budget -----------------Salaries 226,864.68 Premium Earnings 1,890.25 Fringes 10,488.37 Fringe Chrg Back .00 Total Compensation 239,243.30 Budgeted FTE 4.50 Annual Salaries 328,784.28 1995 Budget -----------------361,598.40 1,790.25 18,326.78 .00 381,715.43 10.50 356,301.08 Pct Diff -------59.39 -5.29 74.73 59.55 133.33 8.37
REPORT : NBRBWRK Budget Work Sheet Report * * * REPORT CONTROL INFORMATION * * * Parameter Name _________________________ Parameter Seq No: COAS Code: Previous Fiscal Year: Proposed Fiscal Year: Budget Id: Budget Phase: Average Pct Increase: Record Count : 3 Line Count : 55 Value ________________________ 14783 A 1994 1995 CHRIS2 C2-1 .000 Source ____________ Entered Entered Entered Entered Entered Entered
Message _______________________________________________________
Number of Positions Printed
4-519
November 2010
Position Class Listing Report (NBRPCLS)

Description
This report lists defined position classes and salary guidelines. The report is sorted first by position class, then by EEO skill. For additional information about this report, please refer to the Banner Human Resources/Position Control User Guide. There are no parameters for this report.
4-520
November 2010
REPORT : NBRPCLS
Banner University POSITION CLASS LISTING SAL GROUP 1991 TBL SM -------------- --- SALARY --- -------------GRADE STEP LOW MID 3 33,000.00 34,825.00
PAGE 1 RUN DATE 01/08/1992 RUN TIME 01:07 PM HIGH 37,000.00
POSITION CLASS KMD01 Full Time Administrative
ACTIVITY EEO SKILL EXEMPT EMPLOYEE CLASS CIP CODE DATE 10 Exec/Admin/Mgr Y BK Bi-Weekly 27-JUN-1991 -------------------------------------------------------------------------------------------------------------------------------------------- --- SALARY --- -------------POSITION CLASS SAL GROUP TBL GRADE STEP LOW MID HIGH KMD02 Hourly Rate 1991 SM 1 0 11,000.00 13,200.00 15,400.00 ACTIVITY EEO SKILL EXEMPT EMPLOYEE CLASS CIP CODE DATE 40 Secy/Clerical N SM Semi-Monthly 30-SEP-1991 -------------------------------------------------------------------------------------------------------------------------------------------- --- SALARY --- -------------POSITION CLASS SAL GROUP TBL GRADE STEP LOW MID HIGH KMD03 Salary 1991 SM ACTIVITY EEO SKILL EXEMPT EMPLOYEE CLASS CIP CODE DATE 40 Secy/Clerical Y SM Semi-Monthly 30-SEP-1991 -------------------------------------------------------------------------------------------------------------------------------------------- --- SALARY --- -------------POSITION CLASS SAL GROUP TBL GRADE STEP LOW MID HIGH P1001 Part Time Clerical UN PT 3 ACTIVITY EEO SKILL EXEMPT EMPLOYEE CLASS CIP CODE DATE 40 Secy/Clerical N PT Part Time Hourly 19-APR-1991 -------------------------------------------------------------------------------------------------------------------------------
REPORT : NBRPCLS
Banner University POSITION CLASS LISTING * * * REPORT CONTROL INFORMATION * * *
Parameter Name _________________ Record Count
Value ______________________________ 20
Source _______
Message ____________________________________________________________
4-521
November 2010
Position Class Incumbent Report (NBRPINC)

Description
This report lists incumbents of positions in each position class.
Parameters
Name
Required?
Description
Values
Report As of Date
Yes
Date from which you want to report.
DD-MON-YYYY
4-522
November 2010
REPORT : NBRPINC POSITION CLASS B1001 Professional
Banner University AS OF 23-JAN-1991
------POSITION-----ORGN NUMBER A A A A A A A A A A A A A A 2010 2010 2010 2010 2010 2010 2010 2010 2010 2020 2010 2010 2010 2010 000003-00 000003-00 000003-00 000003-00 000003-00 000003-00 000003-00 000003-00 000003-01 092256-00 100003-00 100003-00 100003-00 100003-00
----------------------EMPLOYEE---------------------- ASSGN ID NAME STA SEX ETHN FTE 704444446 777070011 717000001 777070003 710000020 777070012 777070001 710000004 710000021 710000005 777070013 777070011 710000022 777070012 Adames, Nicole Hill, Thomas P Johnson, Marie Lewis, Franklin M Miller, Harry T Pierce, Andrew K Simpson, Lydia J Stewart, Frank Griffin, Karen M Tucker, Sylvia Goodhart, Kenneth Hill, Thomas P Knotts, Harold P Pierce, Andrew K A A A L F A A A A A A A A A F M M M M M F M F F M M M M 2 1 2 1 1 2 1 4 1 5 1 1 2 2 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
TABLE FT FT FT FT FT FT FT FT FT FT FT FT FT FT
SAL GRADE STEP IND PR PR PR PR PR PR PR PR PR PR PR PR PR PR 0 0 0 0 0 0 0 0 0 0 0 0 0 0 V V V V V V V V V V V V V V
SALARY/RATE 40,000.08 49,999.92 36,000.00 48,000.00 29,999.97 20,800.80 51,700.08 24,000.00 10,400.40 24,000.00 40,000.08 49,000.08 20,800.80 24,000.00 12.500000 34,390.77
MID PT RATIO .56 .71 .51 .68 .42 .29 .73 .34 .15 .34 .56 .69 .29 .34
AVERAGE HOURLY RATE AVERAGE SALARY
REPORT : NBRPINC
Banner University POSITION CLASS INCUMBENT REPORT AS OF 23-JAN-1991 * * * REPORT CONTROL INFORMATION * * *
Parameter Name _________________ Parameter Seq No: As of Date: Record Count Line Count : 55
Value ______________________________ 1000 23-JAN-1991 134
Source _______ Entered
Message ____________________________________________________________ Count of Employee Records Printed
4-523
November 2010
Position Report (NBRPOSN)

Description
This report lists active, frozen, and/or cancelled positions for a specified date range.
Parameters
Name
Required?
Description
Values
Report Start Date Report End Date Report Status
No No No
Start date of the report. If this parameter is left blank, DD-MON-YYYY the system defaults to 01-JAN-YYYY. End date of the report. If this parameter is left blank, the system defaults to 31-DEC-YYYY. Status of positions to be reported. DD-MON-YYYY A F C Blank Active Frozen Cancelled All
4-524
November 2010
REPORT : NBRPOSN
Banner University POSITION REPORT BETWEEN 01-OCT-1990 AND 22-FEB-1991
COAS - A POSITION 000001 000009 000013 000100 000185 000333 000KMD 001KMD 002345 091956 092256 100001 740001 740002 740003 740004 740005 740006 740007 740008 740009 740010 BK0001 G10001 G01002 G10004 KD0005 KD0006 KD0007 S10001 X00003
DEPT - 100 Office of The President DESCRIPTION Instructor Software Consultant Senior Programmer Programmer Secretary Admin Asst. Secretary Administrators Student Worker Maint. Supervisor Senior Technical Specialist Data Entry Specialist Secretary Secretary Secretary Secretary Secretary Secretary Secretary Secretary Secretary Secretary Instructor Counselor Librarian Data Entry Specialist Secretary Secretary Counselor Security Counselor STATUS Active Active Active Active Active Active Active Active Active Active Active Frozen Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active BEGIN DATE END DATE TYPE PCLS H1001 B1001 B1001 SK001 J1001 A1001 A1011 A1011 ST001 M1001 B1001 H1001 00001 00001 00001 00001 00001 00001 00001 00001 00001 00001 BK001 GOVT1 A1001 GOVT4 KD001 KD001 KD001 SE001 X0001 ECLS REPORTS FA SA SA SK KD AD SA SA SW MN SA FA 01 01 01 01 01 01 01 01 01 01 BK GH AD GH K1 K1 K1 SE XS 000101 AUTH # 003434 ROLL C S V C V V V S Z S S C S S S S S S S S S S R C S C V M C S M
01-JUL-1989 Single 01-JUN-1990 30-JUN-1991Single 01-JUL-1990 Single 01-JAN-1991 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Pooled 07-FEB-1991 Pooled 01-JUL-1990 Single 01-JUL-1989 Single 31-JAN-1991 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-JUL-1990 Single 01-SEP-1990 Pooled 01-JAN-1991 Pooled 01-JAN-1991 Pooled 01-JAN-1991 Pooled 01-JUL-1990 Pooled 01-JUL-1990 Pooled 20-FEB-1991 Single 24-JUL-1990 Single 01-AUG-1990 Single
000KMD
343433
993KFK
4-525
November 2010
REPORT : NBRPOSN
Banner University POSITION REPORT BETWEEN 01-OCT-1990 AND 22-FEB-1991 * * * REPORT CONTROL INFORMATION * * *
Parameter Name _________________ Parameter Seq No: Start Date: Stop Date: Position Status: Record Count Line Count : 55
Value ______________________________ 1000 01-OCT-1990 22-FEB-1991 All Positions 75
Source _______ Entered Entered Default
Message ____________________________________________________________
Count of Position Records Printed
4-526
November 2010
Position Status Exception Report (NBRPSTA)

Description
This report lists exception status positions (i.e., over budget, vacant, cancelled, frozen, under-encumbered, or overfilled).
Parameters
Name
Required?
Description
Values
Report As of Date Report Choice by Orgn/Cat (Organization or Category) Report All Position Exceptions Report Over Budget Positions Report Vacant Positions
Yes No
Date from which you want to report. Sort report by organization or category. Enter 1 to sort by organization, or enter 2 to sort by category. All Position Indicator. Enter Y to include all position exceptions, or enter N to exclude all position exceptions from this report. Over Budget Position Indicator. Enter Y to include over budget positions, or enter N to exclude over budget positions from this report. Vacant Position Indicator. Enter Y to include vacant positions, or enter N to exclude vacant positions from this report. Cancelled Position Indicator. Enter Y to include cancelled positions, or enter N to exclude cancelled positions from this report. Frozen Position Indicator. Enter Y to include frozen positions, or enter N to exclude frozen positions from this report. Under Encumbered Position Indicator. Enter Y to include under encumbered positions, or enter N to exclude under encumbered positions from this report.
DD-MON-YYYY 1 or 2 Default = 1 Y N Y N Y N Y N Y N Y N Yes (default) No Yes No Yes No Yes No Yes No Yes No
Yes
No
No
Report Cancelled Positions Report Frozen Positions
No
No
Report Under Encumbered Posns
No
4-527
November 2010
Parameters (cont)
Name
Required?
Description
Values
Report Over Filled FTE Posns Position Totals Option
No
Over Filled Position Indicator. Enter Y to include Y over filled positions, or enter N to exclude over filled N positions from this report. Select one of the following options: S (Salary), F (Fringe), or B (Both). S F B
Yes No Salary Fringe Both (Salary and Fringe)
Yes
REPORT : NBRPSTA
Banner University Position Status Exception Rpt All Position Exceptions As Of 03-FEB-1994
POSITION FT ----------DATE--------- ----------FTE--------- -------------SALARY, FRINGE AMOUNT--------------------STATUS POSITION CLASS PT BEGIN END BUDGET FILLED VACANT BUDGET ENCUMBERED EXPENDED BALANCE ____________________________________________________________________________________________________________________________________ ____________________________________________________________________________________________________________________________________ Active 000002 F1002 3 01-JAN-1991 6.000 13.000 .000 1494,110.50 383,825.26 .00 1110,285.24 Active 000003 P1001 4 01-JAN-1991 10.000 5.000 5.000 328,650.00 51,570.00 .00 277,080.00 Active ADM010 A1001 3 01-JUL-1990 1.000 3.000 .000 46,966.50 52,800.00 .00 -5,833.50 Active ADM020 A1001 3 01-JUL-1990 1.000 .000 1.000 39,138.75 .00 .00 39,138.75 Active CL0100 C0100 3 01-JAN-1991 5.000 .000 5.000 98,280.00 .00 .00 98,280.00 Active CWS001 CWS 6 01-JAN-1991 36.000 .000 36.000 201,285.00 .00 .00 201,285.00 Active EXEC22 A1001 3 01-JUL-1990 1.000 .000 1.000 58,708.65 .00 .00 58,708.65 Active F00002 F0001 2 30-JAN-1991 1.000 2.000 .000 67,095.00 .00 .00 67,095.00 Active F00003 F0001 2 01-JAN-1991 5.000 1.000 4.000 279,562.50 .00 .00 279,562.50 Active F10001 F0001 2 01-JAN-1991 1.000 .000 1.000 61,503.75 .00 .00 61,503.75 Active F11111 F0001 2 01-JAN-1991 1.000 .000 1.000 67,095.00 .00 .00 67,095.00 Active G10001 G0001 3 01-JAN-1991 1.000 .000 1.000 46,966.50 .00 .00 46,966.50 ==================================================================================================================================== A DEPT - 220 Payroll Office ==================================================================================================================================== ORGANIZATION TOTALS Over Budget 1 Vacant 9 Under Budget 11 Over Filled FTE 3 -------BALANCE------FTE AMOUNT .000 -5,833.50 55.000 1129,620.15 55.000 2307,000.39 .000 1171,546.74
4-528
November 2010
REPORT : NBRPSTA
Banner University Position Status Exception Rpt All Position Exceptions As Of 03-FEB-1994
POSITION FT ----------DATE--------- ----------FTE--------- -------------SALARY, FRINGE AMOUNT--------------------STATUS POSITION CLASS PT BEGIN END BUDGET FILLED VACANT BUDGET ENCUMBERED EXPENDED BALANCE ____________________________________________________________________________________________________________________________________ ____________________________________________________________________________________________________________________________________ GRAND ORGN TOTALS Over Budget 2 Vacant 30 Under Budget 32 Over Filled FTE 5 -------BALANCE------FTE AMOUNT .000 -14,933.50 183.000 5214,105.82 169.000 6891,821.72 .000 1504,382.40
REPORT : NBRPSTA
Banner University Position Status Exception Rpt All Position Exceptions As Of 03-FEB-1994 * * * REPORT CONTROL INFORMATION * * *
Parameter Name ___________________ Parameter Seq No: As Of Date: Orgn or Cat: Posn Tots Option: All Posn Exceptions LINE COUNT: 55 RECORD COUNT: 37
Value ______________________________ 16261 03-FEB-1994 2 b y
Source Message __________ _____________________________________________________________________ Entered Entered Entered Entered
4-529
November 2010
Budget Data Finance Extract (NHPFIN1)

Description
NHPFINI1 extracts data for the Banner Finance System interface and updates the position totals with encumbered amounts. This report is most useful when you use the Position Control forms relating to payroll, salary, and job position functions.
Parameters
Name
Required?
Description
Values
Interface COBRA Flag
Yes
COBRA Finance Interface Indicator. Enter Y to perform COBRA interface processing, or enter N to override COBRA interface processing. Budget Data Finance Interface Indicator. Enter Y to perform budget interface processing, or enter N to override budget interface processing.
Y N Y N
Yes No Yes No Yes No
Interface Budget Flag
Yes
Interface Encumbrance Flag
Yes
Encumbrance Data Finance Interface Indicator. Y Enter Y to perform encumbrance processing, or enter N N to override encumbrance processing.
4-530
November 2010
REPORT : NHPFIN1
Banner University Budget Data Finance Extract
T O T A L S Budget ... Budget ...
B Y
C A T E G O R Y 1469600.00 12660.00 1482260.00 + +
Earnings (Original) Fringe (Original)
TOTAL ..................................
REPORT : NHPFIN1
Banner University Budget Data Finance Extract * * * REPORT CONTROL INFORMATION * * *
Parameter Name _________________ Parameter Seq No: Cobra Flag: Budget Flag: Encumbrance Flag: Print Lines/Page:
Value ______________________________ 59274 N Y N 55
Source Message ___________ ____________________________________________________________ Default Entered Entered Entered
Number of NHRFINC records inserted: 47
4-531
November 2010
Finance Interface Report (NHPFIN2)

Description
This report shows information extracted and passed to the Banner Finance System. This report is most useful when you have specific payroll related data in your system.
Parameters
Name
Required?
Description
Values
Produce Detail Report (Y/N) Interface Trans to GURFEED
Yes
Detail Finance Interface Report Indicator. Enter Y to Y create the Detail Finance Interface Report; enter N to N override the Detail Finance Interface Report. Finance Interface Indicator. Enter Y to interface transactions to the Banner Finance System from the Position Control Module; enter N to override the interface to the Banner Finance System from the Position Control Module. Payroll ID code. Enter a value in this parameter if expenditure data is to be interfaced. Y N
Yes No Yes No
Yes
Expenditure Payroll ID
No
4-532
November 2010
REPORT : NHPFIN2 D E T A I L
Banner University Payroll Id: SK Payroll Number: 4 Pay Period: 16-FEB-1991 To 28-FEB-1991
COAS CODE: T FUND 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 ORGN 120 120 120 120 120 120 120 120 120 120 120 120 120 120 120 220 220 220 220 220 220 220 220 220
FISCAL YR: 1991 ACCT 5120 5120 5120 5120 5120 5120 5120 5120 5120 5120 5120 5120 5120 5120 PROG 100 100 100 100 100 100 100 100 100 100 100 100 100 ACTV
CATEGORY: Gross Earnings Payroll Expense LOCN EMPLOYEE NAME Alberts, Jane P Alberts, Jane P Barron, Dan M Barron, Dan M Fellows, Tom Paul Fellows, Tom Paul Newton, Frank P Newton, Frank P Singer, Lois R Singer, Lois R White, Robert M White, Robert M P R O G A C C T O R G N T O T A L T O T A L T O T A L
RULE CLASS: HGRS Payroll - Gross Salary Expense EMPLOYEE ID 765000002 765000002 765000004 765000004 765000005 765000005 765000006 765000006 765000003 765000003 765000001 765000001 AMOUNT 114.44 915.56 119.44 955.56 467.78 3742.23 113.89 11.11 35.00 280.00 888.89 7.11 Dr Dr Dr Dr Dr Dr Dr Dr Dr Dr Dr Dr HOL REG HOL REG HOL REG HOL HOL HOL REG REG REG SOURCE
8763.02 Dr 8763.02 Dr 8763.02 Dr 765000006 765000006 765000003 765000003 765000001 765000001 16.67 133.34 52.50 420.00 1.33 10.67 634.51 634.51 634.51 9397.53 9397.53 9397.53 Dr Dr Dr Dr Dr Dr Dr Dr Dr Dr Dr Dr HOL REG HOL REG HOL REG
5120 5120 5120 5120 5120 5120 5120 5120
100 100 100 100 100 100 100
Newton, Frank P Newton, Frank P Singer, Lois R Singer, Lois R White, Robert M White, Robert M P A O F R C R C R U U A O C G N L T G T N D E E G T T T T T O O O O O O R T T T T T Y A A A A A L L L L L T O T A L
4-533
November 2010
REPORT : NHPFIN2 D E T A I L COAS CODE: T FISCAL YR: 1991
Banner University
T O T A L S
B Y
C A T E G O R Y 9397.53 718.91 10116.44 2174.70 7222.83 718.91 10116.44 Credit Credit Credit Debit Debit
Gross Earnings Payroll Expense Employer Fringe Payroll Expense TOTAL .................................. Employee Deductions Payroll Liability Net Payroll Employer Fringe Payroll Liability TOTAL ..................................
4-534
November 2010
REPORT : NHPFIN2 S U M M A R Y COAS CODE: T FUND 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 ORGN 120 120 120 120 120 220 220 220 220 220 FISCAL YR: 1991 ACCT 5120 5120 5120 5120 PROG 100 100 100 ACTV
Banner University
PAGE 11 RUN DATE 08/21/1991 RUN TIME 06:54 PM RULE CLASS: HGRS Payroll - Gross Salary Expense AMOUNT 973.66 Dr 7789.36 Dr 8763.02 Dr 8763.02 Dr 8763.02 Dr 70.50 Dr 564.01 Dr HOL REG HOL REG SOURCE
CATEGORY: Gross Earnings Payroll Expense LOCN TRANSACTION DATE 28-FEB-1991 28-FEB-1991 P R O G A C C T O R G N T O T A L T O T A L T O T A L
5120 5120 5120 5120
100 100 100
28-FEB-1991 28-FEB-1991 P A O F R C R C R U U A O C G N L T G T N D E E G T T T T T O O O O O O R T T T T T Y A A A A A L L L L L T O T A L
634.51 634.51 634.51 9397.53 9397.53 9397.53
Dr Dr Dr Dr Dr Dr
4-535
November 2010
REPORT : NHPFIN2
Banner University
* * * REPORT CONTROL INFORMATION * * * Parameter Name _________________ Parameter Seq No: Detail Report: Interface: Pay Id: Print Lines/Page: Value ______________________________ 11568 Y Y SK 55 Source Message ___________ ____________________________________________________________ Default Entered Entered Entered
P A Y R O L L
SYSTEM ID ( including Batch header(s) )
Number of GURFEED records inserted: 26 GURFEED DOC CODE (Batch Number)
: F0000303
4-536
November 2010
Budget Distribution Report (NHRBDST)

Description
To use this report, the Banner Human Resources System and the Banner Finance System must both be installed at your site. (If both the Banner Finance indicator and the Banner Human Resources indicator on the Installation Control Form (GUAINST) are set to Y, both systems are installed at your site.) This report prints budgetary information for selected FOAPALs. The information can cover all employee positions, only the positions in specified position classes, or specific positions within any position classes. The data are organized in one of three ways: By positionWhen you choose this option, the report provides data for each position being covered. For each specified earnings or benefit, the report: Indicates the amount budgeted for the item for the fiscal year Indicates the amount expended for the item for the report period Specifies the amount expended for the item from the start of the fiscal year containing the report begin date to the earlier of these two dates: the date the report is run or the end of the fiscal year. For example, if the fiscal end date is 30-Jun-95 and the report run date is 30-Nov-94, the value represents the amount expended through 30-Nov-94. If the report run date is 01-Aug-95, the value represents the amount expended through 30-Jun-95. Tells what percent of the amount budgeted for the item for the fiscal year is represented by the amount expended for that item for the fiscal year By position classWhen you choose this option, the report specifies earnings and benefit data for each position class being covered and for each selected position within each class. The information for positions and position classes is identical with that described for the by-position report. By earnings/benefitWhen you choose this option, the report specifies data for each earnings and benefit being covered. The data is identical with that described for the by-position report. In this case, however, the positions are not listed; that is, each budgeted and expended amount specified is the total amount for all positions covered by the report.
4-537
November 2010
Parameters
Name
Description/Values
Required?
Default
Validation
Report Option
Organization option for report: 1 2 3 The report is to be organized by earnings and/or benefits. The report is to be organized by employee positions. The report is to be organized by position classes.
Yes
2 (by position)
None
Report Begin Date Report End Date Hierarchy Option
First date in the report period Last date in the report period Hierarchy for report. Enter one of the following values: E As exists. This value specifies that all FOAPALs are to be reported as they exist on the database. Data are not to be rolled up to higher fields or higher levels. Roll up to specified FOAP fields. (You will specify the fields in applicable parameters, as described below.) Roll up to a specified level for each FOAP. (You will specify the levels in applicable parameters, as described below.)
Yes Yes Yes
None None E (as exists)
None None None
Note: If you have set this parameter to E or F, skip to the Chart of Accounts parameter. If you have set the parameter to L, go to the Fund Level parameter. When Hierarchy Option equals L and Fund Level equals E (see below), then all funds are reported at the existing level. This gives you the option to just roll to organization level 1 (via the Orgn Level parameter) and report the remaining FOAP data as it exists.
4-538
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Fund Level
Fund level for the report. Enter E (as exists) to No indicate that funds are not to be rolled up to a higher level, or enter a number from 1 through 5 to identify a level to which data is to be rolled. Organization level for the report. Enter E (as No exists) to indicate that organizations are not to be rolled up to a higher level, or enter a number from 1 through 8 to identify a level to which data is to be rolled. Account level for the report. Enter E (as exists) to indicate that accounts are not to be rolled up to a higher level, or enter a number from 1 through 4 to identify a level to which data is to be rolled. Program level for the report. Enter E (as exists) to indicate that programs are not to be rolled up to a higher level, or enter a number from 1 through 5 to identify a level to which data is to be rolled. Code identifying a chart of accounts to be covered in the report. This is a repeating parameter. No
None
Orgn Level
None
Acct Level
None
Prog Level
No
None
Chart of Accounts
Yes (on first appearance only)
None
FTVCOAS
Note: If you have set Hierarchy Option to L (Level roll up), skip to the Employee Class parameter. If Hierarchy Option equals F (FOAP field roll up), skip to the Fund parameter. If Hierarchy Option equals E (as exists) go to the Fund Option parameter.
4-539
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Fund Option
Codes identifying the chart of accounts whose No fund data is to be printed and the fund(s) for which information is to be is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all funds within chart H. This is a repeating parameter. Option for specifying funds: A All. Requests that data be printed for all funds. If you enter this value, skip to the Orgn Option parameter. Range. Requests that data be printed for a specific range of funds. If you enter this value, go to the From Fund parameter. Wild Card. Requests that data be printed for one or more specific funds, and indicates that you will use wild cards when you identify these funds. (By using a wild card, you can identify several funds with one code; for example, A% identifies all fund codes starting with A). If you enter this value, skip to the Fund parameter. Specific. Requests that data be printed for one or more specific funds, and indicates that you will enter exact codes to identify these funds. If you enter this value, skip to the Fund parameter.
All
None
Fund Option
Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
4-540
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
From Fund
Chart of accounts whose fund data is to be printed and the first fund in the range of funds for which data is to be printed. The codes are separated by a comma, for example, H,1000. This is a repeating parameter. Chart of accounts whose fund data is to be printed and the last fund in the range. The codes are separated by a comma, for example, H,2000. This is a repeating parameter. Chart of accounts whose fund data is to be printed and a specific fund for which data is to be printed. The codes are separated by a comma. This is a repeating parameter. If Hierarchy Option equals E, then you can enter several fund codes for each chart; for example, you can enter: A,1000 A,1001 G,2000 H,1000 If Hierarchy Option equals F, then you can enter only one fund code for each chart and cannot use wild cards; for example, you can enter: A,1000 G,2000 H,1001
No
None
None
To Fund
No
None
None
Fund
No
None
FTVFUND
4-541
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Orgn Option
If Hierarchy Option equals F, skip this No parameter and go directly to the Orgn parameter. If Hierarchy Option equals E, enter codes as described below. Codes identifying the chart of accounts whose organization data is to be printed and the organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all organizations within chart H. This is a repeating parameter. There are four options for specifying organizations: A All. Requests that data be printed for all organizations. If you enter this value, skip to the Acct Option parameter. Range. Requests that data be printed for a specific range of organizations. If you enter this value, go to the From Orgn parameter. Wild card. Requests that data be printed for one or more specific organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Orgn parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
All
None
4-542
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Specific. Requests that data be printed for one or more specific organizations, and indicates that you will enter exact codes to identify these organizations. If you enter this value, skip to the Orgn parameter. No None None
From Orgn
Chart of accounts whose organization data is to be printed and first organization in the range of organizations for which data is to be printed. The codes are separated by a comma, for example, H,120. This is a repeating parameter. Chart of accounts whose organization data is to be printed and the last organization in the range. The codes are separated by a comma, for example, H,129. This is a repeating parameter.
To Orgn
No
None
None
4-543
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Orgn
Chart of accounts whose organization data is to be printed and a specific organization for which data is to be printed. The codes are separated by a comma, for example, H,120. This is a repeating parameter. If you have set Hierarchy Option to E, then you can enter several organization codes for each chart. If you have set the Orgn Option to W, you can use wild cards to identify organizations. If Orgn Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one organization code for each chart and cannot use wild cards. (See Fund parameter examples above.)
No
None
FTVORGN
4-544
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Acct Option
If Hierarchy Option equals F, skip this No parameter and go directly to the Acct parameter. If Hierarchy Option equals E, enter codes as described below. Codes identifying the chart of accounts whose account data is to be printed and the account(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all accounts within chart H. This is a repeating parameter. There are four options for specifying accounts: A All. Requests that data be printed for all accounts. If you enter this value, skip to the Prog Option parameter. Range. Requests that data be printed for a specific range of accounts. If you enter this value, go to the From Acct parameter. Wild card. Requests that data be printed for one or more specific accounts, and indicates that you will use wild cards when you identify these accounts. If you enter this value, skip to the Acct parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
All
None
4-545
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Specific. Requests that data be printed for one or more specific accounts, and indicates that you will use exact codes to identify the accounts. If you enter this value, skip to the Acct parameter. No None FTVACCT
From Acct
Chart of accounts whose account data is to be printed and the first account in the range of accounts for which data is to be printed. The codes are separated by a comma, for example, H,5210. This is a repeating parameter. Chart of accounts whose account data is to be printed and the last account in the range. The codes are separated by a comma, for example, H,5220. This is a repeating parameter. Chart of accounts whose account data is to be printed and a specific account for which data is to be printed. The codes are separated by a comma, for example, H,5210. This is a repeating parameter. If you have set Hierarchy Option to E, then you can enter several account codes for each chart. If Acct Option equals W, you can use wild cards to identify accounts. If Acct Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one account code for each chart and cannot use wild cards. (See Fund parameter examples above.)
To Acct
No
None
FTVACCT
Acct
No
None
FTVACCT
4-546
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Prog Option
If Hierarchy Option equals F, skip this parameter and go directly to the Prog parameter. If Hierarchy Option equals E, enter codes as described below. Codes identifying the chart of accounts whose program data is to be printed and the program(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all programs within chart H. This is a repeating parameter. There are four options for specifying programs: A All. Requests that data be printed for all programs. If you enter this value, skip to the Employee Class parameter. Range. Requests that data be printed for a specific range of programs. If you enter this value, go to the From Prog parameter. Wild card. Requests that data be printed for one or more specific programs, and indicates that you will use wild cards when you identify these programs. If you enter this value, skip to the Prog parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
No
All
None
4-547
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Specific. Requests that data be printed for one or more specific programs, and that you will use exact codes to identify these programs. If you enter this value, skip to the Prog parameter. No None None
From Prog
Chart of accounts whose program data is to be printed and the first program in the range of programs for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. Chart of accounts whose program data is to be printed and the last program in the range. The codes are separated by a comma, for example, H,610. This is a repeating parameter.
To Prog
No
None
None
Prog
Chart of accounts whose program data is to be No printed and a specific program for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. If you have set Hierarchy Option to E, then you can enter several program codes for each chart. If the Prog Option equals W, you can use wild cards to identify programs. If Prog Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one program code for each chart and cannot use wild cards. (See Fund parameter examples above.)
None
FTVPROG
4-548
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Employee Class
Employee class for which data is to be printed. This is a repeating parameter. Wild cards can be used. Code specifying whether earnings are to be included: Y N All or some earnings are to be included in the report. No earnings are to be included in the report.
No
All
PTRECLS
Include Earnings
Yes
None
Earn Code
Earn code for which data is to be printed. This is a repeating parameter. Wild cards can be used. If this field is left blank, all earn codes are selected. Code specifying whether benefits are to be included: Y N All or some benefits are to be included in the report. No benefits are to be included in the report.
No
All
None
Include Benefits
Yes
None
Benefit Code
Code identifying a benefit for which data is to No be printed. This is a repeating parameter. Wild cards can be used. If this field is left blank, all benefits are selected. Fringe charge back inclusion indicator: Y N Include fringe charge back data. Do not include fringe charge back data. Y
All
None
Include Fringe Charge Back
None
4-549
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Select Positions or Classes
Positions for which data is to be printed: A Data is to cover all positions in all position classes. If you enter this value, skip the remaining parameters. Data is to cover all positions in specific position classes. If you enter this value, skip to the Position Class parameter. Data is to cover specific positions. If you enter this value, go to the Position parameter.
No
None
Position Classes
Position class for which data is to be printed. This is a repeating parameter. Wild cards can be used. Position for which data is to be printed. This is a repeating parameter. Wild cards can be used.
No
All
NTRPCLS
Position
No
All
NBBPOSN
4-550
November 2010
Report Sample - by Earnings (Page 1 of 2)
PAGE 1 REPORT : NHRBDST Fiscal Yr: 1995 COAS: A Fund 1829B *RG FIM FIO Orgn 120
Banner University Budget Distribution Report Reporting Period: 01-JUL-1994 To 31-DEC-1994
Organization: 120 Treasury Department Acct 5210 Prog 100 Actv Locn Current Actual -------------6,249.96 75.50 322.90 Fiscal Actual ------------6,249.96 75.50 322.90 Annual Budget ------------.00 .00 .00 Variance --------
Fica Medicare Fica Old Age . . . Fund Orgn Acct 1829B 120 5210 *RG OT VAC FIM FIO
Prog 610
Actv
Locn Current Actual -------------38,037.49 .00 .00 459.67 1,020.54 38,037.49 1,480.21 39,517.70 44,287.45 1,878.61 46,166.06 44,287.45 46,166.06 1,878.61 76,074.96 2,960.40 79,035.36 76,074.96 2,960.40 79,035.36 Fiscal Actual ------------38,037.49 .00 .00 459.67 1,020.54 38,037.49 1,480.21 39,517.70 44,287.45 1,878.61 46,166.06 44,287.45 46,166.06 1,878.61 76,074.96 2,960.40 79,035.36 76,074.96 2,960.40 79,035.36 Annual Budget ------------175,000.00 17,500.00 12,500.00 4,750.00 3,750.00 205,000.00 8,500.00 213,500.00 205,000.00 8,500.00 213,500.00 205,000.00 213,500.00 8,500.00 410,000.00 17,000.00 427,000.00 410,000.00 17,000.00 427,000.00 Variance -------21.74 .00 .00 9.68 27.21 18.55 17.41 18.51 21.60 22.10 21.62 21.60 21.62 22.10 18.55 17.41 18.51 18.55 17.41 18.51
Overtime Pay Vacation Pay Fica Medicare Fica Old Age Prog Earnings Total for 610 Prog Benefits Total for 610 Prog Total for 610 Acct Earnings Total for 5210 Acct Benefits Total for 5210 Acct Total for 5210 Fund Earnings Total for 1829B Fund Total for 1829B Fund Benefits Total for 1829B Orgn Earnings Total for 120 Orgn Benefits Total for 120 Orgn Total for 120 Chart of Accounts Earnings Total for A Chart of Accounts Benefits Total for A Chart of Accounts Total for A
4-551
November 2010
Report Sample - by Earnings (Page 2 of 2)
REPORT : NHRBDST Fiscal Yr: 1995
Banner University Budget Distribution Report Reporting Period: 01-JUL-1994 To 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Report Type: Period Begin Date: Period End Date: Hierarchy: COAS: Fund Option: Orgn Option: Acct Option: Prog Option: Select Earnings: Select Benefits: Include Fringe Charge Back: Select Position Option Position Line Count:
Value ________________ 23808 1 01-JUL-1994 31-DEC-1994 E A A A A A A A A A Y Y N S KFTIME 55
Description ____________________________________________________________ Budget Status by Earnings/Benefits FOAP Fields As Exists All All All All All Earnings All Benefits Specific Positions
4-552
November 2010
Report Sample - by Position (Page 1 of 3)
Banner University Budget Distribution Report Reporting Period: 01-JUL-1994 To 31-DEC-1994 Reporting Period: 01-JUL-1994 To 31-DEC-1994
COAS: A
Organization: 120 Auxiliary Services Department Actv Locn Encumbered: Current Actual -------------6,249.96 75.50 322.90 6,249.96 398.40 6,648.36 42,630.94 Fiscal Actual ------------6,249.96 75.50 322.90 6,249.96 398.40 6,648.36 Annual Budget ------------.00 .00 .00 .00 .00 .00 Variance --------
Fund Orgn Acct Prog 1829B 120 5210 100 Position: KFTIME Secretary *RG FIM FIO
Fica Medicare Fica Old Age Posn Earnings Total: KFTIME Posn Benefits Total: KFTIME Position Total for KFTIME . . . Fund Orgn Acct Prog Actv 1829B 120 5210 610 Position: KFTIME Secretary *RG OT VAC FIM FIO
Locn Encumbered: Current Actual -------------38,037.49 .00 .00 459.67 1,020.54 38,037.49 1,480.21 39,517.70 38,037.49 1,480.21 39,517.70 44,287.45 1,878.61 46,166.06 42,630.94 Fiscal Actual ------------38,037.49 .00 .00 459.67 1,020.54 38,037.49 1,480.21 39,517.70 38,037.49 1,480.21 39,517.70 44,287.45 1,878.61 46,166.06 Annual Budget ------------175,000.00 17,500.00 12,500.00 4,750.00 3,750.00 205,000.00 8,500.00 213,500.00 205,000.00 8,500.00 213,500.00 205,000.00 8,500.00 213,500.00 Variance -------21.74 .00 .00 9.68 27.21 18.55 17.41 18.51 18.55 17.41 18.51 21.60 22.10 21.62
Overtime Pay Vacation Pay Fica Medicare Fica Old Age Posn Earnings Total: KFTIME Posn Benefits Total: KFTIME Position Total for KFTIME Prog Earnings Total for 610 Prog Benefits Total for 610 Prog Total for 610 Acct Earnings Total for 5210 Acct Benefits Total for 5210 Acct Total for 5210
4-553
November 2010
Fund Fund Fund Orgn Orgn Orgn
Earnings Total for Benefits Total for Total for 1829B Earnings Total for Benefits Total for Total for 120
1829B 1829B 120 120
44,287.45 1,878.61 46,166.06 76,074.96 2,960.40 79,035.36 76,074.96 2,960.40 79,035.36
44,287.45 1,878.61 46,166.06 76,074.96 2,960.40 79,035.36 76,074.96 2,960.40 79,035.36
205,000.00 8,500.00 213,500.00 410,000.00 17,000.00 427,000.00 410,000.00 17,000.00 427,000.00
21.60 22.10 21.62 18.55 17.41 18.51 18.55 17.41 18.51
Chart of Accounts Earnings Total for A Chart of Accounts Benefits Total for A Chart of Accounts Total for A
Banner University Budget Distribution Report Reporting Period: 01-JUL-1994 To 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission. Value ________________ 23806 2 01-JUL-1994 31-DEC-1994 E A A A A A A A A A Y Y N S KFTIME 55
Description ____________________________________________________________ Budget Status by Earnings/Benefits within Position FOAP Fields As Exists All All All All All Earnings All Benefits Specific Positions
4-554
November 2010
Report Sample - by Position Class (Page 1 of 2)
REPORT : NHRBDST Fiscal Yr: 1995 COAS: A Fund Orgn 1811 120 Posn Class: *RG Fund Orgn 1829B 120 Posn Class: *RG OT VAC FIM FIO . Acct Prog Actv Locn 5210 610 F1001 Full Time Secretary
Banner University Budget Distribution Report Reporting Period: 01-JUL-1994 To 31-DEC-1994
Organization: 120 Auxiliary Services Department Acct Prog Actv Locn 5220 610 F1001 Full Time Secretary
Posn: KFTIME Current Actual -------------31,787.51
Secretary Fiscal Actual ------------31,787.51
Encumbered: 42,630.94 Annual Budget Variance -------------------175,000.00 18.16
Overtime Pay Vacation Pay Fica Medicare Fica Old Age Posn Earnings Total: KFTIME Posn Benefits Total: KFTIME Position Total for KFTIME Posn. Class Earnings for F1001 Posn. Class Benefits for F1001 Position Class Total for F1001 Prog Earnings Total for 610 Prog Benefits Total for 610 Prog Total for 610 Acct Earnings Total for 5210 Acct Benefits Total for 5210 Acct Total for 5210 Fund Earnings Total for 1829B Fund Benefits Total for 1829B Fund Total for 1829B Orgn Earnings Total for 120 Orgn Benefits Total for 120 Orgn Total for 120 Chart of Accounts Earnings Total for A Chart of Accounts Benefits Total for A Chart of Accounts Total for A
Posn: KFTIME Current Actual -------------38,037.49 .00 .00 459.67 1,020.54 38,037.49 1,480.21 39,517.70 38,037.49 1,480.21 39,517.70 38,037.49 1,480.21 39,517.70 44,287.45 1,878.61 46,166.06 44,287.45 1,878.61 46,166.06 76,074.96 2,960.40 79,035.36 76,074.96 2,960.40 79,035.36
test - salary dist Fiscal Actual ------------38,037.49 .00 .00 459.67 1,020.54 38,037.49 1,480.21 39,517.70 38,037.49 1,480.21 39,517.70 38,037.49 1,480.21 39,517.70 44,287.45 1,878.61 46,166.06 44,287.45 1,878.61 46,166.06 76,074.96 2,960.40 79,035.36 76,074.96 2,960.40 79,035.36
Encumbered: 42,630.94 Annual Budget Variance -------------------175,000.00 21.74 17,500.00 .00 12,500.00 .00 4,750.00 9.68 3,750.00 27.21 205,000.00 18.55 8,500.00 17.41 213,500.00 18.51 205,000.00 18.55 8,500.00 17.41 213,500.00 18.51 205,000.00 18.55 8,500.00 17.41 213,500.00 18.51 205,000.00 21.60 8,500.00 22.10 213,500.00 21.62 205,000.00 21.60 8,500.00 22.10 213,500.00 21.62 410,000.00 18.55 17,000.00 17.41 427,000.00 18.51 410,000.00 18.55 17,000.00 17.41 427,000.00 18.51
4-555
November 2010
Report Sample - by Position Class (Page 2 of 2)
REPORT : NHRBDST Fiscal Yr: 1995 tht
Banner University Budget Distribution Report Reporting Period: 01-JUL-1994 To 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission.
Value ________________ 23809 3 01-JUL-1994 31-DEC-1994 E A A A A A A A A A Y Y N S KFTIME 55
Description ____________________________________________________________ Budget Status by Earnings/Benefits within Position Class FOAP Fields As Exists All All All All All Earnings All Benefits Specific Positions
4-556
November 2010
Organization Payroll Distribution (NHRDIST)

Description
To use this report, the Banner Human Resources System and the Banner Finance System must both be installed at your site. (If both the Banner Finance indicator and the Banner Human Resources indicator on the Installation Control Form (GUAINST) are set to Y, both systems are installed at your site.) The Detail Report prints the following information for each FOAPAL distribution covered by the report: data for each employee's position, including the employee's current amounts and/or hours for each specified earnings and the amounts for each specified benefit. This information is followed by the FOAPAL summary totals. The Summary Report prints only the FOAPAL summary totals for each chart of accounts covered by the report.
Parameters
Name
Description/Values
Required?
Default
Validation
Report Type
Report type indicator: D S Detail Summary
Yes
None
Sort Option
Sort option: H D Sort by Home Organization. Sort by FOAPAL distribution organization.
Yes
None
Report Begin Date Report End Date Pay ID
First date for which report data is to be printed Yes Last date for which report data is to be printed Yes Pay ID identifying the payroll for which data No is to be printed. This is a repeating parameter. Wild cards are allowed; for example, A% identifies all pay IDs starting with A. When this field is left blank, all pay IDs are chosen.
None None All
None None PTRPICT
4-557
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Hierarchy Option
Hierarchy for report: E As exists. This value specifies that all FOAPALs are to be reported as they exist on the database. Data are not to be rolled up to higher fields or higher levels. Roll up to specified FOAP fields. (You will specify the fields in applicable parameters, as described below.) Roll up to a specified level for each FOAP. (You will specify the levels in applicable parameters, as described below.)
Yes
None
If you have set this parameter to E or F, skip to the Chart of Accounts parameter. If you have set the parameter to L, go to the Fund Level parameter. When Hierarchy Option equals L and Fund Level equals E (see below), then all funds are reported at the existing level. This gives you the option to just roll to organization level 1 (via the Orgn Level parameter) and report the remaining FOAP data as it exists. Fund Level Fund level for the report. Enter E (as exists) to No indicate that funds are not to be rolled up to a higher level, or enter a number from 1 through 5 to identify a level to which data is to be rolled. Organization level for the report. Enter E (as No exists) to indicate that organizations are not to be rolled up to a higher level, or enter a number from 1 through 8 to identify a level to which data is to be rolled. 1 None
Orgn Level
None
4-558
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Acct Level
Account level for the report. Enter E (as exists), to indicate that accounts are not to be rolled up to a higher level, or enter a number from 1 through 4 to identify a level to which data is to be rolled. Program level for the report. Enter E (as exists) to indicate that programs are not to be rolled up to a higher level, or enter a number from 1 through 5 to identify a level to which data is to be rolled. Chart of accounts to be covered in the report, that is., a FOAPAL distribution chart. This is a repeating parameter.
No
None
Prog Level
No
None
Chart of Accounts
None
FTVCOAS
If you set Sort Option to D (Sort by FOAPAL Distribution Organization), take one of these steps: If Hierarchy Option equals L (Level roll up), skip to the Employee Class parameter. If Hierarchy Option equals E (as exists) or F (FOAP field roll up), skip to the Fund Option parameter. If you set Sort Option to H (Sort by Home Organization), take one of the following steps: If your home organization chart of accounts differs from your distribution chart of accounts, go to the Home Orgn Chart parameter below. Otherwise, skip to the Home Organization Option parameter. Home Orgn Chart Home organization chart. Enter this No parameter only if your home organization chart differs from your distribution chart. This is a nonrepeating parameter. None FTVCOAS
When you enter this parameter the four home organization parameters below relate to the home organization chart you specify here.
4-559
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Home Organization Option
Chart of accounts whose home organization No data is to be printed and the home organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all home organizations within chart H. This is a repeating parameter. A All. Requests that data be printed for all home organizations. If you enter this value and you have set the Hierarchy Option parameter to L, skip to the Employee Class parameter. If you enter this value and Hierarchy Option equals E or F, skip to the Fund Option parameter. R Range. Requests that data be printed for a specific range of home organizations. If you enter this value, go to the From Home Orgn parameter. Wild Card. Requests that data be printed for one or more specific home organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Home Orgn parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing
All
FTVORGN
4-560
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Specific. Requests that data be printed for one or more specific home organizations, and indicates that you will enter exact codes to identify these organizations. If you enter this value, skip to the Home Orgn parameter. No None None
From Home Orgn
Chart of accounts whose home organization data is to be printed and the first home organization in the range of home organizations for which data is to be printed. The codes are separated by a comma, for example, H,110. This is a repeating parameter. Chart of accounts whose home organization data is to be printed and the last home organization in the range. The codes are separated by a comma, for example, H,120. This is a repeating parameter. After entering this parameter take one of the following steps: If you have set the Hierarchy Option to L, skip to the Employee Class parameter. Otherwise, skip to the Fund Option parameter.
To Home Orgn
No
None
None
Home Orgn
Chart of accounts whose home organization data is to be printed and a specific home organization for which data is to be printed. The codes are separated by a comma. This is a repeating parameter.
All
None
FTVORGN
4-561
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
You can specify several charts and can enter several home organizations for each chart; for example, you can enter: A,200 G,200 G,300 If you set the Home Organization Option to W, you can use wild cards to identify home organizations. If Home Organization Option equals S, you must specify exact codes. Fund Option If Hierarchy Option equals F, skip this parameter and go directly to the Fund parameter. If Hierarchy equals E, enter one of the values below. Codes identifying the chart of accounts whose fund data is to be printed and the fund(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all funds within chart H. This is a repeating parameter. A All. Requests that data be printed for all funds. If you enter this value, skip to the Orgn Option parameter. Range. Requests that data be printed for a specific range of funds. If you enter this value, go to the From Fund parameter. No All None
4-562
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Wild Card. Requests that data be printed for one or more specific funds, and indicates that you will use wild cards when you identify these funds. If you enter this value, skip to the Fund parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
Specific. Requests that data be printed for one or more specific funds, and indicates that you will enter exact codes to identify these funds. If you enter this value, skip to the Fund parameter. No None None
From Fund
Chart of accounts whose fund data is to be printed and the first fund in the range of funds for which data is to be printed. The codes are separated by a comma, for example, H,1000. This is a repeating parameter. Chart of accounts whose fund data is to be printed and the last fund in the range. The codes are separated by a comma, for example, H,2000. This is a repeating parameter.
To Fund
No
None
None
4-563
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Fund
Chart of accounts whose fund data is to be No printed and a specific fund for which data is to be printed. The codes are separated by a comma. This is a repeating parameter. If you have set Hierarchy Option to E, then you can specify several fund codes for each chart; for example, you can enter: A,1000 A,1001 G,2000 H,1000 If you set the Fund Option to W, you can use wild cards to identify funds. If Fund Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one fund code for each chart and cannot use wild cards; for example, you can enter: A,1000 G,1000 H,1000
None
FTVFUND
4-564
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Orgn Option
If Hierarchy Option equals F, skip this No parameter and go directly to the Orgn parameter. If Hierarchy Option equals E, enter one of the values below. Chart of accounts whose organization data is to be printed and the organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all organizations within chart H. This is a repeating parameter. There are four options for specifying organizations: A All. Requests that data be printed for all organizations. If you enter this value, skip to the Acct Option parameter. Range. Requests that data be printed for a specific range of organizations. If you enter this value, go to the From Orgn parameter. Wild Card. Requests that data be printed for one or more specific organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Orgn parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
All
None
4-565
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
From Orgn
Chart of accounts whose organization data is to be printed and the first organization in the range of organizations for which data is to be printed. The codes are separated by a comma, for example, H,120. This is a repeating parameter. Chart of accounts whose organization data is to be printed and the last organization in the range. The codes are separated by a comma, for example, H,129. This is a repeating parameter.
To Orgn
No
None
None
4-566
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Orgn
Chart of accounts whose organization data is to be printed and a specific organization for which data is to be printed. The codes are separated by a comma, for example, H,120. This is a repeating parameter. If you set Hierarchy Option to E, then you can enter several organization codes for each chart. If you set the Orgn Option to W, you can use wild cards. If Orgn Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one organization code for each chart and cannot use wild cards. (See Fund parameter examples above.)
No
None
FTVORGN
Acct Option
If Hierarchy Option equals F, skip this No parameter and go directly to the Acct parameter. If Hierarchy Option equals E, enter one of the values below. Chart of accounts whose account data is to be printed and the account(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all accounts within chart H. This is a repeating parameter.
All
None
4-567
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
All. Requests that data be printed for all accounts. If you enter this value, skip to the Prog Option parameter. Range. Requests that data be printed for a specific range of accounts. If you enter this value, go to the From Acct parameter. Wild Card. Requests that data be printed for one or more specific accounts, and indicates that you will use wild cards when you identify these accounts. If you enter this value, skip to the Acct parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
Specific. Requests that data be printed for one or more specific accounts, and indicates that you will use exact codes to identify the accounts. If you enter this value, skip to the Acct parameter. No None None
From Acct
Chart of accounts whose account data is to be printed and the first account in the range of accounts for which data is to be printed. The codes are separated by a comma, for example, H,5210. This is a repeating parameter. Chart of accounts whose account data is to be printed and the last account in the range. The codes are separated by a comma, for example, H,5220. This is a repeating parameter.
To Acct
No
None
None
4-568
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Acct
Chart of accounts whose account data is to be No printed and the specific account within that chart for which data is to be printed. The codes are separated by a comma, for example, H,5210. This is a repeating parameter. If you set Hierarchy Option to E, then you can enter several accounts for each chart. If you have set the Acct Option to W, you can use wild cards. If Acct Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one account code for each chart and cannot use wild cards. (See the Fund parameter examples above.)
None
FTVACCT
Prog Option
If Hierarchy Option equals F, skip this No parameter and go directly to the Prog parameter. If Hierarchy Option equals E, enter one of the values below. Chart of accounts whose program data is to be printed and the program(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all programs within chart H. This is a repeating parameter. A All. Requests that data be printed for all programs. If you enter this value, skip to the Employee Class parameter. Range. Requests that data be printed for a specific range of programs. If you enter this value, go to the From Prog parameter.
All
None
4-569
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Wild Card. Requests that data be printed for one or more specific programs and indicates that you will use wild cards when you identify these programs. If you enter this value, skip to the Prog parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
Specific. Requests that data be printed for one or more specific programs, and that you will use exact codes to identify these programs. If you enter this value, skip to the Prog parameter. No None None
From Prog
Chart of accounts whose program data is to be printed and the first program in the range of programs for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. Chart of accounts whose program data is to be printed and last program in the range. The codes are separated by a comma, for example, H,610. This is a repeating parameter.
To Prog
No
None
None
4-570
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Prog
Chart of accounts whose program data is to be printed and a specific program for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. If you set Hierarchy Option to E, then you can specify several program codes for each chart. If you set the Prog Option to W, you can use wild cards. If Prog Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one program code for each chart and cannot use wild cards. (See Fund parameter examples above.)
No
None
FTVPROG
Employee Class
Employee class for which data is to be printed. This is a repeating parameter. Wild cards can be used. ID code identifying employee for whom data is to be printed. This is a repeating parameter. Wild cards are allowed. Earn code for which data is to be printed. This is a repeating parameter. Wild cards can be used. If this field is left blank, data is printed for all earn codes.
No
All
PTQECLS
Employee ID
No
All
POAIDEN
Earn Code
No
All
PTQEARN
Benefit Code
Benefit for which data is to be printed. This is No a repeating parameter. Wild cards can be used. If this field is left blank, data is printed for all benefits.
All
PTQBDCA
4-571
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Fringe charge back inclusion indicator: Y N Include fringe charge back data. Do not include fringe charge back data.
Yes
None
Include Earnings Hours
Earnings hours inclusion indicator: Y N Include earnings hours. Do not include earnings hours.
Yes
None
When you specify the To Date Totals Option parameter, you should note that the to-date end date (that is, the last date whose data are to be used in calculating the QTD, YTD, and FTD totals) can either be the date the report is run or the report end date. You specify which of these values is to be used in the Use Report End Date As To Date End Date parameter below. To Date Amounts Option To-date totals indicator: N Do not include quarter-to-date (QTD), calendar year-to-date (YTD), or fiscal year-to-date (FTD) amounts. Include QTD amounts for all data entered from the start of the quarter containing the Report Begin Date to the to-date end date. Include YTD amounts for all data entered from the start of the calendar year containing the Report Begin Date to the to-date end date. Include FTD amounts for all data entered from the start of the fiscal year containing the Report Begin Date to the to-date end date. Yes N None
4-572
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Include Earnings
Earnings inclusion indicator: Y N Include earnings data Do not include earnings data
Yes
None
Include Benefits
Benefits inclusion indicator: Y N Include benefits data Do not include benefits data
Yes
None
Level of Payroll Detail
Payroll detail inclusion indicator Y N Include detail information for each pay event covered by the report. Do not include detail information for pay events.
Yes
None
Report End as To Date End
Code indicating whether the system is to use No the report end date as the to-date end date when calculating QTD, YTD, and FTD totals: Y N Indicates that totals are to be calculated to the report end date Indicates that totals are to be calculated to the date the report is run
None
4-573
November 2010
REPORT : NHRDIST COAS: H Organization: 120 TreasuryDepartment Fund Orgn Acct Prog Actv Locn 2232 120 5120 610 ID: 888020010 Name: Rademacher, Kareem ECLS: AP Administrative Professionals REG 1994 TM 7 0 REG 1994 TM 8 0 REG 1994 TM 9 0 REG 1994 TM 10 0 REG 1994 TM 11 0 REG 1994 TM 12 0 REG Regular Pay FIM 1994 TM 12 0 FIM Fica Medicare FIO 1994 TM 12 0 FIO Fica Old Age HME 1994 TM 12 0 HME Health-MESA Position Earnings Total for AP2001 00 Position Benefits Total for AP2001 00 Position Total for AP2001 00 Employee Earnings Total for 888020010 Employee Benefits Total for 888020010 Employee Total for 888020010 Prog Earnings Total for 610 Prog Benefits Total for 610 Prog Total for 610 Acct Earnings Total for 5120 Acct Benefits Total for 5120 Acct Total for 5120 Fund Earnings Total for 2232 Fund Benefits Total for 2232 Fund Total for 2232 Orgn Earnings Total for 120 Orgn Benefits Total for 120 Orgn Total for 120 . . . Chart of Accounts Earnings Total for H Chart of Accounts Benefits Total for H Chart of Accounts Total for H
Banner University Orgn Payroll Distribution Reporting Period: 01-JUL-1994 To: 31-DEC-1994 Hours Amount YTD Hours
YTD Amount
Home Orgn H 120 Treasury Department Posn: AP2001 00 173.33 2,916.67 173.33 2,916.67 173.33 2,916.67 173.33 2,916.67 173.33 2,916.67 173.33 2,916.67 1,039.98 17,500.02 1,039.98 42.29 42.29 180.84 180.84 200.00 200.00 1,039.98 17,500.02 1,039.98 423.13 1,039.98 17,923.15 1,039.98 1,039.98 17,500.02 1,039.98 423.13 1,039.98 17,923.15 1,039.98 1,039.98 17,500.02 1,039.98 423.13 1,039.98 17,923.15 1,039.98 1,039.98 17,500.02 1,039.98 423.13 1,039.98 17,923.15 1,039.98 1,039.98 17,500.02 1,039.98 423.13 1,039.98 17,923.15 1,039.98 1,039.98 17,500.02 1,039.98 423.13 1,039.98 17,923.15 1,039.98
17,500.02 42.29 180.84 200.00 17,500.02 423.13 17,923.15 17,500.02 423.13 17,923.15 17,500.02 423.13 17,923.15 17,500.02 423.13 17,923.15 17,500.02 423.13 17,923.15 17,500.02 423.13 17,923.15
12,660.09 12,660.09
269,413.12 4,693.29 274,106.41
12,660.09 12,660.09
269,413.12 4,693.29 274,106.41
4-574
November 2010
REPORT : NHRDIST HT
Banner University Orgn Payroll Distribution Reporting Period: 01-JUL-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Report Type: Sort Option: Period Begin Date: Period End Date: Hierarchy: COAS: Fund Option: Orgn Option: Acct Option: Prog Option: COAS: Fund Option: Orgn Option: Acct Option: Prog Option: Select Earnings: Include Hours : Select Benefits: Include Fringe Charge Back: To Date Totals Option: Use Report End Date As To Date End Date: Include Payroll Detail: Line Count:
Value ________________ 23419 D D 01-JUL-1994 31-DEC-1994 E A A A A A A A A A H H A H A H A H A Y Y Y N Y Y Y 55
Message ____________________________________________________________ Detail Report Sort By FOAPAL Distribution Organization FOAP Fields As Exists All All All All All All All All
Calendar Year To Date Totals
4-575
November 2010
PAGE REPORT : NHRDIST Banner University Orgn Payroll Distribution Reporting Period: 01-JUL-1994 To: 31-DEC-1994
COAS: A Home Organization: 220 Payroll Office Fund Orgn Acct Prog Actv Locn 1000 220 5120 610 DPA Deferred Pay Amount REG Regular Pay DEN Dental Insurance FIM Fica Medicare FIO Fica Old Age HBC Health-Blue Cross/Blue Shield HEA Health Insurance Prog Earnings Total for 610 Prog Benefits Total for 610 Prog Total for 610 Acct Earnings Total for 5120 Acct Benefits Total for 5120 Acct Total for 5120 Orgn Earnings Total for 220 Orgn Benefits Total for 220 Orgn Total for 220 Fund Earnings Total for 1000 Fund Benefits Total for 1000 Fund Total for 1000 Home Organization Earnings Total for A 220 Home Organization Benefits Total for A 220 Home Organization Total for A 220 Chart of Accounts Earnings Total for A Chart of Accounts Benefits Total for A Chart of Accounts Total for A Hours 3.00 260.01 Amount 7,153.11 21,459.39 300.00 290.50 1,242.13 300.00 375.00 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 30,681.25 2,667.63 33,348.88 YTD Hours 3.00 260.01 YTD Amount 7,153.11 21,459.39 300.00 290.50 1,242.13 300.00 375.00 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 28,612.50 2,507.63 31,120.13 30,681.25 2,667.63 33,348.88
263.01 263.01 263.01 263.01 263.01 263.01 263.01 263.01 263.01 263.01 352.01 352.01
263.01 263.01 263.01 263.01 263.01 263.01 263.01 263.01 263.01 263.01 352.01 352.01
4-576
November 2010
REPORT : NHRDIST
Banner University Orgn Payroll Distribution Reporting Period: 01-JUL-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Report Type: Sort Option: Period Begin Date: Period End Date: Hierarchy: COAS: Home Orgn Option: Fund Option: Orgn Option: Acct Option: Prog Option: COAS: Home Orgn Option: Fund Option: Orgn Option: Acct Option: Prog Option: Select Earnings: Include Hours : Select Benefits: Include Fringe Charge Back: To Date Totals Option: Use Report End Date As To Date End Date: Include Payroll Detail: Line Count:
Value ________________ 23423 S H 01-JUL-1994 31-DEC-1994 E A A A A A A A A A A A H H A H A H A H A H A Y Y Y N Y N N 55
Message ____________________________________________________________ Summary Report Sort By Home Organization FOAP Fields As Exists All All All All All All All All All All
Calendar Year To Date Totals
4-577
November 2010
Effort Certification Report (NHRECRT)

Description
To use this report, the Banner Human Resources System and the Banner Finance System must both be installed at your site. (If both the Banner Finance indicator and the Banner Human Resources indicator on the Installation Control Form (GUAINST) are set to Y, both systems are installed at your site.) Provides FOAPAL information for specified grants or funds. For each grant or fund covered by the report, prints the following monthly data for each FOAPAL distribution: each employee's total amount for selected earnings, the percent of these earnings distributed to the FOAPAL, each employee's total amount for selected benefits, and the percent of these benefits distributed to the FOAPAL.
Parameters
Name
Description/Values
Required?
Default
Validation
Report Option
Sort option for the report: F G The report is to be sorted by funds. The report is to be sorted by grants.
Yes
F (by funds) None
Report Begin Date Report End Date Chart of Accounts
First date for which report data is to be printed Yes Last date for which report data is to be printed Yes Chart of accounts to be covered in the report. This is a repeating parameter. If you set the Report Option parameter to G skip to the Grant Option parameter. If you have set the parameter to F, go to the Fund Option parameter. Yes (on first appearance only)
None None None
None None FTVCOAS
Fund Option
Chart of accounts whose fund data is to be printed and the fund(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all funds within chart H. This is a repeating parameter.
No
All
None
4-578
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
All. Requests that data be printed for all funds. If you enter this value, skip to the Orgn Option parameter. Range. Requests that data be printed for a specific range of funds. If you enter this value, go to the From Fund parameter. Wild Card. Requests that data be printed for one or more specific funds, and indicates that you will use wild cards when you identify these funds. (By using a wild card you can identify several funds with one code; for example, A% identifies all fund codes starting with A). If you enter this value, skip to the Fund parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
Specific. Requests that data be printed for one or more specific funds, and indicates that you will enter exact codes to identify these funds. If you enter this value, skip to the Fund parameter. No None None
From Fund
Chart of accounts whose fund data is to be printed and the first fund in the range of funds for which data is to be printed. The codes are separated by a comma, for example, H,1000. This is a repeating parameter.
4-579
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
To Fund
Chart of accounts whose fund data is to be printed and the last fund in the range. The codes are separated by a comma, for example, H,2000. This is a repeating parameter.
No
None
None
Fund
Chart of accounts whose fund data is to be No printed and a specific fund for which data is to be printed. The codes are separated by a comma. Fund is a repeating parameter. You can specify several charts and several fund codes for each chart; for example, you can enter: A,1000 A,1001 G,2000 H,1000 If you set the Fund Option to W, you can use wild cards. If Fund Option equals S, you must specify exact codes.
None
FTVFUND
Orgn Option
Chart of accounts whose organization data is No to be printed and the organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all organizations within chart H. This is a repeating parameter.
All
None
4-580
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
All. Requests that data be printed for all organizations. If you enter this value, skip to the Acct Option parameter. Range. Requests that data be printed for a specific range of organizations. If you enter this value, go to the From Orgn parameter. Wild Card. Requests that data be printed for one or more specific organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Orgn parameter.
Note: Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
From Orgn
Chart of accounts whose organization data is to be printed and the first organization in the range of organizations for which data is to be printed. The codes are separated by a comma, for example, H,120. This is a repeating parameter.
4-581
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
To Orgn
Chart of accounts whose organization data is to be printed and the last organization in the range. The codes are separated by a comma, for example, H,129. This is a repeating parameter. Chart of accounts whose organization data is to be printed and a specific organization for which data is to be printed. The codes are separated by a comma, for example, H,120. Orgn is a repeating parameter. You can specify several charts and several organization codes for each chart. If you set the Orgn Option to W, you can use wild cards. If Orgn Option equals S, you must specify exact codes. (See Fund parameter examples above.)
No
None
None
Orgn
No
None
FTVORGN
Acct Option
Chart of accounts whose account data is to be printed and the account(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all accounts within chart H. This is a repeating parameter. A All. Requests that data be printed for all accounts. If you enter this value, skip to the Prog Option parameter.
No
All
None
4-582
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Range. Requests that data be printed for a specific range of accounts. If you enter this value, go to the From Acct parameter. Wild Card. Requests that data be printed for one or more specific accounts, and indicates that you will use wild cards when you identify these accounts. If you enter this value, skip to the Acct parameter.
Specific. Requests that data be printed for one or more specific accounts, and indicates that you will use exact codes to identify the accounts. If you enter this value, skip to the Acct parameter. No None None
From Acct
Chart of accounts whose account data is to be printed and the first account in the range of accounts for which data is to be printed. The codes are separated by a comma, for example, H,5210. This is a repeating parameter. Chart of accounts whose account data is to be printed and last account in the range. The codes are separated by a comma, for example, H,5220. This is a repeating parameter.
To Acct
No
None
None
4-583
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Acct
Chart of accounts whose account data is to be printed and a specific account for which data is to be printed. The codes are separated by a comma, for example, H,5210. Acct is a repeating parameter. You can specify several charts and several account codes for each chart. If you have set the Acct Option to W, you can use wild cards. If Acct Option equals S, you must specify exact codes. (See Fund parameter examples above.)
No
None
FTVACCT
Prog Option
Chart of accounts whose program data is to be printed and the program(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all programs within chart H. This is a repeating parameter. A All. Requests that data be printed for all programs. If you enter this value, skip to the Select Earnings Option parameter. Range. Requests that data be printed for a specific range of programs. If you enter this value, go to the From Prog parameter.
No
All
None
4-584
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Wild Card. Requests that data be printed No for one or more specific programs and indicates that you will use wild cards when you identify these programs. If you enter this value, skip to the Prog parameter.
All
None
Note: Whenever possible, use exact codes rather than wild cards since this practice speeds report processing
Specific. Requests that data be printed for one or more specific programs, and that you will use exact codes to identify these programs. If you enter this value, skip to the Prog parameter. None None
From Prog
Chart of accounts for which program data is to No be printed and the first program in the range of programs for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. Chart of accounts for which program data is to No be printed and the last program in the range. The codes are separated by a comma, for example, H,610. This is a repeating parameter.
To Prog
None
None
4-585
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Prog
Chart of accounts for which program data is to No be printed and a specific program for which data is to be printed. The codes are separated by a comma, for example, H,100. Prog is a repeating parameter. You can specify several charts and several program codes for each chart. If you have set the Prog Option to W, you can use wild cards. If Prog Option equals S, you must specify exact codes. (See Fund parameter examples above.)
None
FTVPROG
Grant Option
Chart of accounts whose grant data is to be printed and the grant(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all grants within chart H. This is a repeating parameter. A All. Requests that data be printed for all grants. If you enter this value, skip to the Select Earnings parameter. Range. Requests that data be printed for a specific range of grants. If you enter this value, go to the From Grant parameter.
No
All
None
4-586
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Wild Card. Requests that data be printed for one or more specific grants, and indicates that you will use wild cards when you identify these grants. If you enter this value, skip to the Grant parameter. Specific. Requests that data be printed for one or more specific grants, and that you will use exact codes to identify these grants. If you enter this value, skip to the Grant parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
From Grant
Chart of accounts whose grant data is to be printed and the first grant in the range of grants for which data is to be printed. The codes are separated by a comma, for example, H,1050. This is a repeating parameter. Chart of accounts whose grant data is to be printed and the last grant in the range. The codes are separated by a comma, for example, H,2050. This is a repeating parameter.
No
None
None
To Grant
No
None
None
4-587
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Grant
Chart of accounts whose grant data is to be printed and a specific grant for which data is to be printed. The codes are separated by a comma, for example, H,1050. Grant is a repeating parameter. You can specify several charts and several grant codes for each chart. If you have set the Grant Option to W, you can use wild cards. If Grant Option equals S, you must specify exact codes. (See Fund parameter examples above.)
No
None
FTVPROG
Select Earnings
Code specifying whether earnings are to be selected: Y N All or some earnings are to be selected for the report. No earnings are to be selected for the report.
Yes
Y(es)
None
Earn Code
Earn code for which data is to be printed. This is a repeating parameter. Wild cards can be used. If this field is left blank, all earn codes are selected. Code specifying whether benefits are to be selected: Y N All or some benefits are to be selected for the report. No benefits are to be selected for the report.
No
All
None
Select Benefits
Yes
Y(es)
None
4-588
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Benefits Code
Benefit for which data is to be printed. This is No a repeating parameter. Wild cards can be used. If this field is left blank, all benefits are selected. Fringe charge back inclusion indicator: Y N Include fringe charge back data. Do not include fringe charge back data. No Yes
All
None
None
Employee Class
Employee class for which data is to be printed. This is a repeating parameter. Wild cards can be used. Pay ID identifying the payroll for which data is to be printed. This is a repeating parameter. Wild cards are allowed.
All
PTRECLS
Pay ID
No
All
PTRPICT
Page Break by Employee Parameter indicating whether information for each employee is to start on a new page: Y N Print FOAPAL Totals Y N Break pages by employee Do not break pages by employee Print FOAPAL totals. Do not print FOAPAL totals.
Yes
N(o)
None
Yes
N(o)
None
4-589
November 2010
PAGE 8 REPORT : NHRECRT
Banner University Effort Certification Report Reporting Period: 01-AUG-1994 To: 31-DEC-1994 Current Unrestricted Fund Payroll Office Prog 610 Actv Locn Total
COAS: A Fund: 1000 Grant: Orgn: 220 Fund 1000 Orgn 220 Acct 5120
01-AUG-94 01-SEP-94 01-OCT-94 01-NOV-94 01-DEC-94 31-AUG-94 30-SEP-94 31-OCT-94 30-NOV-94 31-DEC-94 Employee: Jones,Robert M ID: 777010001 Earnings % Distr Benefits % Distr Total: .00 135.00 100.00 % 9,537.50 93.87 % 622.54 6.13 % 9,537.50 93.51 % 662.33 6.49 % 9,537.50 90.92 % 952.76 9.08 % .00 .00 .00
28,612.50 2,372.63 30,985.13
135.00 10,160.04 10,199.83 10,490.26 01-AUG-94 01-SEP-94 01-OCT-94 01-NOV-94 01-DEC-94 -
Prog Total for 610 31-AUG-94 : 135.00 30-SEP-94 : 10,160.04 31-OCT-94 : 10,199.83 30-NOV-94 : 10,490.26 31-DEC-94 : .00 -----------------------------Prog Total Amount: 30,985.13 Acct Total for 5120 31-AUG-94 : 135.00 30-SEP-94 : 10,160.04 31-OCT-94 : 10,199.83 30-NOV-94 : 10,490.26 31-DEC-94 : .00 -----------------------------30,985.13
01-AUG-94 01-SEP-94 01-OCT-94 01-NOV-94 01-DEC-94
Acct Total Amount:
4-590
November 2010
01-AUG-94 01-SEP-94 01-OCT-94 01-NOV-94 01-DEC-94
Orgn Total for 220 31-AUG-94 : 135.00 30-SEP-94 : 10,160.04 31-OCT-94 : 10,199.83 30-NOV-94 : 10,490.26 31-DEC-94 : .00 -----------------------------Orgn Total Amount: 30,985.13
COAS: A Fund: 1000 Grant: Orgn: 220 01-AUG-94 01-SEP-94 01-OCT-94 01-NOV-94 01-DEC-94
Current Unrestricted Fund Payroll Office Fund Total for 1000 31-AUG-94 : 4,308.83 30-SEP-94 : 12,104.99 31-OCT-94 : 12,144.93 30-NOV-94 : 12,435.20 31-DEC-94 : .00 -----------------------------Fund Total Amount: 40,993.95
I certify that the above percentages for earnings and benefits as stated above are an accurate distribution of the individuals effort, except as noted, for the Fund: 1000 Current Unrestricted Fund and Orgn: 220 Payroll Office -------------------------------------------Signature of Department Head
4-591
November 2010
REPORT : NHRECRT
Banner University Effort Certification Report Reporting Period: 01-AUG-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered from Host Prompt.
Parameter Name _____________________________ Parameter Seq No: Sort Option: Begin Date: End Date: COAS Fund Option Orgn Option Acct Option Prog Option Select Earnings: Select Benefits: Include Fringe Charge Back: Page Break By Employee: Print FOAPAL Total: Line Count:
Value ________________ 21030 F 01-AUG-1994 31-DEC-1994 A A A A A A A A A Y Y N N Y 55
Message ____________________________________________________________ Sort By Fund
All All All All
4-592
November 2010
REPORT : NHRECRT
Banner University Effort Certification Report Reporting Period: 01-JUN-1994 To: 30-NOV-1994 Food Services - Cafe Treasury Department Prog 610 Actv Locn Total
COAS: A Fund: 1829B Grant: Orgn: 120 Fund 1829B Orgn 120 Acct 5210
01-JUN-94 01-JUL-94 01-AUG-94 01-SEP-94 01-OCT-94 01-NOV-94 30-JUN-94 31-JUL-94 31-AUG-94 30-SEP-94 31-OCT-94 30-NOV-94 Employee: Natarajan,Gowri ID: K2 Earnings % Distr Benefits % Distr Total: .00 .00 .00 1,041.67 46.45 % 79.70 3.55 % 1,121.37 1,041.67 46.45 % 79.69 3.55 % 1,121.36 1,041.67 46.45 % 79.69 3.55 % 1,121.36 1,041.67 46.45 % 79.69 3.55 % 1,121.36 1,041.67 46.45 % 79.70 3.55 % 1,121.37
5,208.35 398.47 5,606.82
I certify that the above percentages for earnings and benefits as stated above are an accurate distribution of my effort, except as noted. -------------------------------------------Employee Signature
4-593
November 2010
REPORT : NHRECRT
Banner University Effort Certification Report Reporting Period: 01-JUN-1994 To: 30-NOV-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered from Host Prompt.
Parameter Name _____________________________ Parameter Seq No: Sort Option: Begin Date: End Date: COAS Fund Option Orgn Option Acct Option Prog Option Select Earnings: Select Benefits: Include Fringe Charge Back: Page Break By Employee: Print FOAPAL Total: Line Count:
Value ________________ 21025 F 01-JUN-1994 30-NOV-1994 A A A A A A A A A Y Y N Y N 55
Message ____________________________________________________________ Sort By Fund
All All All All
4-594
November 2010
Employee Distributions Report (NHREDST)

Description
To use this report, the Banner Human Resources System and the Banner Finance System must both be installed at your site. (If both the Banner Finance indicator and the Banner Human Resources indicator on the Installation Control Form (GUAINST) are set to Y, both systems are installed at your site.) For each employee's position, provides one of the following sets of data for each FOAPAL distribution: The sum of selected earnings distributed to the FOAPAL, the percent of the selected earnings represented by the reported sum, and the percent of the employee's total earnings represented by the sum of all earnings distributed to the FOAPAL. The sum of selected benefits distributed to the FOAPAL, the percent of the selected benefit amount represented by the reported sum, and the percent of the employee's total benefit amount represented by the sum of all benefits distributed to the FOAPAL. The sum of selected earnings and benefits distributed to the FOAPAL, the percent of the employee's total amount for selected salary items (i.e., total selected earnings plus total selected benefits) represented by the reported sum, and the percent of the employee's total job amount represented by the sum of all earnings and benefits distributed to the FOAPAL. In each case, the first percent value is called the report percent, and the second percent value is called the total percent. The report percent and the total percent are the same if all earnings or benefits have been selected for the report. They differ, however, if only some of the earnings or benefits are being reported. For example, if a report includes only earnings figures and all earnings are being reported, both the report percent and the total percent reflect all earnings. If, however, only selected earnings are being reported, the report percent reflects only the selected earnings and the total percent reflects all earnings. The total percent, thus, provides a more accurate reflection of the employee's job distribution. The NHREDST report can include the total hours for selected earnings. Hours figures are not, however, used in calculating the report percent or the total percent. Fringe charge backs can be included in benefit totals. The following example shows how FOAPAL distribution data is reported in the NHREDST report. This report shows data only for benefits. All benefits have been selected. Thus, the report percent and the total percent for each FOAPAL are each calculated by dividing the distribution amount (for example, 3138.40 for the first FOAPAL) by the total job amount (4553.03).
4-595
November 2010
Fund
Org
Acct
Prog
Hrs
Amt
Rpt %
Tot %
210100 210100 831421 830771
840613 810615 831421 830771
51111 51111 51111 51111
PC205 ID210 SP2 SP2 Employee Total
3138.40 291.40 682.95 440.28 4553.03
68.93 6.40 15.00 9.67 100.00
68.93 6.40 15.00 9.67 100.00
Parameters
Name
Description/Values
Required?
Default
Validation
Sort Option
Sort option: H E Sort by Home Organization. Sort by employee name (first by last name and then by first name)
Yes
E (by employee name)
None
Begin Date End Date Pay ID
First date for which report data is to be printed Yes Last date for which report data is to be printed Yes Pay ID identifying the payroll for which data No is to be printed. This is a repeating parameter. Wild cards are allowed; for example, A% identifies all pay IDs starting with A. When this field is left blank, all Pay IDs are chosen. Chart of accounts to be covered in the report, that is., a FOAPAL distribution chart. This is a repeating parameter. Yes (on first appearance only)
None None All
None None PTRPICT
Chart of Accounts
None
FTVCOAS
If your home organization chart of accounts differs from your distribution chart of accounts, the following four parameters relate to the home organization chart, that is, the chart identified in the Home Orgn Chart parameter below.
4-596
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Home Organization Option
Chart of accounts whose home organization No data is to be printed and the home organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all home organizations within chart H. This is a repeating parameter. A All. Requests that data be printed for all home organizations. If you enter this value, take one of the following steps: If your home organization chart differs from your distribution chart, skip to the Home Orgn Chart parameter below. Otherwise, skip to the Employee Class parameter. Range. Requests that data be printed for a specific range of home organizations. If you enter this value, go to the From Home Orgn parameter. Wild Card. Requests that data be printed for one or more specific home organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Home Orgn parameter. Whenever possible, use exact codes rather than wild cards since this practice speeds report processing.
All
None
4-597
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Specific. Requests that data be printed for one or more specific home organizations, and indicates that you will identify these organizations with exact codes. If you enter this value, skip to the Home Orgn parameter. No None None
From Home Orgn
Chart of accounts whose home organization data is to be printed and the first home organization in the range of organizations for which data is to be printed. The codes are separated by a comma, for example, H,110. This is a repeating parameter. Chart of accounts whose home organization data is to be printed and the last home organization in the range. The codes are separated by a comma, for example, H,120. This is a repeating parameter. After entering this parameter, take one of the following steps: If your home organization chart differs from your distribution chart, skip to the Home Orgn Chart parameter below. Otherwise, skip to the Employee Class parameter.
To Home Orgn
No
None
None
4-598
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Home Orgn
Chart of accounts whose home organization data is to be printed and a specific home organization for which data is to be printed. The codes are separated by a comma. This is a repeating parameter. You can specify several charts and several home organizations for each chart; for example, you can enter: A,200 G,200 G,300 If the Home Organization Option equals W, you can use wild cards. If Home Organization Option equals S, you must specify exact codes.
No
None
None
Home Orgn Chart
Your home organization chart. Enter this No parameter only if your home organization chart differs from your distribution chart. This parameter is a nonrepeating parameter. Employee class for which data is to be printed. This is a repeating parameter. Wild cards can be used. ID code identifying employee for whom data is to be printed. This is a repeating parameter. Wild cards are allowed. No
None
FTVCOAS
Employee Class
All
PTQECLS
Employee ID
No
All
POAIDEN
4-599
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Select Earnings
Code specifying whether earnings are to be selected: Y N All or some earnings are to be selected for the report. No earnings are to be selected for the report.
Yes
Y(es)
None
Earn Code
Earn code for which data is to be printed. This is a repeating parameter. Wild cards can be used. If this field is left blank, all earn codes are selected. Code specifying whether benefits are to be selected: Y N All or some benefits are to be selected for the report. No benefits are to be selected for the report.
No
All
None
Select Benefits
No
None
Benefit Code
Benefit for which data is to be printed. This is No a repeating parameter. Wild cards can be used. If this field is left blank, all benefit codes are selected. Fringe charge back inclusion indicator: Y N Include fringe charge back data. Do not include fringe charge back data. Yes
All
None
None
4-600
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Include Earnings Hours
Earnings hours inclusion indicator: Y N Include earnings hours. Do not include earnings hours.
Yes
None
Certification Option
Code that indicates if certification of hours or signature is required on report. If yes, the Head of Department Certification appears when the Sort Option is H(ome Organization) or the Employee Certification appears when the Sort Option is E(mployee). Y N Include certification. Do not include certification.
Yes
None
4-601
November 2010
Report Sample - One Benefit Selected (Page 1 of 2)
REPORT: NHREDST
Banner University Employee Distributions Report Reporting Period: 01-JUN-1994 To: 31-DEC-1994
COAS: A Banner University Name: Mallikarjun, Amritha ECLS: FT Ful Fund Orgn Acct 1811 120 5220 1829B 120 5210 Employee Total for: Chart of Accounts Total Prog 610 610 K1 for A Actv Locn ID: K1 Home Orgn A 120 Treasury Department Amount 346.92 346.92 693.84 693.84 Report % 50.00 50.00 100.00 Total % 26.72 26.72 53.44
Position: KFTIME 00 Hours
Report Sample - One Benefit Selected (Page 2 of 2)
REPORT : NHREDST
Banner University Employee Distributions Report Reporting Period: 01-JUN-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered from Host Prompt.
Parameter Name _____________________________ Parameter Seq No: Sort Option: Period Begin Date: Period End Date: COAS: Employee ID: Select Earnings: Select Benefits: Benefit: Include Fringe Charge Back: Line Count: Record Count:
Value ________________ 18984 E 01-JUN-1994 31-DEC-1994 A K1 N Y FIO N 55 1
Message ____________________________________________________________ Sort By Employee Name
- Number of Employees processed
4-602
November 2010
Report Sample - All Benefits Selected (Page 1 of 2)
PAGE 1 REPORT : NHREDST COAS: A Banner University Name: Mallikarjun, Amritha ECLS: FT Ful Fund Orgn Acct 1811 120 5220 1829B 120 5210 Employee Total for: Chart of Accounts Total Prog 610 610 K1 for A Actv Locn
Banner University Employee Distributions Report Reporting Period: 01-JUN-1994 To: 31-DEC-1994 ID: K1 Home Orgn A 120 Treasury Department Amount 649.07 649.05 1,298.12 1,298.12 Report % 50.00 50.00 100.00
Position: KFTIME 00 Hours
Total % 50.00 50.00 100.00
Report Sample - All Benefits Selected (Page 2 of 2)
REPORT : NHREDST
Banner University Employee Distributions Report Reporting Period: 01-JUN-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered from Host Prompt.
Parameter Name _____________________________ Parameter Seq No: Sort Option: Period Begin Date: Period End Date: COAS: Employee ID: Select Earnings: Select Benefits: Include Fringe Charge Back: Line Count: Record Count:
Value ________________ 18985 E 01-JUN-1994 31-DEC-1994 A K1 N Y N 55 1
Message ____________________________________________________________ Sort By Employee Name
- Number of Employees processed
4-603
November 2010
Employee Payroll Summary by Organization (NHRSDST)

Description
To use this report, the Banner Human Resources System and the Banner Finance System must both be installed at your site. (If both the Banner Finance indicator and the Banner Human Resources indicator on the Installation Control Form (GUAINST) are set to Y, both systems are installed at your site.) This report prints up to eight columns of earnings and benefit data for each FOAPAL distribution covered by the report. You describe the contents of these columns via report parameters. Each column can contain the employee's current hour totals or amount totals for one or more earnings, the amount totals for one or more benefits, or the amount totals for fringe charge back. For example, you can choose four earnings groups displaying hours and amounts, eight benefit groups, or a mix of earnings and benefit groups as illustrated in the following example:
Column
Description
Hrs/Amt
Codes
Column 1 Column 2 Column 3 Column 4 Column 5 Column 6 Column 7 Column 8
Regular Earnings Regular Earnings Other Earnings Fringe FICA - Old Age FICA - Medicare Other Taxes Medical, Dental
Hours Amts Amts Amts Amts Amts Amts Amts
Earn Codes: REG Earn Codes: REG Earn Codes: VAC, SIC, HOL, OT Fringe Charge Back: *FC (As shown here, *FC, a pseudo benefit code, is used to identify fringe charge back.) Benefits: FIO Benefits: FIM Benefits: PA, MI, LOC Benefits: HMO, HEA, DEN
In the report described in this example, column 1 contains total hours for earn code REG, column 2 contains total amounts for earn code REG, column 3 contains figures that each represent the sum of the total amounts for earn codes VAC, SIC, HOL, and OT, column 4 contains the total amounts for fringe charge back, column 5 contains the total amounts for benefit code FIO, etc.
Note Another salary distribution report, the Organization Payroll Distribution Report (NHRDIST), lists the following data for each distribution covered by the report: data for each employee's position, including the employee's current amounts and/or hours for each specified earnings and the amounts for each specified benefit. The data for each earnings and benefit appears on a separate row. This information is followed by the FOAPAL summary totals. A summary version of this report, which prints only FOAPAL totals is also available. (See the NHRDIST report description earlier in this chapter for further information.)
4-604
November 2010
Parameters
Name
Description/Values
Required?
Default
Validation
Sort Option
Sort option: H D Sort by Home Organization. Sort by FOAPAL distribution organization.
Yes
None
Report Begin Date Report End Date Pay ID
First date for which report data is to be printed Yes Last date for which report data is to be printed Yes Pay ID identifying the payroll for which data No is to be printed. This is a repeating parameter. Wild cards are allowed; for example, A% identifies all pay IDs starting with A. When this field is left blank, all pay IDs are chosen. Hierarchy for report: E As exists. This value specifies that all FOAPALs are to be reported as they exist on the database. Data are not to be rolled up to higher fields or higher levels. Roll up to specified FOAP fields. (You will specify the fields in applicable parameters, as described below.) Roll up to a specified level for each FOAP. (You will specify the levels in applicable parameters, as described below.) Yes
None None All
None None PTRPICT
Hierarchy Option
E (as exists)
None
If you have set this parameter to E or F, skip to the Chart of Accounts parameter. If you have set the parameter to L, go to the Fund Level parameter.
4-605
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
When Hierarchy Option equals L and Fund Level equals E (see below), then all funds are reported at the existing level. This gives you the option to just roll to organization level 1 (via the Orgn Level parameter) and report the remaining FOAP data as it exists. Fund Level Fund level for the report. Enter E (as exists) to No indicate that funds are not to be rolled up to a higher level, or enter a number from 1 through 5 to identify a level to which data is to be rolled. Organization level for the report. Enter E (as No exists) to indicate that organizations are not to be rolled up to a higher level, or enter a number from 1 through 8 to identify a level to which data is to be rolled. Account level for the report. Enter E (as exists), to indicate that accounts are not to be rolled up to a higher level, or enter a number from 1 through 4 to identify a level to which data is to be rolled. Program level for the report. Enter E (as exists) to indicate that programs are not to be rolled up to a higher level, or enter a number from 1 through 5 to identify a level to which data is to be rolled. Chart of accounts to be covered in the report, that is, a FOAPAL distribution chart. This is a repeating parameter. No 1 None
Orgn Level
None
Acct Level
None
Prog Level
No
None
Chart of Accounts
None
FTVCOAS
4-606
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
If you set Sort Option to D (SORT by FOAPAL Distribution Organization), take one of these steps: If Hierarchy Option equals L (Level roll up), skip to the Employee Class parameter. If Hierarchy Option equals E (as exists) or F (FOAP field roll up), skip to the Fund Option parameter. If you set Sort Option to H (Sort by Home Organization), take one of the following steps: If your home organization chart of accounts differs from your distribution chart of accounts, go to the Home Orgn Chart parameter below. Otherwise, skip to the Home Organization Option parameter. Home Orgn Chart Your home organization chart. Enter this No parameter only if your home organization chart differs from your distribution chart. This is a nonrepeating parameter. When you enter this parameter the four home organization parameters below relate to the home organization chart you specify here. Home Organization Option Chart of accounts whose home organization No data is to be printed and the home organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all home organizations within chart H. This is a repeating parameter. A All. Requests that data be printed for all home organizations. If you enter this value and Hierarchy Option equals L, skip to the Employee Class parameter. If you enter this value and Hierarchy Option equals E or F, skip to the Fund Option parameter. All FTVORGN None FTVCOAS
4-607
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Range. Requests that data be printed for a specific range of home organizations. If you enter this value, go to the From Home Orgn parameter. Wild Card. Requests that data be printed for one or more specific home organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Home Orgn parameter.
Note: Whenever possible, use exact codes rather than wild cards to speed report processing.
Specific. Requests that data be printed for one or more specific home organizations, and indicates that you will enter exact codes to identify these organizations. If you enter this value, skip to the Home Orgn parameter. No None None
From Home Orgn
Chart of accounts whose home organization data is to be printed and the first home organization in the range of home organizations for which data is to be printed. The codes are separated by a comma, for example, H,110. This is a repeating parameter.
4-608
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
To Home Orgn
Chart of accounts whose home organization data is to be printed and the last home organization in the range. The codes are separated by a comma, for example, H,120. This is a repeating parameter. After entering this parameter, take one of the following steps: If you have set the Hierarchy Option to L, skip to the Employee Class parameter. Otherwise, skip to the Fund Option parameter. Codes identifying the chart of accounts whose home organization data is to be printed and a specific home organization for which data is to be printed. The codes are separated by a comma. This is a repeating parameter. You can enter several charts and can enter several home organizations for each chart; for example, you can enter: A,200 G,200 G,300
No
None
None
Home Orgn
If you set the Home Organization Option to W, you can use wild cards to identify home organizations. If Home Organization Option equals S, you must specify exact codes.
No
None
FTVORGN
4-609
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Fund Option
If Hierarchy Option equals F, skip this parameter and go directly to the Fund parameter. If Hierarchy equals E, enter one of the values below. Codes identifying the chart of accounts whose fund data is to be printed and the fund(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all funds within chart H. This is a repeating parameter. A All. Requests that data be printed for all funds. If you enter this value, skip to the Orgn Option parameter. Range. Requests that data be printed for a specific range of funds. If you enter this value, go to the From Fund parameter. Wild Card. Requests that data be printed for one or more specific funds, and indicates that you will use wild cards when you identify these funds. If you enter this value, skip to the Fund parameter.
No
All
None
Specific. Requests that data be printed for one or more specific funds, and indicates that you will enter exact codes to identify these funds. If you enter this value, skip to the Fund parameter.
4-610
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
From Fund
Chart of accounts whose fund data is to be printed and the first fund in the range of funds for which data is to be printed. The codes are separated by a comma, for example, H,1000. This is a repeating parameter. Chart of accounts whose fund data is to be printed and the last fund in the range, for example, H,2000. This is a repeating parameter.
No
None
None
To Fund
No
None
None
Fund
Chart of accounts whose fund data is to be No printed and a specific fund for which data is to be printed. The codes are separated by a comma. This is a repeating parameter. If Hierarchy Option equals E, then you can enter several fund codes for each chart, for example, you can enter: A,1000 A,1001 G,2000 H,1000 If you set the Fund Option to W, you can use wild cards to identify funds. If Fund Option equals S, you must specify exact codes.
None
FTVFUND
4-611
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
If Hierarchy Option equals F, then you can enter only one fund code for each chart and you cannot use wild cards; for example: A,1000 G,2000 H,1000 Orgn Option If Hierarchy Option equals F, skip this No parameter and go directly to the Orgn parameter. If Hierarchy Option equals E, enter one of the values below. Chart of accounts whose organization data is to be printed and the organization(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all organizations within chart H. This is a repeating parameter. R Range. Requests that data be printed for a specific range of organizations. If you enter this value, go to the From Orgn parameter. All. Requests that data be printed for all organizations. If you enter this value, skip to the Acct Option parameter. Wild Card. Requests that data be printed for one or more specific organizations, and indicates that you will use wild cards when you identify these organizations. If you enter this value, skip to the Orgn parameter. All None
4-612
November 2010
Parameters (cont)
Name
Description/Values Note: Whenever possible, use exact codes rather than wild cards to speed report processing.
Required?
Default
Validation
From Orgn
Chart of accounts whose organization data is to be printed and the first organization in the range of organizations for which data is to be printed. The codes are separated by a comma, for example, H,110. This is a repeating parameter. Chart of accounts whose organization data is to be printed and the last organization in the range. The codes are separated by a comma, for example, H,120. This is a repeating parameter.
To Orgn
No
None
None
4-613
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Orgn
Chart of accounts whose organization data is to be printed and a specific organization for which data is to be printed. The codes are separated by a comma, for example, H,120. This is a repeating parameter. If Hierarchy Option equals E, then you can enter several organization codes for each chart. If you have set the Orgn Option to W, you can use wild cards. If Orgn Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one organization code for each chart and cannot use wild cards. (See Fund Examples above.)
No
None
FTVORGN
Acct Option
If Hierarchy Option equals F, skip this No parameter and go directly to the Acct parameter. If Hierarchy Option equals E, enter one of the values below. Codes identifying the chart of accounts whose account data is to be printed and the account(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all accounts within chart H. This is a repeating parameter. A All. Requests that data be printed for all accounts. If you enter this value, skip to the Prog Option parameter. Range. Requests that data be printed for a specific range of accounts. If you enter this value, go to the From Acct parameter.
All
None
4-614
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Wild Card. Requests that data be printed for one or more specific accounts, and indicates that you will use wild cards when you identify these accounts. If you enter this value, skip to the Acct parameter.
Specific. Requests that data be printed for one or more specific accounts, and indicates that you will enter exact codes to identify these accounts. If you enter this value, skip to the Acct parameter. No None None
From Acct
Chart of accounts whose account data is to be printed and the first account in the range of accounts for which data is to be printed. The codes are separated by a comma, for example, H,5210. This is a repeating parameter. Chart of accounts whose account data is to be printed and the last account in the range. The codes are separated by a comma, for example, H,5220. This is a repeating parameter. Chart of accounts whose account data is to be printed and a specific account within that chart for which data is to be printed. The codes are separated by a comma. for example, H,5210. This is a repeating parameter.
To Acct
No
None
None
Acct
No
None
FTVACCT
4-615
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
If you have set Hierarchy Option to E, then you can enter several account codes for each chart. If you set the Acct Option to W, you can use wild cards. If Acct Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one account code for each chart and cannot use wild cards. (See Fund parameter examples.) Prog Option If Hierarchy Option equals F, skip this No parameter and go directly to the Prog parameter. If Hierarchy Option equals E, enter one of the values below. Chart of accounts whose program data is to be printed and the program(s) for which information is to be presented. The codes are separated by a comma; for example, H,A specifies that data is to be printed for all programs within chart H. This is a repeating parameter. A All. Requests that data be printed for all programs. If you enter this value, skip to the Employee Class parameter. Range. Requests that data be printed for a specific range of programs. If you enter this value, go to the From Prog parameter. All None
4-616
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Wild Card. Requests that data be printed for one or more specific programs, and indicates that you will use wild cards when you identify these programs. If you enter this value, skip to the Prog parameter.
Specific. Requests that data be printed for one or more specific programs, and indicates that you will enter exact codes to identify these programs. If you enter this value, skip to the Prog parameter. No None None
From Prog
Chart of accounts whose program data is to be printed and the first program in the range of programs for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. Chart of accounts whose program data is to be printed and the last program in the range. The codes are separated by a comma, for example, H,610. This is a repeating parameter.
To Prog
No
None
None
4-617
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Prog
Chart of accounts whose program data is to be printed and a specific program for which data is to be printed. The codes are separated by a comma, for example, H,100. This is a repeating parameter. If Hierarchy Option equals E, then you can enter several program codes for each chart. If you set the Prog Option to W, you can use wild cards. If Prog Option equals S, you must specify exact codes. If Hierarchy Option equals F, then you can enter only one program code for each chart and cannot use wild cards. (See Fund parameter examples.)
No
None
FTVPROG
Employee Class
Employee class for which data is to be printed. This is a repeating parameter. Wild cards can be used. ID code identifying employee for whom data is to be printed. This is a repeating parameter. Wild cards are allowed. Type of data to be reported in column 1: E B F N Earnings Benefits Fringe Charge Back Nothing. If you enter this value, skip to the Payroll Detail parameter.
No
All
PTRECLS
Employee ID
No
All
POAIDEN
Column 1 Option
Yes
None
None
4-618
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
Column 1 Description
Brief description of data to be reported in column 1 If Column 1 Option equals B, skip to Column 1 Earn/Benefit Code. If Column 1 Option equals F, skip to Column 2 Option. If Column 1 Option equals E, go to Column 1 Earnings - Hrs/Amt.
No
None
None
Column 1 Earnings -Hrs/Amt
Hours/Amount indicator for column 1: H A Report earnings hours in column 1. Report earnings amounts in column 1.
No
None
Column 1 Earn/Benefit Code
Earn/Benefit code identifying an earning or benefit for which data is to be printed. This is a repeating parameter. Wild cards are allowed. If this field is blank, data is printed for all earnings and/or benefits.
Yes
None
None
Parameters identical with those for column 1 (Option, Description, Earnings - Hrs/Amt, and Earn/Benefit Code) are included for columns 2 through 8. The instructions for using these parameters are identical for each column. Payroll Detail Payroll detail inclusion indicator: Y N Include detail information for each pay event covered by the report. Do not include detail information for pay events. Yes N None
4-619
November 2010
Parameters (cont)
Name
Description/Values
Required?
Default
Validation
When specifying the To Date Totals Option parameter, you should note that the to-date end date (that is, the last date whose data are to be used in calculating the QTD, YTD, and FTD totals) can either be the date the report is run or the report end date. You specify which of these values is to be used in the Use Report End Date As End Date To Date parameter below. To Date Amounts Option To-date totals indicator: N Do not include quarter-to-date (QTD), calendar year-to-date (YTD), or fiscal year-to-date (FTD) amounts Include QTD amounts for all data entered from the start of the quarter containing the Report Begin Date to the to-date end date. Include YTD amounts for all data entered from the start of the calendar year containing the Report Begin Date to the to-date end date. Include FTD amounts for all data entered from the start of the fiscal year containing the Report Begin Date to the to-date end date. Yes N None
If you set this parameter to N, skip to the Include Earnings parameter. Otherwise, go to the Use Report End Date as To Date End Date parameter. Report End Date as TD End Date Code indicating whether the system is to use No the report end date as the to-date end date when calculating QTD, YTD, and FTD totals: Y N Totals are to be calculated to the report end date Totals are to be calculated to the date the report is run N None
4-620
November 2010
Report Sample - Sorted by FOAPAL Distribution Organization (Page 1 of 3)
REPORT: NHRSDST
Banner University Empl Payroll Summary By Orgn Reporting Period: 01-JUL-1994 To: 31-DEC-1994
COAS: H Organization: 135 Facilities Department Fund F ID/Name Orgn 135 Acct 5120 Prog 610 Actv * REGULAR Amount .00 2,083.34 2,083.34 2,083.34 2,083.34 8,333.36 8,333.36 Locn * DEFER ACCR Amount .00 694.45 694.45 694.45 694.45 2,777.80 2,777.80 FIO Amount .00 .00 .00 .00 118.70 118.70 118.70 . . . 118.70 118.70 118.70 118.70 . . . 118.70 118.70 118.70 118.70 FIM Amount .00 .00 .00 .00 27.76 27.76 27.76 OTHER BEN Amount 150.00 .00 .00 .00 150.00 300.00 300.00 FRINGE Total Amount Hours .00 .00 .00 .00 .00 .00 86.66 86.66 86.66 86.66 Total Amount 150.00 2,777.79 2,777.79 2,777.79 3,074.25 11,557.62 11,557.62
REGULAR Hours 888020005 Libby, Label 1994 TM 8 0 .00 1994 TM 9 0 86.66 1994 TM 10 0 86.66 1994 TM 11 0 86.66 1994 TM 12 0 86.66 Empl Total YTD Total 346.64 346.64
.00 346.64 .00 346.64
Prog Total YTD Total Acct Total YTD Total
606.62 606.62 606.62 606.62
8,583.38 8,583.38 8,583.38 8,583.38
2,827.80 2,827.80 2,827.80 2,827.80
27.76 27.76 27.76 27.76
300.00 300.00 300.00 300.00
.00 606.62 .00 606.62 .00 606.62 .00 606.62
11,857.64 11,857.64 11,857.64 11,857.64
Fund Total YTD Total Orgn Total YTD Total
606.62 606.62 606.62 606.62
8,583.38 8,583.38 8,583.38 8,583.38
2,827.80 2,827.80 2,827.80 2,827.80
27.76 27.76 27.76 27.76
300.00 300.00 300.00 300.00
3,264.99 606.62 3,264.99 606.62 3,264.99 606.62 3,264.99 606.62
15,122.63 15,122.63 15,122.63 15,122.63
4-621
November 2010
REPORT : NHRSDST
Banner University Empl Payroll Summary By Orgn Reporting Period: 01-JUL-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Sort Option: Period Begin Date: Period End Date: Hierarchy: COAS Fund Option: Fund: Fund: Orgn Option: From Orgn: To Orgn: Acct Option: Acct: Acct:
Prog Option: Column 1 Values ------ - -----Option: Description: Earnings By Hours/Amount Earn Code: Earn Code: Earn Code: Column 2 Values ------ - -----Option: Description: Earnings By Hours/Amount Earn Code: Earn Code: Earn Code: Column 3 Values ------ - -----Option:
Value ________________ 25335 D 01-JUL-1994 31-DEC-1994 E H H S H 1000 H F H R H 110 H 220 H W H 5000 H 5100 . . . H A E REGULAR H REG SIC VAC E REGULAR A REG SIC VAC E
Message ____________________________________________________________ Sort By FOAPAL Distribution Organization FOAP Fields As Exists Specific Range Wildcards
All Earnings By Hours
Earnings By Amount
Earnings
4-622
November 2010
REPORT : NHRSDST
Banner University Empl Payroll Summary By Orgn Reporting Period: 01-JUL-1994 To: 31-DEC-1994 Value ________________ DEFER ACCR A DPA B FIO FIO B FIM FIM B OTHER BEN 401 DEN HBC HEA HME HMO F FRINGE N Yes YTD Total Y 55 Column 8 is not being used in this report.
Parameter Name _____________________________ Description: Earnings By Hours/Amount Earn Code: Column 4 Values ------ - -----Option: Description: Benefit: Column 5 Values ------ - -----Option: Description: Benefit: Column 6 Values ------ - -----Option: Description: Benefit: Benefit: Benefit: Benefit: Benefit: Benefit: Column 7 Values ------ - -----Option: Description: Column 8 Values ------ - -----Option: Print Pay Detail: To Date Totals Option: Use Report End Date As To Date End Date: Line Count:
Message ____________________________________________________________ By Amount
Benefits
Benefits
Benefits
Fringe Charge Back
Not Used
4-623
November 2010
Report Sample - Sorted by Home Organization (Page 1 of 3)
REPORT : NHRSDST
Banner University Empl Payroll Summary By Orgn Reporting Period: 01-JUL-1994 To: 31-DEC-1994
COAS: H Home Organization: 125 Treasury Department Fund F ID/Name Acct Total YTD Total Fund F ID/Name Orgn 155 Orgn 155 Acct 5120 Prog 610 Actv * ALL EARN Amount 24,000.00 32,000.00 Actv * ALL EARN Amount 3,000.00 4,000.00 3,000.00 4,000.00 3,000.00 4,000.00 . . . Orgn Total YTD Total Fund Total YTD Total Home Total YTD Total 936.00 1,248.00 1,039.98 1,386.64 1,039.98 1,386.64 27,000.00 36,000.00 30,000.00 40,000.00 30,000.00 40,000.00 484.93 1,696.09 538.81 1,884.54 538.81 1,884.54 6,750.00 6,750.00 7,500.00 7,500.00 7,500.00 7,500.00 936.00 1,248.00 1,039.98 1,386.64 1,039.98 1,386.64 34,234.93 44,446.09 38,038.81 49,384.54 38,038.81 49,384.54 Locn * ALL BEN Amount 431.05 1,507.63 Locn * ALL BEN Amount 53.88 188.46 53.88 188.46 53.88 188.46 FRINGE Amount .00 .00 .00 .00 .00 .00 Total Hours 103.98 138.64 103.98 138.64 103.98 138.64 Total Amount 3,053.88 4,188.46 3,053.88 4,188.46 3,053.88 4,188.46 FRINGE Amount .00 .00 Total Hours 832.02 1,109.36 Total Amount 24,431.05 33,507.63
ALL EARN Hours 832.02 1,109.36 Acct 5220 Prog 600
ALL EARN Hours 888020006 Sander, Mark Empl Total YTD Total Prog Total YTD Total Acct Total YTD Total 103.98 138.64 103.98 138.64 103.98 138.64
4-624
November 2010
REPORT : NHRSDST
Banner University Empl Payroll Summary By Orgn Reporting Period: 01-JUL-1994 To: 31-DEC-1994 * * * REPORT CONTROL INFORMATION * * * Parameters have been entered via Job Submission.
Parameter Name _____________________________ Parameter Seq No: Sort Option: Period Begin Date: Period End Date: Hierarchy: COAS Home Orgn Option: Fund Option: Orgn Option: Acct Option: Prog Option: Column 1 Values ------ - -----Option: Description: Earnings By Hours/Amount Earn Code: Column 2 Values ------ - -----Option: Description: Earnings By Hours/Amount Earn Code: Column 3 Values ------ - -----Option: Description: Benefit: Column 4 Values ------ - -----Option: Description: Column 5 Values ------ - -----Option: Column 6 Values ------ - -----Option: Column 7 Values
Value ________________ 25336 H 01-JUL-1994 31-DEC-1994 E H H A H A H A H A H A E ALL EARN H Allearns E ALL EARN A Allearns B ALL BEN Allbdcas F FRINGE N N
Message ____________________________________________________________ Sort By Home Organization FOAP Fields As Exists All All All All All Earnings By Hours
Earnings By Amount
Benefits
Fringe Charge Back
Not Used Not Used
4-625
November 2010
REPORT : NHRSDST
Banner University Empl Payroll Summary By Orgn Reporting Period: 01-JUL-1994 To: 31-DEC-1994 Value ________________ N N No YTD Total N 55 Column 5 thru Column 8 are not being used in this report.
Parameter Name _____________________________ Option: Column 8 Values ------ - -----Option: Print Pay Detail: To Date Totals Option: Use Report End Date As To Date End Date: Line Count:
Message ____________________________________________________________ Not Used Not Used
4-626
November 2010
Archive/Purge
This section describes each report in the Archive/Purge feature. A table provides related parameter information. A report with sample data follows each parameter table. The reports are listed alphabetically by their seven-character names.
4-627
November 2010
Archive/Purge Process (FOPARCP)

Description
The Archive process copies data from the production current tables into another table structure. Data which resides on the archive tables can be purged when it is outdated or no longer needed. The Purge process deletes data from the production current or production archive tables. A database indicator is included among the parameters to determine which database will be purged. The Archive/Purge Process consists of the following user enterable parameters which control whether data will be archived or purged and determine which data will be archived/purged.
Parameters
Name
Required?
Description
Values
Hours of Processing Parameter
No
Duration of time to process. If null, processing will continue until all relative data is processed. Otherwise, when actual execution time exceeds this parameter value, processing will come to a programmatic termination. If a document is currently being processed for archive/purge, then that cycle will complete prior to termination. Action to be performed. A (Archive) will copy data from the production tables to the archive tables. The data is then removed from the production tables. P (Purge) will remove data from the production or archive tables. This value is printed in the report header for every page (next to literal Action:). If P (Purge) is selected, there will be a confirmation (Y/ N) of this parameter. If confirmation of purge is Y, processing continues; otherwise, the program terminates. A P Archive Purge
Action Indicator
Yes
4-628
November 2010
Parameters (cont)
Name
Required?
Description
Values
Database Indicator
No
Type of tables to be processed: P (Production) tables or A (Archive) tables. This parameter is only valued when the Action Indicator = P (Purge). This process can be used to purge data from either the production tables or the archive tables. This value is printed in the report header for every page (next to literal Source:).
P A
Production tables Archive tables
Execution Mode
Yes
Determines whether the process is run in A (Audit) A mode or U (Update) mode. Audit mode produces a report detailing potential database activity; however, U no database changes occur. Update mode produces the report and updates the database. The database is determined by the value of the Action Indicator. This value is printed in the report header for every page (next to literal Mode:). Indicates whether or not to perform the edits for bank reconciliation data (some Banner Finance sites reconcile check transaction processing and some do not). An entry of Y will perform these edits as part of the archive or purge execution. Indicates whether or not to perform the edits for grant related data. An entry of Y will perform these edits as part of the archive or purge execution. Parameter that is used if both of the following conditions exist: The grant edit is being performed. A purge is taking place. Government regulations may require that grant data should not be deleted until five years after its termination date. Y N
Audit mode Update mode
Perform Bank Reconciliation Edit
No
Yes (default) No
Perform Grant Edit
No
Y N
Yes (default) No
Grant Purge Years Tolerance
No
Default = 5
4-629
November 2010
Parameters (cont)
Name
Required?
Description
Values
Print Mode
No
When the Execution Mode is set to A (Audit), you may choose the Print Mode. A Print Mode set to E (Exceptions) may produce a smaller, more manageable report. An Execution Mode of U (Update) requires a Print Mode of D (Detail). The detail version of the report will include the exceptions data provided with an exception print mode execution. Multiple Chart of Accounts codes are allowed. The data in this field is compared to the chart of accounts field in the FGBTRNH table (if archiving or purging from the production database) or FGBTRNH_ARCHIVE table (if purging from the archive database). If the codes match, the associated records from the driver and related tables will be archived or purged. All charts are validated against the Chart of Accounts Validation Table (FTVCOAS). This verifies that the chart(s) exist. There is no effective or termination date checking.
D E
Detail Exceptions
Yes
4-630
November 2010
Parameters (cont)
Name
Required?
Description
Values
Fiscal Year
Yes
Multiple fiscal years are allowed. The data in this field is compared to the fiscal year in the related table. If the fiscal years match, the associated records from the driver and related tables are archived or purged. The fiscal year is used in conjunction with the Chart of Accounts to determine if the fiscal year is closed. If the fiscal year is not closed, the combination of fiscal year and Chart of Accounts is invalid and the data cannot be archived or purged. The fiscal year cannot be a current year or prior year with regard to concurrent year processing functionality. An archive/purge process can be reissued for the same chart of accounts and fiscal year relative to a document that has been partially archived or to check reconciliation.
YY
4-631
November 2010
FOPARCP 2.1.11
SEED Data Archive/Purge Transaction History Activity Listing Source: PRODUCTION Action: ARCHIVE Mode: UPDATE
03/18/1996 15:54:30 PAGE 1
EXCEPT COA FSYR DOCUMENT DOC SEQ ITEM SEQ NUM SUBMISSION SER NUM DOC REFERENCE TRANS DATE TRANS DESC BANK ------ --- ---- -------- ------- ---- ------- ---------- ------- ------------- ----------- ----------------------------------- ---A 93 I0000003 3 0 1 0 1 10-AUG-1992 Fitzpatrick Davies Brown CPA A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 I0000004 3 0 1 0 1 10-AUG-1992 Fitzpatrick Davies Brown CPA A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 I0000085 3 0 1 0 1 17-JUL-1992 National Supplies, Inc. DM
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 TEL00001 20 0 1 3 0 10-OCT-1992 To Post Monthly Telephone Charges A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 TEL00001 20 0 1 4 0 10-NOV-1992 To Post Monthly Telephone Charges A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- ---
4-632
November 2010
FOPARCP 2.1.11
03/18/1996 15:54:30 PAGE 2
EXCEPT COA FSYR DOCUMENT DOC SEQ ITEM SEQ NUM SUBMISSION SER NUM DOC REFERENCE TRANS DATE TRANS DESC BANK ------ --- ---- -------- ------- ---- ------- ---------- ------- ------------- ----------- ----------------------------------- ---A 93 TEL00001 20 0 3 4 0 10-NOV-1992 To Post Monthly Telephone Charges A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 TEL00001 20 0 1 5 0 10-DEC-1992 To Post Monthly Telephone Charges A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 RULE ---JE15 JE15 A 93 RULE ---JE15 JE15 A 93 TEL00001 RULP ---20 20 PROC ---O030 O030 20 LDG --G O 20 LDG --G O 20 0 1 6 0 ORGN -----120 120 10-JAN-1993 To Post Monthly Telephone Charges ACCT -----3020 6400 A1
FLD POST PRD --- -------01 07 03 07 0 2
ACTIVITY COA FSYR FUND ----------- --- ---- -----20-JUL-1995 A 93 1000 20-JUL-1995 A 93 1000 6 0
PROG ACTV LOCN TRANS AMOUNT DR/CR REV ------ ------ ------ ---------------- ----- --100 250.00 D N 100 250.00 + N A1
TEL00001 RULP ---20 20 PROC ---O030 O030
10-JAN-1993 To Post Monthly Telephone Charges ORGN -----165 165 ACCT -----3020 6400
FLD POST PRD --- -------01 07 03 07 0 3
TEL00001
10-JAN-1993 To Post Monthly Telephone Charges
4-633
November 2010
FOPARCP 2.1.11
SEED Data Archive/Purge Transaction History Activity Listing Source: PRODUCTION Action: ARCHIVE Mode: UPDATE RULP ---20 20 PROC ---O030 O030 LDG --G O 41 FLD POST PRD --- -------02 07 03 07 1 1 ACTIVITY COA FSYR FUND ----------- --- ---- -----20-JUL-1995 A 93 1000 20-JUL-1995 A 93 1000 0 0 ORGN -----210 210 ACCT -----3020 6400
03/18/1996 15:54:30 PAGE 3
RULE ---JE15 JE15 A 93
PROG ACTV LOCN TRANS AMOUNT DR/CR REV ------ ------ ------ ---------------- ----- --100 500.00 C N 100 -500.00 N IM
Q0000011
22-JAN-1993 Variable Option
EXCEPT COA FSYR DOCUMENT DOC SEQ ITEM SEQ NUM SUBMISSION SER NUM DOC REFERENCE TRANS DATE TRANS DESC BANK ------ --- ---- -------- ------- ---- ------- ---------- ------- ------------- ----------- ----------------------------------- ---A 93 Q0000012 41 1 1 0 0 22-JAN-1993 Variable Option IM
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- ---
FOPARCP 2.1.11
03/18/1996 15:54:30 PAGE 4
Production Transaction History Table -----------------------------------Starting Row Count = 5,667 Activity Row Count = -17 Ending Row Count = 5,650 Production Transaction Detail Table -----------------------------------Starting Row Count = 20,946 Activity Row Count = -6 Ending Row Count = 20,940
Archive Transaction History Table -----------------------------------Starting Row Count = 0 Activity Row Count = 17 Ending Row Count = 17 Archive Transaction Detail Table -----------------------------------Starting Row Count = 0 Activity Row Count = 6 Ending Row Count = 6
4-634
November 2010
FOPARCP 2.1.11
03/18/1996 15:54:30 PAGE 5
* * * REPORT CONTROL INFORMATION * * * PARAMETER SEQUENCE NUMBER: 2456 PARAMETER PROCESSING HOURS: 1.00 ACTION INDICATOR: A DATABASE INDICATOR: P EXECUTION MODE: U PRINT MODE: D CHART OF ACCOUNTS/FISCAL YEAR: A93 AS OF DATE: 03/18/1996 PERFORM BANK RECONCILIATION EDIT: N NUMBER OF PRINTED LINES PER PAGE: 55 RECORD COUNT: 23
4-635
November 2010
Restore Process (FOPARCR)

Description
The Restore Process reestablishes previously archived data into the production current tables. The restored data will be removed from the production archive tables as part of the Restore Process. Purged data cannot be restored. The Restore Process consists of the following user enterable parameters which control which data will be restored:
Parameters
Name
Required?
Description
Values
Hours of Processing Parameter
No
Duration of time to process. If null, processing will continue until all relative data is processed. Otherwise, when actual execution time exceeds this parameter value, processing will come to a programmatic termination. If a document is currently being processed for restore, then that cycle will complete prior to termination. Determines whether the process will be run in A A (Audit) mode or U (Update) mode. Audit mode will U produce a report detailing potential database activity; however, no database changes will occur. Update mode will produce the report and update the database. The database is determined by the value of the Action Indicator. This value is printed in the report header for every page (next to literal Mode:). When the Execution Mode is set to A (Audit), you may choose the Print Mode. A Print Mode set to E (Exceptions) may produce a smaller, more manageable report. An Execution Mode of U (Update) requires a Print Mode of D (Detail). The detail version of the report will include the exceptions data provided with an exception print mode execution. D E Audit mode Update mode
Execution Mode
Yes
Print Mode
No
Detail Exceptions
4-636
November 2010
Parameters (cont)
Name
Required?
Description
Values
Yes
Multiple Chart of Accounts codes are allowed. The data in this field is compared to the chart of accounts field in the related table. If the codes match, the associated records from the driver and related tables will be restored. All charts are validated against the Chart of Accounts Validation Table (FTVCOAS). This verifies that the chart(s) exist; there is no effective or termination date checking. Multiple fiscal years are allowed. The data in this parameter is compared to the fiscal year in the related table. If the fiscal years match, the associated records from the driver and related tables are restored. The process checks to make sure that a row exists on FTVFSYR for each chart and fiscal year combination. YY
Fiscal Year
Yes
4-637
November 2010
FOPARCR 2.1.11
SEED Data Restore Transaction History Activity Listing Mode: UPDATE
03/18/1996 17:01:43 PAGE 1
EXCEPT COA FSYR DOCUMENT DOC SEQ ITEM SEQ NUM SUBMISSION SER NUM DOC REFERENCE TRANS DATE TRANS DESC BANK ------ --- ---- -------- ------- ---- ------- ---------- ------- ------------- ----------- ----------------------------------- ---A 93 I0000003 3 0 1 0 1 10-AUG-1992 Fitzpatrick Davies Brown CPA A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 I0000004 3 0 1 0 1 10-AUG-1992 Fitzpatrick Davies Brown CPA A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 I0000085 3 0 1 0 1 17-JUL-1992 National Supplies, Inc. DM
4-638
November 2010
FOPARCR 2.1.11
03/18/1996 17:01:43 PAGE 2
EXCEPT COA FSYR DOCUMENT DOC SEQ ITEM SEQ NUM SUBMISSION SER NUM DOC REFERENCE TRANS DATE TRANS DESC BANK ------ --- ---- -------- ------- ---- ------- ---------- ------- ------------- ----------- ----------------------------------- ---A 93 TEL00001 20 0 3 4 0 10-NOV-1992 To Post Monthly Telephone Charges A1
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --A 93 RULE ---JE15 JE15 A 93 RULE ---JE15 JE15 A 93 TEL00001 RULP ---20 20 PROC ---O030 O030 20 LDG --G O 20 LDG --G O 20 0 1 6 0 ORGN -----120 120 10-JAN-1993 To Post Monthly Telephone Charges ACCT -----3020 6400 A1
FLD POST PRD --- -------01 07 03 07 0 2
TEL00001 RULP ---20 20 PROC ---O030 O030
10-JAN-1993 To Post Monthly Telephone Charges ORGN -----165 165 ACCT -----3020 6400
FLD POST PRD --- -------01 07 03 07 0 3
TEL00001
4-639
November 2010
FOPARCR 2.1.11
SEED Data Restore Transaction History Activity Listing Mode: UPDATE RULP ---20 20 PROC ---O030 O030 LDG --G O 41 FLD POST PRD --- -------02 07 03 07 1 1 ACTIVITY COA FSYR FUND ----------- --- ---- -----20-JUL-1995 A 93 1000 20-JUL-1995 A 93 1000 0 0 ORGN -----210 210 ACCT -----3020 6400
03/18/1996 17:01:43 PAGE 3
RULE ---JE15 JE15 A 93
PROG ACTV LOCN TRANS AMOUNT DR/CR REV ------ ------ ------ ---------------- ----- --100 500.00 C N 100 -500.00 N IM
Q0000011
22-JAN-1993 Variable Option
EXCEPT COA FSYR DOCUMENT DOC SEQ ITEM SEQ NUM SUBMISSION SER NUM DOC REFERENCE TRANS DATE TRANS DESC BANK ------ --- ---- -------- ------- ---- ------- ---------- ------- ------------- ----------- ----------------------------------- ---A 93 Q0000012 41 1 1 0 0 22-JAN-1993 Variable Option IM
RULE RULP PROC LDG FLD POST PRD ACTIVITY COA FSYR FUND ORGN ACCT PROG ACTV LOCN TRANS AMOUNT DR/CR REV ---- ---- ---- --- --- -------- ----------- --- ---- ------ ------ ------ ------ ------ ------ ---------------- ----- --JE15 20 JE15 20 A 93 O030 G O030 O 20 01 03 0 07 20-JUL-1995 07 20-JUL-1995 3 6 A A 93 93 0 1000 1000 165 165 3020 6400 100 100 250.00 250.00 D + A1 N N
TEL00001
FOPARCR 2.1.11
03/18/1996 17:01:43 PAGE 4
Production Transaction History Table -----------------------------------Starting Row Count = 5,650 Activity Row Count = 17 Ending Row Count = 5,667 Production Transaction Detail Table -----------------------------------Starting Row Count = 20,940 Activity Row Count = 6 Ending Row Count = 20,946
Archive Transaction History Table -----------------------------------Starting Row Count = 17 Activity Row Count = -17 Ending Row Count = 0 Archive Transaction Detail Table -----------------------------------Starting Row Count = 6 Activity Row Count = -6 Ending Row Count = 0
4-640
November 2010
FOPARCR 2.1.11
03/18/1996 17:01:43 PAGE 5
* * * REPORT CONTROL INFORMATION * * * PARAMETER SEQUENCE NUMBER: 2459 EXECUTION MODE: U CHART OF ACCOUNTS/FISCAL YEAR: A93 AS OF DATE: 03/18/1996 NUMBER OF PRINTED LINES PER PAGE: 55 RECORD COUNT: 23
4-641
November 2010
4-642
November 2010
GASB Report Examples

Reporting for the GASB enhancements does not generate printed output directly; instead, it creates a comma separated value file (csv). You can open this file with a standard spreadsheet tool, such as Microsoft Excel. Within Excel, you can customize each report for transactions, or comments, unique to your institution. You can also enhance the formatting to produce financial statements that are camera ready. This section contains examples of the following GASB reports, an attribute listing for the Statement of Net Assets, plus report samples of each of the three GASB Extract Process Attribute Errors reports. This section includes the following sub-sections. GASB 35 reports: Statement of Net Assets in three different forms (an excerpt from an Excel workbook, an expanded version of the workbook page, and a camera-ready copy of the finished report) Camera-ready sample of the Statement of Revenue, Expenses, and Changes in Net Assets Sample attribute listing for the Statement of Net Assets that would be generated if you ran the extract attributes option GASB 34 reports: Government Wide Statement of Net Assets Government Wide Statement of Activities Governmental Funds Balance Sheet Governmental Funds Statement of Revenues, Expenditures, and Changes in Fund Balances GASB Extract Process Attribute Errors reports generated by FGPGEXT Your GASB reports may look different from the examples provided here, because you can customize each report for your institution.
November 2010
4-643
Statement of Net Assets - Workbook

This example is an excerpt from an Excel workbook as it appears when the .csv file for the GASB 35 Statement of Net Assets is first opened. Parameter information is included at the top (only some of the data are captured here). Text and numbers are not correct, since the default column width was used.
4-644
November 2010
Statement of Net Assets - Expanded Workbook

This example provides an expanded version of the same workbook page. The difference is that the columns are expanded to display the full values they contain.
November 2010
4-645
Statement of Net Assets - Camera-ready Report

This example shows how the Statement of Net Assets might be prepared for printing, by setting column widths and alignments, formatting amounts, and inserting comments.
4-646
November 2010
Statement of Revenue, Expenses, and Changes in Net Assets
November 2010
4-647
4-648
November 2010
Attributes for Statement of Net Assets

The following sample shows a listing of fund, account, program, fund type, and account type codes that have been associated to the report attribute types and values for the Statement of Net Assets. This listing was generated by entering the following parameters: Chart code:N Fiscal Year: Fiscal Period: Report Name: Statement of Net Assets Extracted Data mode: ATTRIBUTES
CHART CODE N N N N N N N N N N N N N N
ATTRIBUTE TYPE CODE G5BAA1CA G5BAA1CA G5BAA1CA G5BAA2NA G5BAA3CL G5BAA3CL G5BAFUND G5BAFUND G5BAFUND G5BAFUND G5BAFUND G5BAFUND G5BAN1NA G5BAN1NA
ATTRIBUTE TYPE TITLE Current assets Current assets Current assets Noncurrent assets Current liabilities Current liabilities Public Inst BTA Column Public Inst BTA Column Public Inst BTA Column Public Inst BTA Column Public Inst BTA Column Public Inst BTA Column Net Assets Net Assets
ATTRIBUTE VALUE CODE 1010CURA 1030CURA 1030CURA 2060NCRA 3020CLIB 3020CLIB 1010PI 1010PI 1010PI 1010PI 1020CU 9999EXCL 1090NA 1090NA
ATTRIBUTE VALUE DESC Cash and cash equivalents Accounts receivable net Accounts receivable net Capital assets net Deferred revenue Deferred revenue Primary Institution Primary Institution Primary Institution Primary Institution Component Unit Exclude Unrestricted Unrestricted
FOAPAL ELEMENT TYPE ATYP ACCT ATYP ATYP ATYP ATYP FUND FTYP FTYP FTYP FTYP FTYP ATYP ATYP
FOAPAL CODE 11 1116 13 17 23 24 1000 21 31 41 32 9 31 41
FOAPAL TITLE Cash and Cash Equivalents Food Services Receivable Accounts Receivable Fixed Assets Deferred Credits Deposits Current Unrestricted Fund Restricted Auxiliary Enterprise Student Loan Agency Bank Fund Control Accounts Fund Balance
4-649
November 2010
Government Wide Statement of Net Assets
4-650
November 2010
Government Wide Statement of Activities
4-651
November 2010
Governmental Funds Balance Sheet
4-652
November 2010
Governmental Funds Statement of Revenues Expenditures and Changes in Fund Balances
4-653
November 2010
GASB Extract Process Attribute Errors reports

The Data Extract Process is run via job submissions. This process uses the parameters entered to extract the appropriate information from the General Ledger (FGBGENL) and Operating Ledger (FGBOPAL) tables to the FGWREPT table. For additional information about the FGPGEXT process, refer to the Data Extract Process information in the General Ledger Module section. If any FOAPAL elements do not have attributes selected, or have duplicate associations, the FGPGEXT process generates error reports. Another report identifies FOAPAL elements intentionally excluded from the GASB statements. Samples of each report, plus a copy of the control page that prints after the report, are included here.
FOAPAL Elements with Duplicate Associations
04/04/2001 13:21:32 Chart [from parm] FOAPAL Type -----------Account Code ATYP Code Fund Code FTYP Code Program Code
Development GASB Extract Process Attribute Errors FOAPAL Elements with duplicate associations Attribute Type Begins ------------G5BAO G5BAO G5BAA Count -----2 2 3
PAGE 1 FGPGEXT
Value -------5150 5170 71 [etc]
FOAPAL Elements with No Valid Association
04/04/2001 13:21:32 Chart [from parm] FOAPAL Type -------------Account Fund Program Low Level Value --------7160 25010 251000 715
Development GASB Extract Process Attribute Errors FOAPAL Elements with No Valid Association Hierarchy Value --------7100 250100 70 Level 2 Type ------71 8A 8A Report -------------------------------------------G5BA GASB 35 Basic Accounting G4GF GASB 34 Governmental Funds Financials G4GF GASB 34 Governmental Funds Financials G4GW GASB 34 Government Wide Financials
PAGE 2 FGPGEXT
4-654
November 2010
Data Excluded from Extract based on Attribute Assignments
04/04/2001 13:21:32 Chart [from parm] Type --------Account Fund Code -------54880 805111
Development GASB Extract Process Attribute Errors Data Excluded from Extract based on Attribute Assignmnets Title ---------------------------------Capital Outlay Student Government Agency Account
PAGE 3 FGPGEXT
Report Control Information
06-AUG-2001 11:09 AM Chart B
Development GASB Extract Process * * * REPORT CONTROL INFORMATION * * * Parameters have been entered from Host Prompt.
PAGE 4 FGPGEXT 4.4
Parameter Name ___________________________________ Parameter Seq No: Chart of Accounts: As of Date: Fiscal Year (calculated): Period (calculated): Period End Date (calculated): Account Hierarchy at: Include Accrual: Government Wide Financials: Government Funds Financials: Public Institution BTA Financials: Processing Mode:
Value ________________ 899735 B 30-JUN-2001 2001 12 30-JUN-2001 LEVEL1 Y Y N N E
Number of Rows Deleted: Number of Rows Inserted:
421 421
Activity to fund balance accounts in the current year may cause an out of balance condition between the Operating reports and the Balance Sheet reports unless an equivalent amount of revenue/expense has been excluded from the Operating report. Net Fund Balance activity (all funds): 197,482.00 If the Close General Ledger process (FGRCLOP) has been run, the close-out activity is included in the net activity above.
4-655
November 2010
4-656
November 2010
Glossary
Account balance The difference in dollars between the total debits and the total credits in an account. Accounting equation Assets equal liabilities plus owners' equity.
A = L + OE
Accounting system A financial information system that includes financial forms, records, reports, employee work assignments, and internal controls procedures designed to fit the particular needs of a business or government agency. Accounts payable Accounts which a company or government agency owes its creditors for goods and services purchased on credit. Accounts Receivable module The Accounts Receivable module enables you to manage your payables process by tracking cash flow and maximizing your investment earnings. American Institute of Certified Public Accountants (AICPA) The national professional association of certified public accounts. The AICPA conducts extensive research and is instrumental in improving accounting standards and practices. Archive/Purge Use the Archive/Purge feature to write information to another medium or to delete information from your system. Assets The economic resources owned by a business that are expected to benefit future operations. Balance sheet A financial statement that lists the assets, liabilities, and capital structure of a company on a specific date.
November 2010
Banner Finance 8.5 User Guide Glossary
G-1
Bids and contracts processing Bid processing occurs within the Purchasing and Procurement module. This feature enables you to create and award vendor bids and/or contracts. Bonds When corporations, banks, or the government want to raise money, they may borrow it from lenders by issuing debt obligations. These debt obligations have maturity dates which are short (money market instruments less than one year), intermediate (notes one to ten years), or long (bonds over ten years). When you buy a debt obligation such as a bond, you lend money to a bank, the government, or a corporation for a particular period of time. They pay you, the debt holder, interest on the debt to compensate you for the use of your money. The bank, the government, or corporation agrees to pay you, the debt holder, a fixed rate of interest each year and to repay the full sum principal on the bond's maturity date. Bonds do not represent ownership. Bond rating Bonds are rated on the borrower's (that is, the corporation or government) ability to make interest payments and to repay the principal. Budget Development module This component of Banner Finance enables you to create complex or simple budgets. In addition, you can simultaneously update a working budget for analytical purposes while adjusting the approved budget. Capital appreciation When the market value of an investment portfolio increases. Capital gains Capital gains are earned when an investment portfolio manager sells a stock or bond within the portfolio for a profit and then distributes the money to investors or reinvests the money in proportion to the number of owned shares. Chart of accounts A systematic classification of accounts is an essential component of the Banner Finance accounting system. You should develop your accounts to be compatible with your organizational structure. You should arrange your chart of accounts form and content in agreement with the financial reports that you issue.
G-2
November 2010
Clause The Clause Entry Form (FOACLAU) enables you to associate a description with a clause number for purchase order processing purposes. This is a Banner Finance specific item. Controller The chief accounting officer of a business. Cost accounting This component of Banner Finance automates the process by which you charge customers for services rendered. The customers may be internal or external to your organization. Cost principle The widely used concept of valuing assets for accounting purposes at their original cost to the business or government agency. Credit A dollar amount that you enter on the right-hand side of an account ledger. Use a credit to record a decrease in an asset and an increase in a liability or owners' equity. Credit balance The dollar amount of an account in which the total amount of credits exceeds the total amount of debits. Credit memo A credit is a deduction from an amount which is otherwise due. A memo is an informal record. Enter a credit memo against a vendor's account when for various reasons, the vendor owes your installation money. This credit is used against future purchases. This credit transaction remains on the vendor's record until there are enough purchases to equal or exceed the amount of the credit. Creditor The person or company to whom a liability is owed. Current assets Cash and other assets that you can readily convert into cash, such as accounts receivable, inventory and prepaid expenses.
November 2010
G-3
Current liabilities The company debts that are due and payable within the next 12 months. CUSIP Committee on Uniform Securities Identification Procedures. CUSIP is frequently cited in Investment Management documentation. Debit A dollar amount that you enter on the left-hand side of an account ledger. Use a debit to record an increase in an asset and a decrease in a liability or in owners' equity. Debit balance The balance of an account in which the total dollar amount of debits exceeds the total dollar amount of credits. Deficit The net loss of a company when expenditures exceed income or when there is an excess of liabilities over assets. Direct costs Costs which can be traced and allocated directly to a specific product, such as the cost of paper for a corporation, school, or government office. Dividends A cash distribution by a corporation or government agency to its stockholders. Dividends are earned and paid on stocks and bonds. Equity The net value of an asset or business (i.e., assets minus liabilities). ESOP Employee Stock Ownership Plans FASB Financial Accounting Standards Board An independent group that conducts research in accounting practices and issues authoritative statements as to proper accounting principles and methods for reporting financial information.
G-4
November 2010
Financial accounting The area of accounting which emphasizes measuring and reporting in conformity with generally accepted accounting principles, including the financial position and operating results of a business entity. Financial statements Reports which summarize the financial position and operating results of a business (e.g., balance sheet and income statements). Fixed assets Assets of a lasting nature, such as land, buildings, or equipment that you do not usually convert to cash in the course of doing business. Fixed Assets module This component of Banner Finance enables you to track the assets held by your organization. Fixed income funds Funds that invest in securities which pay fixed rates, such as bonds. FOAPAL The Banner Finance System Fund, Organization, Account, Program, Activity, and Location specified for a particular labor distribution. Components are defined as follows: FundA balance sheet item (assets, liabilities, equity). A fund can be restricted (e.g., grants) or unrestricted (e.g., general). Organization A department within the installation. AccountA line item within a site's financial structure. Categories include general ledger accounts (assets and liabilities) and operating ledger accounts (revenues and expenses). ProgramA defined function. Programs enable you to establish a method of pulling transactions across organizations and accounts. Examples include instruction, research, and plant operations. Most educational institutions use programs defined by the National Association of College and University Business Offices (NACUBO). ActivityAn accounting element for use in tracking non-budget-control financial affairs. An example of an activity is the YMCA's use of your site's pool to teach lifesaving. LocationA building and room number.
November 2010
G-5
Generally accepted accounting principles The accounting concepts, measuring techniques, and standards of presentation used in financial statements. Examples include the cost principle, the going-concern assumption, and the objectivity principle. General Ledger module The General Ledger module is the core of the Banner Finance System. General Ledger supports comprehensive fund accounting, including grant and encumbrance accounting. Going-concern assumption An assumption by accountants that a business will continue to operate indefinitely, unless specific evidence to the contrary exists, such as impending bankruptcy. Gross profit or loss The result when you subtract the cost of goods sold from the achieved revenue or sales. Growth funds Growth funds are mutual funds with an investment objective of capital appreciation. Income statement A detailed statement that shows revenue, minus all expenses, which results in a net profit or loss for a specific period. Income taxes payable A liability to government computed as a percentage of profits earned by a corporation. Internal control All measures your business uses to guard against errors, waste, and fraud. Internal control also assures the reliability of accounting data and promotes compliance with all company policies. Inventory A list of goods (commodities) and their quantities on hand. Another name for this is stock. Invoice An itemized list of goods purchased specifying the price and the terms of purchase. An invoice triggers a check to be produced for the vendor as payment for the goods.
G-6
November 2010
Journal A chronological record of transactions. Journals show the debits and credits entered in specific ledger accounts for each and every transaction. Ledger The online records that contain all the separate accounts of a business. Liabilities The debts or obligations of a business. The claims of creditors against the assets of a business or government agency. Liquid assets Assets which you can readily convert to cash. Liquidity The degree to which a company can produce cash within a short time frame. Money market funds Money market funds invest in short term (less than 13 months) debt obligations. They are different from bond funds because the principal investment is safer. Because of the safety factor, the interest rate for money market funds is usually lower due to the lower risk associated with short-term debt obligations. Municipal bonds There are two types of government bonds: federal and local. Only bonds issued by state or local governments are considered municipal bonds. Municipal bonds, with the exception of certain private activity bonds, are federally tax-exempt. Private activity bonds include those used to finance sports, convention, and trade show facilities. Private activity bonds are used to finance housing and industrial developments. Private activity bonds may generate taxable interest, subject to the federal Alternative Minimum Tax, depending on your individual tax circumstances. NACUBO National Association of College and University Business Officers Net profit or loss Obtain your net profit or net loss when you subtract Other Expenses and add Other Income to the Gross Profit or Loss.
November 2010
G-7
Net worth The business owner's equity in a company represented by the difference between total assets and total liabilities. Notes payable Liabilities evidenced by a formal written promise to pay a certain amount of money, plus interest, at a future date. Usually arises from borrowing. NSF checking Non-sufficient funds checking. This feature checks to determine if there is an available budget to cover an expenditure. Packing slip An itemized list of the goods and quantities purchased, supplied by the vendor with a shipment. A packing slip is used by the receivers on a dock to check against the purchase order. PIDM Personal Identification Number. In Banner, this is an internal identification number assigned to any person or company that uniquely identifies this entity. Posting The process in which you transfer information from the journal to individual accounts in the ledger. Prospectus The official document that describes a mutual fund. Each mutual fund has a particular goal or investment objective. Purchasing and Procurement module Use the Purchasing and Procurement module (and the Receiving features) to handle on-demand request purchasing and long term purchasing operations. Report A written record or summary of data in hard copy form. Retained earnings The portion of stockholders' equity that results from profits that have been retained in the business, rather than distributed as dividends.
G-8
November 2010
Scroll This feature allows you to move through the text on a screen or portion of a screen as if unrolling a scroll. The keyboard option for this feature is your Page Up/Page Down keys. The mouse option for this feature is to click the directional arrows in the bars to the sides of a window. Share price To determine the share price of an investment portfolio, divide the number of shares into the market value of the entire portfolio. Solvency You are considered financially solvent when your accounts contain enough money to pay debts as they become due. Stocks Stocks are securities. When you buy stock issued by a corporation, you own shares or have equity in that company. You may sell stock shares at any time. If you sell shares for a price higher than the original purchase price, your records show a profit or capital gain. If you sell shares for a price lower than the original purchase price, your records show a loss or capital loss. Student Accounts Receivable module This module is an optional feature for Banner Finance. It supports higher education specific accounts receivable processing. Transactions Business events you can measure in fiscal amounts and which you enter in accounting records. Vendor A person or company selling goods or providing services to your institution. Typically, Banner Finance requires a vendor record for anyone to whom a check is sent.
November 2010
G-9
G-10
November 2010
Index
Numerics
1099 creating a correction version 2-86 creating an original 2-85 1099 Forms Print (FAB1099) 4-6 1099 Forms Test Patterns (FAT1099) 4-71 1099 Reporting/Withholding Audit Report (FARWHLY) 4-69 1099 Reporting/Withholding Status Report (FARWHLD) 4-67 1099 Tape Summary Audit Report (FAM1099) 4-24 1099 withholding 2-249 Agencies adding 2-169 search 2-169 Agency Budget Report (FRRABUD) 4-418 Agency codes establishing 2-170 Application of Payment Process (TRRAPPL) 4-393 Approval forms Approvals Notification Form (FOIAINP) 2-191 Document Approval Form (FOAAINP) 2191 Finance Approval Menu (FINAPPR) 2191 User Approval Form (FOAUAPP) 2-191 Approval Process (FORAPPL) 4-303 Approval Process Flow 2-193 Approval Queue Maintenance Form (FTMAPPQ) 2-197 Approval Queue Routing Codes Form (FOMAQRC) 2-193 Approvals canceling document after final approval 2-196 overview 2-191 Approvals form Approval History Form (FOIAPHT) 2-191 Approval Queue Maintenance Form (FTMAPPQ) 2-191 Approval Queue Routing Codes Form (FOMAQRC) 2-191 Document Approval History Form (FOIAPPH) 2-191 Approvals Processing 2-191 Approved Budget Report (FBRAPPR) 4-79 Approved Distributed Budget Report (FBRAPPD) 4-75 Archive/Purge Process (FOPARCP) 4-628 Attributes for Statement of Net Assets 4-649 Automatic accounting redistribution 2-210 Automatic journal vouchers 2-24, 2-57 Automatic rate calculation
A
ABC Classification 2-274 Account Hierarchy Report (FGRACTH) 4-147 Account index defaults 2-66 Account Index Report (FGRACCI) 4-144 Accounting data querying 2-87 Accounts payable transaction definitions 2-257 Accounts Payable module description 1-5 Accounts Payable procedures Calculating tax exemption amounts 2253 Creating "Doing Business As" (DBA) vendors 2-249 Creating a correction 1099 2-86 Creating a new vendor 2-248 Creating an original 1099 2-85 Running bank reconciliation 2-246 Running bank reconciliation reports 2247 Accrual period 2-79 Activity Codes Report (FGRACTV) 4-149 Adjustments to cost 2-270
November 2010
Banner Finance 8.5 User Guide Index
I-1
equipment 2-349 for organizations 2-343 inventory 2-348 material management 2-350 Available balance checking establishing 2-14 Available balance process 2-26 set-up parameters 2-14 Available Balance Rebuild Process (FGRBAVL) 4-151
B
Balance Forward Processing Report (FGRGLRL) 4-222 Balance Sheet Report (FGRBLSH) 4-162 Bank Cash Interfund Account Balance Exception Report (FGRBIEX) 4-164 Bank Interfund Account Control Report (FGRCASH) 4-167 Bank reconciliation 2-247 Bank Reconciliation - Activity Aging Report (FARAAGE) 4-41 Bank Reconciliation Balance Report (FARBBAL) 4-42 Bank Reconciliation Report (FARBREC) 4-43 Banner Finance System major features 1-2 module descriptions 1-4 Batch Check Accounting Process (FABCHKA) 4-9 Batch Check Process (FABCHKS) 4-18 Batch Direct Deposit Advice Print Process (FARDIRD) 4-49 Batch Disbursement Register Process (FABCHKR) 4-16 Bid Evaluation Report (FPRBEVL) 4-318 Bid Form Print Report (FPABIDD) 4-305 Bids creating from requisitions 2-241 Billing Detail Exception Report (FRRBDEX) 4-420 Billing Exception Report (FRRBEXC) 4-422 Billing process preparation 2-329 running 2-331 Blanket orders creating 2-221
invoice directly against 2-222 purchase order directly against 2-222 remaining balance 2-223 Budget carrying forward to next year 2-77 Budget and Position Control module description 1-5 Budget Build Process (FBRBDBB) 4-83 Budget carry forward parameters 2-14 Budget Data Finance Extract (NHPFIN1) 4530 Budget Defaults SS Mass Update (FBPBDEF) 4-73 Budget Development overview 2-287 Budget Development procedures Budget development cycle 2-287 Budget maintenance time line example 2-291 Deleting a budget phase by account type and fund type 2-296 Establishing subsequent fiscal year phases 2-291 Rolling an approved budget phase to OPAL 2-295 Budget Distribution Report (NHRBDST) 4537 Budget Maintenance Process (NBPBUDM) 4-499 Budget Mass Change Process (FBRMCHG) 4-88 Budget phase deleting by account type 2-296 Budget phases Changing line items within a budget phase 2-292 Establishing initial phases 2-291 Establishing subsequent fiscal year phases 2-291 Budget roll approved budget phase to OPAL budget ledgers 2-295 multiple budget phases into a final phase 2-295 roll phase to phase within budget ID 2292 Budget Roll Process Report (NBPBROL) 4496 Budget Roll to General Ledger (FBRBDRL) 4-85
I-2
November 2010
Budget Status (Current Period) Report (FGRBDSC) 4-159 Budget Worksheet Report (FBRWKSH) 4-89 Budget Worksheet Report (NBRBWRK) 4515 Budgets approving working 3-38 establishing and feeding 3-6 modeling 3-16
C
C/A Rate Schedule Report (FCRSCHD) 4106 C/A Variance Analysis Report (FCRVARA) 4108 Canadian Direct Deposit Tape Process (FAPCDIR) 4-30 Canadian Standard Report Form (FRRCNSF) 4-427 Cash Gifts 2-297 Cash receipts processing from a vendor 2-60 Using the Direct Cash Receipt Form (FGADCSR) 2-61 Cash Receipts Report (FGRCSRP) 4-153 Cash Requirements Report (FARCSHR) 447 Change Order Form Print Report (FPACORD) 4-306 Change orders completing 2-221 creating 2-214 currency conversion 2-220 querying 2-221 Changes in Unrestricted Net Assets Report Statement of Revenues, Expenses, and Other Changes (FGRCUNA) 4-207 Check Print Process (FABCHKP) 4-15 Check Register Report (FARCHKR) 4-44 Checks cancelling with recurring payable 2-269 recurring payables 2-269 Close Operating Accounts Report (FGRCLOP) 4-200 COBRA feed checklist for 3-60 processing transactions for 3-56 Collections Report (TRRCOLL) 4-475
collector tables 2-130, 2-132 Combined Balance Sheet - All Fund Types and Account Groups (FGRCOBS) 4-171 Combined Statement of Revenues, Expenditures, and Changes in Fund Balance Budget and Actual 4-179 Combined Statement of Revenues, Expenditures, and Changes in Fund Balances (FGRCREF) 4-175 Combined Statement of Revenues, Expenses, and Changes in Retained Earnings/Fund Balances 4-182 Combining Balance Sheets Report (FGRCBSR) 4-184 Combining Statement of Revenues, Expenditures and Changes in Fund Balance (FGRCSSR) 4-188 Commodity level accounting criteria 2-257 purchase order 2-224 reallocation 2-212 taxes 2-251, 2-253 with a purchase order 2-224 commodity level accounting 2-201 Comparative Balance Sheets Report (FGRCGBS) 4-186 Comparative Statements of Revenues, Expenditures and Changes in Fund Balances (FGRCSCF) 4-190 Comparative Statements of Revenues, Expenditures, and Changes in Fund Balances - Budget and Actual (FGRCGBA) 4-192 Comprehensive Annual Financial Reports 4169 Concurrent year processing 2-80 Cost Accounting Billing Detail Report (FCRBDTR) 4-104 Cost Accounting Billing Process (FCBBILL) 4-93 Cost Accounting module description 1-6 Cost Accounting procedures Defining additional external rates 2-340 Entering project charges 2-341 Establishing a project/work order 2-338 Establishing cost types for an organization 2-345 Establishing rate codes for an organization 2-343
November 2010
I-3
Preparing the billing process 2-329 Cost adjustments 2-270, 2-282 Cost types assigning to organization 2-346 entering the actual units 2-341 establishing 2-345 internal rate codes 2-346 Credit memo creating in prior year 2-82 Currency conversion Accounts Payable Module 2-159 Accounts Receivable Module 2-159 by module 2-158 cash accounts 2-17 defining values 2-158 entering information 2-209 foreign vendors 2-264 General Ledger Module 2-159 journal vouchers 2-159 overview 2-157 Purchasing and Procurement Module 2159 taxes 2-213 Customers adding 2-171
Direct Deposit Transmittal Register Process (FAPTREG) 4-40 Disbursement Check Report (FABCHKD) 412 Distribution Process Summary (FBRBDDS) 4-84 Dock to Stock Exceptions Report (FSRSTEX) 4-367 Document level accounting criteria 2-257 redistribution 2-262 document level accounting 2-201 Due To/Due From Control Report (FGRTOFR) 4-296
E
Effective date processing 2-32 Effort Certification Report (NHRECRT) 4-578 Employee Distributions Report (NHREDST) 4-595 Employee Payroll Summary by Organization (NHRSDST) 4-604 Employees adding 2-171 Encumbrances roll parameters 2-14 rolling 2-74 rolling a prior year encumbrance 2-76 End-of-Year Budget Carry Forward Report (FGRBDRL) 4-158 End-of-Year Encumbrance Carry Forward Report (FGRENRL) 4-211 Equipment Rental Rate Calculation Report (FCBEQPT) 4-96
D
Daily Transaction Control Report (FGRTRNH) 4-298 Data Extract Process (FGPGEXT) 4-142 Date querying on 2-88 Defaulting logic 2-64 Defaults Account Indexes 2-66 defining for FOAPAL 2-66 Deferred editing 2-23 change order 2-216 invoices 2-260 journal vouchers 2-55 Deferred Grant Process (FRRGRNT) 4-385 Deferred Grant Purge Process (FRRGRNP) 4-389 Delivery Log Report (FPRDELV) 4-320 Depreciation Process (FFPDEPR) 4-110 Direct Deposit File Creation Process (FAPDIRD) 4-31
F
Federal Financial Report (FRRFFRR) 4-442 Finance Budget Feed Process (FBRFEED) 4-86 Finance Feed Sweep Process (FURFEED) 4-494 Finance Interface Report (NHPFIN2) 4-532 Finance Operations module description 1-4 Finance Operations procedures Adding agencies to the database 2-169
I-4
November 2010
Adding customers to the database 2-171 Adding employees in the database 2-171 Adding financial managers to the database 2-166 Adding vendors to the Finance database 2-164 Approval queue routing set-up example 2-199 Approvals processing 2-191 Canceling a document after final approval 2-196 Currency conversion overview 2-157 Defining currency conversion values 2158 Direct Cash Receipt Approvals 2-200 Identifying persons and entities in the Finance database 2-161 Finance Upload to GURFEED Process (FUPLOAD) 4-486 Financial managers 2-166 Fixed Asset DTAG Aging Report (FFRDTGA) 4-121 Fixed Asset DTAG Transaction Report (FFRDTGT) 4-123 Fixed Asset Origination Tag Extraction Process (FFPOEXT) 4-114 Fixed Asset Property Report (FFRPROP) 4136 Fixed Asset/Asset Group Report (FFRAGRP) 4-117 Fixed Assets attachments and components 2-308 impact of cancellation of checks 2-307 impact of cancellation of invoices 2-307 Origination Tag Creation Matrix 2-305 Origination Tag Extraction Matrix 2-306 Fixed Assets module description 1-6 Fixed Assets procedures adjustment functions 2-314 Depreciation Adjustment 2-318 GL Change - Asset Account 2-320 GL Change - Cap Amount/Account 2-324 GL Change - Equity Account 2-321 GL Change - Fund and Equity 2-323 GL Change - Fund Code 2-322 Origination Tag Capitalization 2-317 Permanent Tag Capitalization 2-317 Record Past Depreciation 2-319
Sale of Asset 2-314 Write Off 2-315 Write Up/Down Adjustments 2-316 adjustments 2-312 completing 2-314 creating 2-312 querying 2-327 Automatic Capitalization Process 2-304 commodity and accounting records 2297 completing adjustment documents 2-314 creating adjustment documents 2-312 creating commodity codes 2-302 creating depreciation framework 2-309 creating depreciation method codes 2309 defining supporting structure 2-297 depreciation 2-309 Depreciation Process 2-311 direct capitalization 2-307 establishing account codes 2-297 fund code hierarchy 2-299 Origination Tag Process 2-304 referencing a credit memo 2-307 set-up 2-297 FOAPAL redefaulting 2-65 Foreign currency see Currency conversion 2-158 Forms NTRFINI HR/Finance Set Up Rule Form 3-3 Fund Balance Account Report (FGRFBAL) 4215 Fund Exception Report (FRRFEXC) 4-440 Fund Hierarchy Report (FGRFNDH) 4-218 Fund/Account Activity Report (FGRFAAC) 4213
G
G/L Transaction Activity Report (FGRGLTA) 4-225 GASB Extract Process Attribute Errors reports 4-654 General Accounting Transaction procedures Automatic journal voucher process 2-57 Budget carry forward 2-77 Cash activity in the prior year 2-80
November 2010
I-5
Closing operating control accounts 2-77 Concurrent year processing 2-80 Creating a journal entry transaction 2-54 Currency conversion for journal vouchers 2-159 Encumbrance roll 2-74 FOAPAL defaulting 2-64 General ledger transactions in the prior year 2-80 OPAL transactions in the prior year 2-80 Opening accrual periods 2-72 Posting examples of liquidations in the prior year 2-82 Querying a specific date 2-88 Querying accounting data 2-87 Rolling a prior year encumbrance 2-76 Rolling general ledger balances 2-72 Year end processing 2-71 Year end processing checklist 2-78 General Ledger Balance Forward Process (FGRGLRL) 2-73 General Ledger module description 1-4 General Ledger procedures Available balance process 2-26 Effective date processing 2-32 Establishing alternatives for cash accounts and bank funds 2-15 General Ledger Consolidated Postings 2-20 General Ledger Summary Postings 2-21 Pro-rata cost allocation 2-33 Generic Bill Form (FRRGENB) 4-455 Generic Report Form (FRRGENR) 4-459 GL/Subsidiary Ledger Control Report (FGRCTRL) 4-203 Grant Billing Preview Report (FRRINVS) 4469 Grant Budget Interface Process (FRPBINF) 4-373 Grant Budget Report (FRRBUDG) 4-425 Grant Budget Status Report (FRRGBFY) 4452 Grant Events Report (FRREVNG) 4-432 Grant Expenditures Report (FRRINDC) 4466 Grant Inception to Date Report (FRRGITD) 4463 Grant interface process
interfacing grant information to Banner 2130 mapping collector tables to grant tables 2-132 running 2-131 Grant Interface Process (FRPGINF) 4-375 Grant Ledger Exception Report (FGRGLEX) 4-396 Grant Processing procedures T Account examples 2-101 Grant Rebuild Process (FGRGRBD) 4-155, 4-372 Grant Reconciliation Report (TRRRCON) 4479 Grant/Budget Error Printing (FRRTRNR) 4471 Grants Aging Analysis Report (TRRAGES) 4472
I
ID Person Definition tables 2-172 PIDM relationship 2-172 Identification Form (FOAIDEN) 2-161 IFOAPAL definition 2-338 Inception to Date Activity Report (FGRFITD) 4-216 Incomplete Document Report (FGRIDOC) 4228 Interfaces Banner Finance System approving working budgets 3-39 budget modeling 3-17 establishing and feeding budgets 3-6 feeding payroll transactions 3-48 installments/feed to finance 3-64 processing wage/salary adjustments 3-30 introduction 3-1 NTRFINI HR/Finance Set Up Rule Form 3-3 processing COBRA transactions 3-56 Interfund accounts 2-16 Internal rate codes assigning 2-344 assigning cost types 2-346 creating 2-344
I-6
November 2010
Internal Vendor Order Processing 2-184 Internal Controls 2-184 Internal Vendor Setup 2-185 Process Flow 2-186 Process Flow 2-189 running FUPLOAD in Audit mode 2-187 running FUPLOAD in Update Mode 2187 Security Considerations 2-184 Special Considerations 2-185 Step-by-Step Process 2-187 Inventory adjustment status 2-271 paying in Accounts Payable 2-281 purchasing from outside vendors 2-275 purchasing within a department 2-276 receiving 2-281 Inventory Handling Rate Calculation Report (FCBINVT) 4-99 Inventory Listing Report (FSRINVL) 4-342 Invoice Activity Report (FARINVA) 4-51 Invoice Aging Report (FARIAGE) 4-50 Invoice Feed Process (FAPINVT) 4-37 Invoice Processing procedures Issuing an invoice 2-256 Setting up recurring payables 2-268 Using a one-time vendor 2-266 Using the Invoice/Credit Memo Form (FAAINVE) 2-257 Invoice Selection Report (FARINVS) 4-53 Invoices against a purchase order 2-222 checks 2-269 entering charges 2-342 entering information 2-257 in the Receiving/Matching Process 2-174 Invoice/Credit Memo Form (FAAINVE) 2257 issuing 2-256 project codes 2-342 recurring payable 2-269 specifying invoice type 2-256 Invoices Awaiting Receiver Report (FARIREC) 4-55 Issue Ticket Report (FSRISST) 4-345 Issues goods 2-270 overview 2-270
J
Journal Voucher Listing Report (FGRJVLR) 4-230 Journal vouchers automatic journal voucher process 2-57 creating an entry transaction 2-54 currency conversion 2-159 entering charges 2-342 posting 2-56 using the Journal Voucher Entry Form (FGAJVCD) 2-54
L
Labor Rate Calculation Report (FCBLABR) 4-101 Line item changes within a budget phase 2292 Location Hierarchy Report (FGRLOCH) 4242
M
Mass Salary Table Update Report (NBPMASS) 4-504 Material Management Rate Calculation Report (FCBMATL) 4-102 Merge budgets 2-295 Multiple Fund Balance implementing 2-18 Multiple fund balance processing 2-18
O
One-time vendor 2-266 OPAL definition 2-278 ledger entries 2-279 transactions in the prior year 2-80 Open Encumbrance Report (FGROPNE) 4247 Open Invoice Report (FAROINV) 4-57 Open Purchase Order Report (FPROPNP) 4321 Open Requisitions Report (FPROPNR) 4326
November 2010
I-7
Open Stores Requisitions Report (FSROPNR) 4-350 Operating control accounts 2-77 Oracle security 2-1 Organization Detail Activity Report (FGRODTA) 4-244 Organization Hierarchy Report (FGRORGH) 4-252 Organization Payroll Distribution (NHRDIST) 4-557
P
Packing slips purchase order 2-243 Payroll feeding transactions 3-48 PCard processing forms FAAINVT Purchase Card Transaction Maintenance Form 2-239 FAICARD Purchase Card Query Form 2-240 FOMPROF User Profile Maintenance Form 2-241 FTIIDEN Entity/Name ID Search Form 2-241 FTMCARD Purchase Card Maintenance Form 2-239 FTMPCSH Payment Cutoff Schedule Maintenance Form 2240 FTVMCAT Merchant Category Code Validation Form 2-240 how to configure Banner 2-228 how to initialize PCard 2-228 loading PCard data 2-232 process flow 2-227 process flow description 2-227 processing options 2-230 things to consider 2-226 Physical inventory 2-270 Physical Inventory Discrepancy Report (FSRPIDR) 4-359 Physical Inventory Process Report (FSRPHYR) 4-354 Physical Inventory Worksheet (FSRPIWS) 4362
Pick List Report (FSRPICK) 4-356 PIDM ID relationship 2-172 PO Batch Close Process (FPPPOBC) 4-314 PO Receiving Status Report (FPRRCST) 4332 Position Class Incumbent Report (NBRPINC) 4-522 Position Class Listing Report (NBRPCLS) 4520 Position Report (NBRPOSN) 4-524 Position Status Exception Report (NBRPSTA) 4-527 Posting change order 2-221 cost adjustments 2-282 Direct Cash Receipts 2-63 invoice against a purchase order 2-222 invoice charges 2-342 invoice paid purchase order 2-342 journal vouchers 2-56 Posting program (FGRACTG) 2-222 project encumbrances 2-340 purchase order remaining balance 2-223 Stores Inventory 2-275 submission parameters 2-268 Posting Process (FGRACTG) 4-145 Prior year cash activity 2-80 posting liquidations 2-82 Pro Rata Allocation Process (FGRPRAP) 4257 Pro Rata Allocation Report (FGRPRAR) 4265 Pro-rata cost allocation defining allocation information 2-33 hierarchy 2-35 limiting rule groups 2-36 overview 2-33 performing allocations 2-36 reporting 2-36, 2-38 Procedures ABC classification 2-274 Adding agencies to the database 2-169 Adding customers to the database 2-171 Adding employees to the database 2-171 Adding financial managers to the database 2-166
I-8
November 2010
Adding vendors to the Finance database 2-164 Approval queue routing set-up example 2-199 Approvals processing 2-191 Automatic journal voucher process 2-57 Available balance process 2-26 Budget carry forward 2-77 Budget development and position control introduction 3-1 Budget development cycle 2-287 Budget maintenance time line example 2-291 Calculating tax exemption amounts 2253 Canceling a document after final approval 2-196 Cash activity in the prior year 2-80 Cash disbursement activity in the prior year 2-81 Closing operating control accounts 2-77 Commodity level accounting with a purchase order 2-224 Concurrent year processing 2-80 Creating a blanket order 2-221 Creating a change order 2-214 Creating a correction 1099 2-86 Creating a journal entry transaction 2-54 Creating a new vendor 2-248 Creating a receipt of goods 2-242 Creating a requisition 2-209 Creating an original 1099 2-85 Currency conversion for journal vouchers 2-159 Currency conversion overview 2-157 Defining additional external rates 2-340 Defining currency conversion values 2158 Depreciation of fixed assets 2-309 Determining the remaining balance of a blanket order 2-223 Effective date processing 2-32 Encumbrance roll 2-74 Entering cost adjustments to physical inventory 2-270 Entering currency conversion information 2-209 Entering project charges 2-341 Entering tax information 2-251, 2-253 Establishing a project/work order 2-338
Establishing accounting structure for fixed assets 2-297 Establishing alternatives for cash accounts and bank funds 2-15 Establishing commodity structure for fixed assets 2-302 Establishing cost types for an organization 2-345 Establishing rate codes for an organization 2-343 Fixed asset adjustments 2-312 General ledger summary postings 2-20, 2-21 General ledger transactions in the prior year 2-80 Identifying persons and entities in the Finance database 2-161 Issuing a purchase order 2-212 Issuing an invoice 2-256 Opening accrual periods 2-72 Performing a query for specific date 2-88 Posting examples of liquidations in the prior year 2-82 Posting processes 2-275 Preparing the billing process 2-329 Processing an invoice against a purchase order 2-222 Querying accounting data 2-87 Receiving and matching process 2-173 Rolling a prior year encumbrance 2-76 Rolling general ledger balances 2-72 Running bank reconciliation 2-246 Running bank reconciliation reports 2247 Setting up recurring payables 2-268 T Account examples 2-101 Using a one-time vendor 2-266 Using the Invoice/Credit Memo Form (FAAINVE) 2-257 Valuation process 2-274 Year end processing 2-71 Year end processing checklist 2-78 Procurement Card processing See PCard processing 2-226 Program Detail Activity Report (FGRPDTA) 4-254 Program Hierarchy Report (FGRPRGH) 4272 Project charges 2-341 Project work order 2-338
November 2010
I-9
Proposal Events Report (FRREVNP) 4-436 Purchase Card Transactions Process (FAPCARD) 4-27 Purchase Order Activity Report (FPRPURA) 4-328 Purchase Order Form Print Report (FPAPORD) 4-311 Purchase orders assigning requisitions 2-224 commodity level accounting 2-224 issuing 2-212 processing an invoice against 2-222 Purchasing and Procurement module description 1-5 Purchasing and Procurement procedures Commodity level accounting with a purchase order 2-224 Creating a blanket order 2-221 Creating a change order 2-214 Determining the remaining balance of a blanket order 2-223 Issuing a purchase order 2-212 Processing an invoice against a purchase order 2-222 Receiving/matching process 2-174 Put List Report (FSRPUTL) 4-364
Q
Queue routing 2-199
R
Rate codes establishing for an organization 2-343 Rebates establishing multiple rebate percentages 2-253 specifying a default rebate accounting distribution 2-253 specifying distribution information 2-254 using the Rebate Maintenance Form (FTMREBT) 2-253 Receipts creating 2-242 Receiving & Delivery Report (FPRRCDL) 4330 Receiving and matching process 2-173
Receiving Matching Process (FABMATC) 420 Receiving Processing procedures Creating a receipt of goods 2-242 Receiving/matching process 2-173 Reconciliation bank records 2-246 Recurring payables cancelling 2-269 checks 2-269 setting up 2-268 submission 2-268 Redefaulting FOAPAL 2-66 Remaining balance purchase order 2-223 Reports Naming conventions 4-2 Reports and Processes Attributes for Statement of Net Assets 4649 Comprehensive Annual Financial Report (CAFR) 4-169 FAB1099 1099 Forms Print 4-6 FABCHKA Batch Check Accounting Process 4-9 FABCHKD Disbursement Check Report 4-12 FABCHKP Check Print Process 4-15 FABCHKR Batch Disbursement Register Process 4-16 FABCHKS Batch Check Process 4-18 FABMATC Receiving Matching Process 4-20 FAM1099 1099 Tape Summary Audit Report 4-24 FAPCARD Purchase Card Transactions Process 4-27 FAPCDIR Canadian Direct Deposit Tape Process 4-30 FAPDIRD Direct Deposit File Creation Process 4-31 FAPINVT Invoice Feed Process 4-37 FAPTREG Direct Deposit Transmittal Register Process 4-40 FARAAGE Bank Reconciliation - Activity Aging Report 4-41 FARBBAL Bank Reconciliation Balance Report 4-42
I-10
November 2010
FARBREC Bank Reconciliation Report 443 FARCHKR Check Register Report 4-44 FARCSHR Cash Requirements Report 4-47 FARDIRD Batch Direct Deposit Advice Print Process 4-49 FARIAGE Invoice Aging Report 4-50 FARINVA Invoice Activity Report 4-51 FARINVS Invoice Selection Report 4-53 FARIREC Invoices Awaiting Receiver Report 4-55 FAROINV Open Invoice Report 4-57 FARVALP Vendor Alphabetical Listing Report 4-61 FARVHST Vendor History Report 4-63 FARVNUM Vendor Numerical Listing Report 4-65 FARWHLD 1099 Reporting/Withholding Status Report 4-67 FARWHLY 1099 Reporting/Withholding Audit Report 4-69 FAT1099 1099 Forms Test Patterns 4-71 FBPBDEF Budget Defaults SS Mass Update 4-73 FBRAPPD Approved Distributed Budget Report 4-75 FBRAPPR Approved Budget Report 4-79 FBRBDBB Budget Build Process 4-83 FBRBDDS Distribution Process Summary 4-84 FBRBDRL Budget Roll to General Ledger 4-85 FBRFEED Finance Budget Feed Process 4-86 FBRMCHG Budget Mass Change Process 4-88 FBRWKSH Budget Worksheet Report 489 FCBBILL Cost Accounting Billing Process 4-93 FCBEQPT Equipment Rental Rate Calculation Report 4-96 FCBINVT Inventory Handling Rate Calculation Report 4-99 FCBLABR Labor Rate Calculation Report 4-101 FCBMATL Material Management Rate Calculation Report 4-102 FCRBDTR Cost Accounting Billing Detail Report 4-104
FCRSCHD C/A Rate Schedule Report 4106 FCRVARA C/A Variance Analysis Report 4-108 FFPDEPR Depreciation Process 4-110 FFPOEXT Fixed Asset Origination Tag Extraction Process 4-114 FFRAGRP Fixed Asset/Asset Group Report 4-117 FFRDTGA Fixed Asset DTAG Aging Report 4-121 FFRDTGT Fixed Asset DTAG Transaction Report 4-123 FFRMAST Fixed Asset Master Record Report 4-127 FFRPROP Fixed Asset Property Report 4-136 FGPGEXT Data Extract Process 4-142 FGRACCI Account Index Report 4-144 FGRACTG Posting Process 4-145 FGRACTH Account Hierarchy Report 4147 FGRACTV Activity Codes Report 4-149 FGRBAVL Available Balance Rebuild Process 4-151 FGRBDRL End-of-Year Budget Carry Forward Report 4-158 FGRBDSC Budget Status (Current Period) Report 4-159 FGRBIEX Bank Cash Interfund Account Balance Exception Report 4-164 FGRBLSH Balance Sheet Report 4-162 FGRCASH Bank Interfund Account Control Report 4-167 FGRCBSR Combining Balance Sheets Report 4-184 FGRCGBA Comparative Statements of Revenues, Expenditures, and Changes in Fund Balances - Budget and Actual 4-192 FGRCGBS Comparative Balance Sheets Report 4-186 FGRCHFB Statement of Changes in Fund Balance Report 4-194 FGRCHNA Statement of Changes in Net Assets Report 4-197 FGRCLOP Close Operating Accounts Report 4-200 FGRCOBS Combined Balance Sheet All Fund Types and Account Groups 4-171
November 2010
I-11
FGRCREF Combined Statement of Revenues, Expenditures, and Changes in Fund Balances 4-175 FGRCSBA Combined Statement of Revenues, Expenditures, and Changes in Fund Balance Budget and Actual 4-179 FGRCSCF Comparative Statements of Revenues, Expenditures and Changes in Fund Balances 4-190 FGRCSRE Combined Statement of Revenues, Expenses, and Changes in Retained Earnings 4-182 FGRCSRP Cash Receipts Report 4-153 FGRCSSR Combining Statement of Revenues, Expenditures and Changes in Fund Balance 4-188 FGRCTRL GL/Subsidiary Ledger Control Report 4-203 FGRCUNA Changes in Unrestricted Net Assets Report Statement of Revenues, Expenses, and Other Changes 4-207 FGRENRL End-of-Year Encumbrance Carry Forward Report 4-211 FGRFAAC Fund/Account Activity Report 4-213 FGRFBAL Fund Balance Account Report 4-215 FGRFITD Inception to Date Activity Report 4-216 FGRFNDH Fund Hierarchy Report 4-218 FGRFPSN Statement of Financial Position Report 4-220 FGRGLEX Grant Ledger Exception Report 4-396 FGRGLRL Balance Forward Processing Report 4-222 FGRGLTA G/L Transaction Activity Report 4-225 FGRGRBD Grant Rebuild Process 4155, 4-372 FGRIDOC Incomplete Document Report 4-228 FGRJVLR Journal Voucher Listing Report 4-230 FGRLOCH Location Hierarchy Report 4242 FGRODTA Organization Detail Activity Report 4-244 FGROPNE Open Encumbrance Report 4-247
FGRORGH Organization Hierarchy Report 4-252 FGRPDTA Program Detail Activity Report 4-254 FGRPRAP Pro Rata Allocation Process 4-257 FGRPRAR Pro Rata Allocation Report 4265 FGRPRGH Program Hierarchy Report 4272 FGRREOB Statement of Revenues, Expenditures, Other Changes 4-274 FGRREOC Statement of Revenues, Expenditures, Other Changes 4-278 FGRTAXR Statement of Taxes and Rebates Report 4-282 FGRTBAL Trial Balance Report 4-288 FGRTBEX Trial Balance Exception Report 4-294 FGRTOFR Due To/Due From Control Report 4-296 FGRTRNH Daily Transaction Control Report 4-298 FGRTRNI Transaction Interface Process 4-301 FGRTRNR Transaction Error Report 4302 FOPARCP Archive/Purge Process 4-628 FOPARCR Restore Process 4-636 FORAPPL Approval Process 4-303 FPABIDD Bid Form Print 4-305 FPACORD Change Order Form Print 4306 FPAPORD Purchase Order Form Print 4311 FPARQST Requisition Form Print 4-313 FPPPOBC PO Batch Close Process 4314 FPRBEVL Bid Evaluation Report 4-318 FPRDELV Delivery Log 4-320 FPROPNP Open Purchase Orders Report 4-321 FPROPNR Open Requisitions Report 4326 FPRPURA Purchase Order Activity Report 4-328 FPRRCDL Receiving & Delivery Report 4-330 FPRRCST PO Receiving Status Report 4-332
I-12
November 2010
FPRVCAT Vendor Products Catalog Report 4-334 FPRVVOL Vendor Volumes Report 4336 FRPBINF Grant Budget Interface Process 4-373 FRPGINF Grant Interface Process 4-375 FRR134B Standard 1034 Billing Form 4398 FRR269R Standard 269 Report Form 4402, 4-442 FRR270B Standard 270 Billing Form 4406 FRR272B Standard 272 Billing Form 4410 FRR272R Standard 272 Report Form 4414 FRRABUD Agency Budget Report 4-418 FRRBDEX Billing Detail Exception Report 4-420 FRRBEXC Billing Exception Report 4422 FRRBILL Research Accounting Billing Process 4-377 FRRBREV Research Accounting Billing Reversal Process 4-383 FRRBUDG Grant Budget Report 4-425 FRRCNSF Canadian Standard Report Form 4-427 FRRCONV Research Accounting Conversion Report 4-430 FRREVNG Grant Events Report 4-432 FRREVNP Proposal Events Report 4436 FRRFEXC Fund Exception Report 4-440 FRRFFRR Federal Financial Report 4442 FRRGBFY Grant Budget Status Report 4-452 FRRGENB Generic Bill Form 4-455 FRRGENR Generic Report Form 4-459 FRRGITD Grant Inception to Date Report 4-463 FRRGRNP Deferred Grant Purge Process 4-389 FRRGRNT Deferred Grant Process 4385 FRRGRPT Research Accounting Report Process 4-390 FRRINDC Grant Expenditures Report 4466
FRRINVS Grant Billing Preview Report 4-469 FRRTRNR Grant/Budget Error Printing 4-471 FSRDTLG Stores Daily Transaction Listing Report 4-339 FSRINVL Inventory Listing Report 4-342 FSRISST Issue Ticket Report 4-345 FSRLWSR Stores Low Stock Report 4348 FSROPNR Open Stores Requisitions Report 4-350 FSROUTP Stores Outstanding Purchases Report 4-352 FSRPHYR Physical Inventory Process Report 4-354 FSRPICK Pick List Report 4-356 FSRPIDR Physical Inventory Discrepancy Report 4-359 FSRPIWS Physical Inventory Worksheet 4-362 FSRPUTL Put List Report 4-364 FSRSTEX Dock to Stock Exceptions Report 4-367 FSRSUPC Supply Catalog Report 4-369 FUPLOAD Finance Upload to GURFEED Process 4-486 FURAPAY Student Refund Interface Process 4-493 FURFEED Finance Feed Sweep Process 4-494 GASB Extract Process Attribute Errors reports 4-654 NBPBROL Budget Roll Process Report 4-496 NBPBUDM Budget Maintenance Process 4-499 NBPMASS Mass Salary Table Update Report 4-504 NBRBWRK Budget Worksheet Report 4515 NBRPCLS Position Class Listing Report 4-520 NBRPINC Position Class Incumbent Report 4-522 NBRPOSN Position Report 4-524 NBRPSTA Position Status Exception Report 4-527 NHPFIN1 Budget Data Finance Extract 4-530
November 2010
I-13
NHPFIN2 Finance Interface Report 4532 NHRBDST Budget Distribution Report 4537 NHRDIST Organization Payroll Distribution 4-557 NHRECRT Effort Certification Report 4578 NHREDST Employee Distributions Report 4-595 NHRSDST Employee Payroll Summary by Organization 4-604 Roll Open Labor Encumbrances Process (FGRLENC) 4-234 TRRAGES Grants Aging Analysis Report 4-472 TRRAPPL Application of Payment Process 4-393 TRRCOLL Collections Report 4-475 TRRRCON Grant Reconciliation Report 4-479 TRRUNAP Unapplication of Payments Process 4-394 TRRUNPL Unapplied Payments Listing 4-483 Request Processing procedures Creating a requisition 2-209 Entering currency conversion information 2-209 Requisition Form Print Report (FPARQST) 4313 Requisitions cancelling 2-196 Research Accounting Billing Process (FRRBILL) 4-377 Research Accounting Billing Reversal Process (FRRBREV) 4-383 Research Accounting Conversion Report (FRRCONV) 4-430 Research Accounting module description 1-7 Research Accounting Report Process (FRRGRPT) 4-390 Restore Process (FOPARCR) 4-636 Returned goods returns 2-270 Roll Open Labor Encumbrances Process (FGRLENC) 4-234 Rule codes balancing methods 2-59
S
salary distribution reporting 4-578 Search persons 2-167 Security Banner 2-2 Oracle 2-1 overview 2-1 Security procedures Security overview 2-1 Standard 1034 Billing Form (FRR134B) 4398 Standard 269 Report Form (FRR269R) 4402, 4-442 Standard 270 Billing Form (FRR270B) 4-406 Standard 272 Billing Form (FRR272B) 4-410 Standard 272 Report Form (FRR272R) 4-414 Statement of Changes in Fund Balance Report (FGRCHFB) 4-194 Statement of Changes in Net Assets Report (FGRCHNA) 4-197 Statement of Financial Position Report (FGRFPSN) 4-220 Statement of Revenues, Expenditures, Other Changes (FGRREOB) 4-274 Statement of Revenues, Expenditures, Other Changes (FGRREOC) 4-278 Statement of Taxes and Rebates Report (FGRTAXR) 4-282 Stock issuing directly 2-277 transferring locations 2-280 Stores Daily Transaction Listing Report (FSRDTLG) 4-339 Stores Inventory accounting entries 2-277, 2-278, 2-279, 2-280, 2-281 request overview 2-269 Stores Inventory module description 1-4 Stores Inventory procedures ABC classification 2-274 Entering cost adjustments to physical inventory 2-270 Posting processes 2-275 Valuation process 2-274 Stores Low Stock Report (FSRLWSR) 4-348
I-14
November 2010
Stores Outstanding Purchases Report (FSROUTP) 4-352 Student Refund Interface Process (FURAPAY) 4-493 Supply Catalog Report (FSRSUPC) 4-369 System Control Maintenance Form (FOASYSC) 2-193
T
Taxes additional charges 2-252 change order 2-220 commodity level 2-251, 2-253 compounded 2-252 establishing a Taxing Authority ID 2-252 establishing information 2-251, 2-253 Establishing tax information 2-251 including discounts 2-252 one-time vendor 2-266 purchase order 2-214 specifying a liability accounting distribution 2-253 using the Tax Rate Code Maintenance Form (FTMTRAT) 2-251 Totals 2-70 Tracking costs 2-342 Transaction Interface Process (FGRTRNI) 223, 4-301 Trial Balance Exception Report (FGRTBEX) 4-294 Trial Balance Report (FGRTBAL) 4-288
Vendor Numerical Listing Report (FARVNUM) 4-65 Vendor Products Catalog Report (FPRVCAT) 4-334 Vendor Volumes Report (FPRVVOL) 4-336 Vendors adding 2-164 addresses and phone numbers 2-250 creating 2-248 Doing Business As (DBA) 2-249 types 2-250
W
Work order 2-338 Wrap-up routine 2-263 accounting redistribution 2-210
Y
Year-end processes concurrent year processing 2-18 multiple fund balance indicator 2-18 Year-end processing checklist 2-78 list of processes 2-78 overview 2-71
U
Unapplication of Payments Process (TRRUNAP) 4-394 Unapplied Payments Listing (TRRUNPL) 4483 User Profile Maintenance Form (FOMPROF) 2-193
V
Valuation 2-274 Vendor Alphabetical Listing Report (FARVALP) 4-61 Vendor History Report (FARVHST) 4-63
November 2010
I-15
4 Country View Road Malvern, Pennsylvania 19355 United States of America www.sungardhe.com

Finance 80500 U

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Finance 80500 U

Uploaded by

Copyright:

Available Formats

BANNER FINANCE USER GUIDE

Release 8.5 November 2010

Trademark, Publishing Statement and Copyright Notice

Prepared by: SunGard Higher Education

Customer Support Center Website

Distribution Services E-mail Address

Revision History Log Publication Date

Banner Finance 8.5 User Guide

Banner Finance 8.5 User Guide Contents

Endowment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Accounts Receivable

Research Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Change Order Form Print Purchase Order Form Print

. . . . . . . . . . . . . . . . (FPACORD) . . . . . . 4-306 . . . . . . . . . . . . . . . (FPAPORD) . . . . . . 4-311

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide Contents

Banner Finance 8.5 User Guide System Overview

Banner Finance System Flow Diagram

Purchasing and Procurement

5 Invoices, Checks, and Direct Deposits Charges and Payments

Customers and Refunds

Requisitions and Valuation

Banner AR Position Budgeting and Control

Project Charges and Encumbrances

Original and Adjusted Budget

Salary and Adjustments

Major Features of Banner Finance

Banner Finance 8.5 User Guide System Overview

Banner Finance 8.5 User Guide System Overview

Banner Finance 8.5 User Guide System Overview

Purchasing and Procurement

Budget and Position Control

Banner Finance 8.5 User Guide System Overview

Banner Finance 8.5 User Guide System Overview

Banner Finance 8.5 User Guide System Overview

Standard/ User Edits

Fund Availability Check

Completed/ Approved Document

Overrride Fund Availability

General/ Operating Ledger

Transaction History Files

Banner Finance 8.5 User Guide System Overview

Procurement Requisition for Stock Approved

Purchase Order for Stock Approved

Receipt of Stock into Dock for Warehouse Locs

Is Stock Invoiced Yet?

Value Stock Cost with PO Cost

Decrease Stock Not Invoiced Qty

Is Inv cost different from PO?